ConfigMgr 2012 RC2 / MDT 2012 Issues

I’m now just starting to be able to commit some more time to taking a good peek under the hood of Configuration Manager 2012 Release Candidate and as I come across interesting features or, er, not so interesting “features” then I’ll throw them quickly into this blog post.

  • Capture Media not working – TSMBAutoRun.exe does not seem to do anything for me.  I have tried regenerating the capture media iso but so far nothing seems to happen when I try to capture a running OS.  If I use capture media from my old ConfigMgr 2007 environment the wizard launches fine.  Performing a Capture using an automated Build and Capture Task Sequence still seems to be OK, but I prefer to inspect, patch, tweak, clear logs, remove temp files and otherwise manually refine my reference OS before I capture it.
  • Bitlocker Partitioning – Partitioning has always been a sore point for migrations and it is interesting to see that Microsoft now have a partitioning step for the New Computer scenario that creates a partitioning structure suitable for Bitlocker.  I have implemented this method myself in the past, however recently I changed to creating only a single partition initially and then utilising the ZTIBde.wsf script to do the Bitlocker drive configuration later in the task sequence – which leaves the OS partition as the first partition on the disk and makes life easier when refreshing.  In the new MDT 2012 Client Task Sequence Template a 512MB BDEDrive partition is created at the start of the disk and the remainder of the drive is partitioned and assigned the OSDisk variable.  The subsequent Apply Operating System Image step is configured to apply to the OSDisk variable, which is fine, however, from experience I know that there can then be problems when attempting to perform a Refresh due to the lack of the OSDisk variable as there is no partitioning step.  I’m just starting to look at this to see if Microsoft have improved or implemented something I can’t see which is clever enough to figure out the correct drive to apply the OS Image to during refresh – otherwise we have to use a custom script just after rebooting into WindowsPE to detect on which drive letter the existing OS is living on and then set the OSDisk variable accordingly for the Apply Operating System Image step to use.  ** Update – Microsoft seem to have taken care of this with a revised ZTIUtility.vbs that now has a function for determining the correct partition to apply the Operating System image to and setting the OSDisk variable accordingly. ** – This is a very welcome addition.
  • USMT Hardlinking option with MDT 2012 Task Sequence – It is good to see that you can now check options in the Capture User State Task Sequence step UI to enable local state captures to use hardlinks, however this option should not be ticked when using an MDT 2012 Client Task Sequence as the “Determine Local or Remote User State” Task Sequence step employs the ztiuserstate.wsf which will, where possible, append the /hardlink and /nocompress options to the Scanstate.exe command line automatically.  If the option is ticked, the options will be duplicated on the resulting command line and the Capture User State step will fail.
  • Driver Importing – I don’t seem to be able to have the option to import drivers into sub-folders within the Drivers node – thus everything so far has to be imported at the root level and then moved afterwards.
  • BGInfo Backgrounds – The MDT 2012 Toolkit files package does not contain the WindowHide.exe and the ZTISetBackground.wsf script no longer hides the FirstUXWnd – this means that once you are out of the initial Windows PE phase you can no longer see your custom BGInfo backgrounds/custom wallpaper.  I have yet to try re-including this functionality.  MDT 2012 Release Candidate now includes the WindowHide.exe – yaay!

More to come…