I'm a big fan of integrating MDT 2012 Update 1 with ConfigMgr 2007/2012, not only for all the OSD enhancements, but also for the development framework and its ability to call external scripts, databases, web services and much more…
That being said I'm not all that excited about some of the changes that MDT 2012 Update 1 brought in regards to the standard client task sequence template for ConfigMgr. In Update 1 Microsoft merged the UDI client template with the normal client template, and if you thought the old template was big, think again J
Anyway, the new template, that is only good, can be made great!
Here are the changes I propose to a SCCM 2012 SP1 task sequence created by the new MDT 2012 Update 1 standard client template:
- Change the OSDPreserveDriveLetter from False to True. That will configure SCCM 2012 SP1 to honor the drive letter setting in your reference image. Meaning if the drive letter was C:, it will still be C: when deployed.
The OS ending up on the E drive without the OSDPreserveDriveLetter value set to True. New "feature" when deploying with MDT 2012 Update 1 and SCCM 2012 SP1.
Setting the OSDPreserveDriveLetter value to True.
- Set the password for the local administrator, by default the template enables the admin account and sets it to blank (not good). Please note that UDI requires the administrator account to be enabled, but not if you don't use UDI. Assigning a local password is also useful when setting up the initial deployment solution, so that you for example can login locally to troubleshoot join domain issues etc.
Set a password for the local administrator in the task sequence, or disable if not using UDI.
- Always configure an OU in Apply Network Settings. MDT can only update the MachineObjectOU value if you set it to something first.
Specify an OU in the Apply Network Settings action, and no, the Computers "OU" is not an OU, it's a container. Don't use it, never, ever.
/ Johan
More ...