ConfigMgr 2007 with slipstreamed SP2 – Full version, is now available on MSDN for download… Finally…

Install Language Pack offline or online in ConfigMgr 2007 (Zero Touch) fails… Here is the fix…

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/6fb55d1e-f66e-4fda-a940-a918746d66ef

When using MDT 2010 to encrypt additional drives the ZTIBDE.WSF script does not implement the wait for BitLocker to complete… Here is the fix…

http://blogs.technet.com/deploymentguys/archive/2009/10/09/how-to-configure-bitlocker-on-additional-drives-in-a-mdt-2010-deployment.aspx

If you encountered that MDT 2010 Lite Touch or Zero Touch doesn’t capture all system settings with USMT, you are not alone….

It’s a bug in the ZTIUserState.wsf script…

Update! Microsoft has now released a public fix:

Network drives and network printers are not migrated when you use Microsoft Deployment Toolkit 2010 with the User State Migration Tool (USMT) 4.0
http://support.microsoft.com/kb/977565

/ Johan

When starting Refresh, Replace, Sysprep and Capture with MDT 2010 Lite Touch, you may get the following error…

“Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed”

Here is the fix.

http://blogs.technet.com/msdeployment/archive/2009/09/18/fix-for-multiple-connections-to-a-server-or-shared-resource-by-the-same-user-using-more-than-one-user-name-are-not-allowed-problem-with-mdt-2010.aspx

Mark Russinovich and Stephen Rose discuss Windows 4.0… This is funny..

http://blogs.technet.com/stephenrose/archive/2009/11/12/mark-russinovich-and-i-discuss-windows-4-0.aspx

 

 

If you install MDT 2010 on a virtual machine running folder redirection, the setup might stall and never finish…

It looks like this:

The workaround, run the setup with the /passive switch, looks like this

msiexec.exe /i MicrosoftDeploymentToolkit2010_x86.msi /passive

or

msiexec.exe /i MicrosoftDeploymentToolkit2010_x64.msi /passive

/ Johan

You might have noticed when you create entries in bcd using bcdedit, it assigns guid’s to the entry, that you need to reference for any following settings you add.

By using a batchfile and som clever for, do command you don’t have to type in the guid…

Sample batchfile

set BCD-File=C:\Demo\bcd

for /f “tokens=1-3” %%a in (‘Bcdedit /store %BCD-File%  /create /d “WinPE x86” /application osloader’) do set guid1=%%c

Bcdedit /store %BCD-File% /set %guid1% systemroot \Windows

Please note that the second line has been wrapped and should be entered as one command…

/ Johan

The WC Commercial group held a 72-hour film festival for Windows 7 in Seattle last week. 17 film teams in the Seattle area competed.  Rules were to create a 30 second to 2 minute film, targeted to IT Pros. 

Each team picked a different genre from a hat (e.g. Comedy, Music, Parkour, Blast from the Past, etc.), and they had to include the following in their film:

1) A character called “CIO Wiggins”
2) A line of dialog “The guys in IT are going to like this”
3) Mention “Windows 7”

Check out the results: 
http://www.youtube.com/user/Win7FilmFest

My Favorite: Installation
http://www.youtube.com/user/Win7FilmFest#p/u/0/mxtG6s9B3rY

 

After installing KB 974571 the Request State Store action in the Task Sequence fails.  The failure occurs by a NULL value in the ConfigMgr client certificate (friendly name property).

Credit’s goes to Anders Ahl for extensive troubleshooting and a new workaround…

Anyway, after installing KB 974571 you will se the following in the smsts.log file.

Failed to import the client certificate store (0x80092024) OSDSMPClient 2009-10-23 09:15:17 1856 (0x0740)
ClientRequestToMP::DoRequest failed (0x80092024). OSDSMPClient 2009-10-23 09:15:17 1856 (0x0740)
ExecuteCaptureRequestMP failed (0x80092024). OSDSMPClient 2009-10-23 09:15:17 1856 (0x0740)
ExecuteCaptureRequest failed (0x80092024). OSDSMPClient 2009-10-23 09:15:17 1856 (0x0740)

Failed to run the action: Request State Store.
Unknown error (Error: 00002024; Source: Unknown) TSManager 2009-10-23 09:15:17 340 (0x0154)

Workaround #1: Uninstall KB 974571 (patch MS09-056)

Workaround #2: Fix the Certificate

1. On the ConfigMgr Server, start a mmc, add the Certificates snap-in, select computer account, and select the local computer. 
    
2. Expand certificates, expand SMS, and expand certificates 
    
3. Open the SMS Encryption Certificate, click the Details tab, click Edit Properties, and change the Friendly Name to SMS Encryption Certificate v2, click OK twice. 
    
4. Open the SMS SMP Encryption Certificate, click the Details tab, click Edit Properties, and change the Friendly Name to SMS SMP Encryption Certificate v2, click OK twice. 
    
5. Open the SMS Signing Certificate, click the Details tab, click Edit Properties, and change the Friendly Name to SMS Signing Certificate v2, click OK twice.