Top 25 Free iPhone Web Apps for Your Daily Life | iPhone Toolbox

Top 25 Free iPhone Web Apps for Your Daily Life

Blogging Writer’s Block | kikolani 2.0
Systems Management Server 2003 Inventory Tool for Dell Update

Documenting Your Task Sequences Automagically

Documenting Your Task Sequences Automagically Often times, after creating an MDT or SCCM task sequence, you need to document it for yourself or your customers. Usually, this involves creating a table with the groups and steps, extracting their descriptions, identifying conditions and denoting the step actions and variables and then having format it all nicely and with indents denoting hierarchy. All of this information is usually already in the XML of the task sequence and all you’re really doing is formatting. You can automatically format XML documents by using an XSL transform with the right logic. In order to do this: 1. Copy the attached file at the bottom of the post to the same folder as your task sequence. 2. Open your task sequence in your favourite text editor. 3. After the first line which should look something like this: or enter the following as the second line: 4. Save your task sequence file and open it in Internet Explorer. Presto! The XSL takes care of formatting, indents and sizing. Your Task Sequence should look like this: image You can even change the styles of groups and steps easily. 1. Open up the tsDocumentorv1.xsl file 2. Edit the following section: TD.group { background-color:teal;color:white } TD.step { background-color:beige } Change the colours or any other css properties you choose! The XSL should work with task sequences created with BDD 2007, MDT 2008 and SCCM 2007. Please try it out and post comments. This post was contributed by Aly Shivji a consultant with Microsoft Services - U.S. East Region.

http://blogs.technet.com/deploymentguys/archive/2008/08/17/documenting-your-task-sequences-automagically.aspx

Hotfix for ConfigMgr WoL Issue

SMS&MOM : Update for ConfigMgr 2007: Current issues with Wake On LAN (WOL)

hotfix here.

A few months ago Brian Huneycut wrote a post titled ConfigMgr 2007: Current issues with Wake On LAN (WOL) and we now have a hotfix to address the issue.  We released the  hotfix under KB953148 but the fix is actually in SP1 so if you’re current you should be good to go.

J.C. Hornbeck | Manageability Knowledge Engineer

SMS&MOM : ConfigMgr 2007: Sample Configurations and Common Performance Questions DOC
“We are pleased to announce the release of our first update to Microsoft Deployment Toolkit 2008 (MDT 2008). And overview and the download link is below: ======== Overview Microsoft Deployment Toolkit (MDT) 2008 Update 1 unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. The fourth generation deployment accelerator adds integration with recently released Microsoft deployment technologies to create a single path for image creation and automated installation. MDT’s tools and end-to-end guidance reduce deployment time, standardize desktop and server images, limit service disruptions, reduce post-deployment help desk costs, and improve security and ongoing configuration management. Microsoft Deployment Toolkit technologies eliminate interaction time required to install desktop and server operating systems. Interaction at the targeted computer may take a few moments using the Lite Touch Installation (LTI) method or it can be completely automated using Zero Touch Installation (ZTI). Zero Touch Installation utilizes Microsoft System Center Configuration Manager 2007 or Systems Management Server 2003 with the Operating System Deployment Feature Pack. Lite Touch Installation can be used when software distribution tools are not in place. Microsoft Deployment Tookit 2008 Update 1 also uses Configuration Manager 2007’s stand-alone media-initiated operating system deployment feature. This release offers project management guidance for all deployment roles and separates technical documentation for the products and technologies to facilitate automation tasks. What’s New in MDT 2008 Update 1? MDT 2008 Update 1 includes new capability for OEM preload scenarios, a revised System Center Operations Manager Management Pack, bug fixes, and revised documentation. This updated version provides guidance in the .chm help file format only. If you need the guidance in .doc file format, you can download it here. MDT 2008 Update 1 enables deployment of the following Microsoft products: * Windows Vista Business, Enterprise, and Ultimate (32 and 64 bit) RTM and SP1 * Office Professional, Professional Plus, Enterprise, and Ultimate 2007 * Windows Server 2008 * Windows Server 2003 R2 (32 and 64 bit) * Windows XP Professional with Service Pack 2 and Service Pack 3 (32 and 64 bit) or Windows XP Tablet PC Edition To continue reading and to download see http://www.microsoft.com/downloads/details.aspx?FamilyID=3bd8561f-77ac-4400-a0c1-fe871c461a89&DisplayLang=en. J.C. Hornbeck | Manageability Knowledge Engineer”
— SMS&MOM : ConfigMgr 2007: Announcing the Microsoft Deployment Toolkit 2008 Update 1 Solution Accelerator!
“Here’s a great tip from Frank Rojas, a real life Support Engineer in North Carolina. If you having trouble with Remote Desktop on some of your clients and can’t figure out why then this may be your issue: ======== Issue: Remote control is setup in ConfigMgr 2007 via the Remote Tools Client Agent. Remote Tools, Remote Assistance, and Remote Desktop work fine on Windows XP clients, however, only Remote Tools works on Windows Vista clients. Note: Remote Assistance is not supported on Windows Vista clients Cause: This problem is caused by Network Level Authentication being turned on under the Remote Desktop tab of the Remote Tools Client Agent. If the Operating System of the PC trying to initiate the remote control session does not support Network Level Authentication it will fail to connect. Currently, the only Operating Systems that support Network Level Authentication are Windows XP SP3, Windows Vista, and Windows Server 2008. Resolution: To fix the problem, take one of the two following actions: * Run the ConfigMgr Admin console from a PC running on an OS that supports Network Level Authentication and initiate the remote control session from that PC. or * In the ConfigMgr Admin Console, disable the option “Require Network Level Authentication on computers running Windows Vista” under the Remote Desktop tab in the Remote Tools Client Agent. Policy needs to update on PCs before you can start using remote control on the PCs. Additional information: For information on how to configure the Windows Firewall ports for Configuration Manager clients and remote control see http://technet.microsoft.com/en-us/library/bb694088.aspx. For more information on Network Level Authentication see Understanding Network Level Authentication at http://technet.microsoft.com/en-us/library/cc505913.aspx. ======== Thanks Frank! J.C. Hornbeck | Manageability Knowledge Engineer”
— SMS&MOM : ConfigMgr 2007: Remote Desktop remote control does not work with Windows Vista clients
“The Desktop Files: Windows Deployment Services 101 Wes Miller continues digging into Windows Deployment Services. In this column, he explores the different versions of WDS, shows you how you can capture a custom operating system image, and tells you what you need in order to perform more automated installations. If you missed the first part of this series on Windows Deployment Services, Network-Booting Windows, you’ll find it here. And stay tuned—more to come in the September issue.”
— TechNet Magazine Blog : The Desktop Files: Windows Deployment Services 101
“New ENERGY STAR Compliant Power Management Tool Just a quick update for all you energy conscious IT professionals. Microsoft has launched a new Desired Configuration Management (DCM) pack for Microsoft System Center Configuration Manager 2007. The new pack fully complies with ENERGY STAR configuration guidelines and is endorsed by the United States Environmental Protection Agency (EPA). This new tool lets you assess your client settings against ENERGY STAR recommendations. You can: * Ensure computers enter system standby or hibernate after 30 to 60 minutes of inactivity. * Ensure monitors enter sleep mode after 5 to 20 minutes of inactivity. * Create a warning notification report if screen savers are not disabled. Ultimately, this can help lower your operational costs and it provides a basis for compliance reporting against various pledge programs, such as Climate Savers Computing Initiative and ENERGY STAR Low Carbon IT Campaign. You can download the Microsoft Assessment Configuration Pack for ENERGY STAR Power Management or read more about it on the Microsoft Environment site.”
— TechNet Magazine Blog : New ENERGY STAR Compliant Power Management Tool