2:47 pm in Uncategorized by nsienaert
At MMS we could hear that the MDT team will try to release MDT 2012 RTM 30 days after the RTM release of SCCM 2012.
Last week the Beta1 was released. Let’s have a sneak peak.
With this version there is support of:
- The SCCM App Model & UDA
- Integration with the SCCM 2012 Console
- New UDI components (new wizard & Designer) and more customization will be possible
- Support UEFI
- Support of new OSes: Windows POSReady7 & Windows ThinPC
- Cross-platfrom deployment (Install x64 OS from x86 windows PE) The other combination, booting from an x64 boot image and deploying an x86 OS, isn’t supported by Windows Setup.
- Deploy to VHD – creating a VHD file during the task sequence that can then be used for booting the OS (“boot from VHD”).
Maybe you are wondering if there are changes on USMT, Windows PE and WAIK. Well no, only bug fixes. WAIK (USMT is part of WAIK) is depending on Windows releases not MDT releases, that’s why.
The MDT Team wants to remove support of Windows XP & Server 2003 but SCCM 2012 does still support XP SP3, so probably MDT will 2012 still support XP SP3 as Source OS, not as Target OS.
Features that will be added in next releases:
- Integration of Windows RE (Set Recovery partition during OS Process)
- Integration with MDOP tools like App-V and DaRT
- Powershell support in Task Sequence
- LTI Facelift
At first glance, visually not much has been changed in the SCCM console. One button has been added to the Tab Bar to start the MDT Task Sequence wizard.
Once we have created an MDT Task Sequence via the wizard, we don’t notice much changes in the Task Sequence.
Probably the 2 most biggest changes are:
- USMT has more GUI options
2. The New App Model
Note that the MDT Team added an extra script before the Install Application step to “workaround” something. Application variables end up with 2 digit suffixes (ex. Applications01), MDT expects 3 digit suffixes (ex. Packages001). The script is making a 3 digit list and convert it to a 2 digit list so SCCM can install the applications.
Also in the MDT LTI Workbench no much changes can be observed.
- Integration of the new App Model (note: also ConfigMgr Packages can still be used)
2. The Deploy to VHD Templates. (only supported in LTI scenarios)
So, now we have looked into the changes, let’s deploy a Bare Metal image via the MDT Wizard in the SCCM Console.
Once I finished the MDT wizard, it failed immediately with following error:
Creating boot image.
Generating boot image.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.Exception: Unable to mount image C:\Users\ADM-NS~1\AppData\Local\Temp\2\winpe.wim to C:\Users\ADM-NS~1\AppData\Local\Temp\2\PE20_mount.x86 —> System.ComponentModel.Win32Exception: A required privilege is not held by the client
— End of inner exception stack trace —
at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
From my experience I remember that the deployment tools of WAIK like to be executed with “Run as Administrator”.
So I have restarted my SCCM Console with “Run as Administrator”, as from now the image could be mounted correctly and the wizard finished successfully.
Stay tuned for more blogs that go deeper into the MDT Topic.
Till next time!
Nico Sienaert (twitter: nsienaert)