Since the dawn of time, Windows PE (WinPE) has not had any support for the 802.1x authentication protocol. This meant that any network deployment of Windows via a network secured with 802.1x was a non-starter, causing headaches for a few on my customers; I actually had one customer that ran new network cables to a majority of the desks in order to be able to deploy Windows XP over the network.
The Deployment Guys : Added support for 802.1x in Windows PE
System Center Configuration Manager 2007 Operating System Deployment has the ability to migrate the time zone from the source operating system to the destination operating system. This is done by using the Migrate time zone option in the Capture Windows Settings step of the task sequence.
Unfortunately, MDT Lite Touch Deployment does not offer the same functionality. So I created a User Exit script (GetCurrentTimeZoneExit.vbs) to query the source OS time zone and set the MDT time zone variable(s).
The Deployment Guys : Setting MDT Time Zone Variables from the Source OS Time Zone
Before I became a “Deployment Guy”, I used to be an “Active Directory Guy” and worked on quite a few Active Directory deployments and migrations. When users, groups, and computers are migrated to a new domain, the resources (files, shares, user profiles, etc.) need to have the permissions on them changed so that the migrated accounts can access them as before. If users/groups are migrated before the resources, they can be migrated with SID History (the SID of the old accounts are placed in the sIDHistory attribute of the new account) to allow access to resources before the “security translation” of permissions is completed.
The Deployment Guys : Creating a SID Mapping File with Windows PowerShell
Windows Vista (and later) all have IPv6 enabled by default. However, in Windows Vista/Server 2008 (SP2 or earlier) the IPv6 adapter is reinstalled in some scenarios. Combined with driver hosting, Windows Vista will enumerate the remote driver store each time this occurs. So now you have the network guys complaining that Windows Vista systems are utilising the network excessively.
The Deployment Guys : Awesome feature with a catch
Below is a list of useful links when it comes to Deployment (MDT 2010 and SCCM), USMT 4.0, Activation, Application Compatibility, and Boot to VHD on several Microsoft related websites. These links can change from time to time, but are a good start for getting your environment ready for Windows 7 or other deployments.
Ask the Core Team : Windows 7 Useful Links
Levi Stevens posted a blog entry today describing a workaround for an issue with ConfigMgr SP2 and USMT 4.0 that causes USMT to not capture all of the user state information.
Michael Niehaus' Windows and Office deployment ramblings : Workaround posted for ConfigMgr SP2 issue with USMT 4.0
I was asked by our Support folks to let you know about an issue that effects Windows 7 when you try to set the desktop wallpaper through Group Policy. I am blogging this on the Deployment Guys blog because the issue can be avoided by a configuration item in the image build.
The Deployment Guys : Windows 7 RTM Issue with Group Policy Enforced Wallpaper
The User State Migration Tool (USMT) is an extremely powerful and essential piece of an Operating System Deployment. With the release of the Windows AIK for Windows 7, USMT 4.0 was made available and includes many great new features such as hard-link migration (for more information on what’s new in USMT 4.0 see this article). MDT 2010 integrates USMT directly into the task sequence for both Lite Touch Installations and Zero Touch Installations. There have been several questions since MDT 2010 was released on how USMT works with MDT and how all of the pieces fit together.
Understanding USMT with MDT 2010 « Xtreme Deployment
The Office 2010 Beta went public late last night so you might be wondering how to deploy it with MDT 2010.
Installing Office 2010 Beta with MDT 2010 « Xtreme Deployment
I’m working on a Windows XP to Windows 7 migration project (I think we’ll all be working on those for the next couple of years!) using a standalone MDT 2010 solution. Overall it’s been working great and the improvements in MDT over each version have resulted in a really impressive deployment platform.
USMT Issues with MDT 2010 | System Center Ideas