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.
- 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.
- 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.
Just do the changes, it's quite quick. An exported MDT task sequence will contain quite many references to packages you don't have so it's easier just to do these changes.
Any chance somebody could export a task sequence (of course stripped from any confidential information)?
Fixed in MDT 2013 preview, btw.
Thanks, it's a known issue.
We have found additional configuration missing. Inside task Format and Partition Disk (UEFI) variable OSdisk is missing for OSDisk (Primary) partition and because this apply operating system image fails during UEFI deployment scenario.
Check the log files on the client to see if the remote connection values are written.
I'm using MDt 2012 U1 monitoring / SCCM 2012 SP1 on Windows 2008 R2. I've applied your tip renaming the folder to V7 and the viewer starts. However when i try to connect to a system it times out with a message: Attemt to connect remotely failed. When i connect manually to the system with the details provided by the DaRT Remote Connection tool i can connect. It seems that the connection details are not correctly passed over to the DaRT Connection Viewer. Have you got any idea where to start troubleshooting?
The first tip in this post looks like exactly the problem I came across recently when testing deployment of an image with SCCM2012 SP1 beta. I'll give it a shot, hopefully that is all it takes to fix my issue!