Can SCCM 2012 OSD deploy to VHD using MDT 2012 integration?

By now you may have heard that support for deploying and booting to VHDs is integrated into Microsoft Deployment Toolkit 2012. If not, Maik Koster has a great article over at you should check out! One thing we have been working on lately is whether there is a way to use ConfigMgr’s OSD feature to deploy to VHD. With the tight integration between MDT and SCCM, you might expect this to be fairly straightforward.

Stay tuned, because before going on we should clear something up – why would you want to boot physical hardware to a VHD in the first place? One reason that Maik Koster points out in the article above is the ability to use differencing disks. A differencing disk is great for testing updates or running a demo – it’s just another VHD that treats the original VHD as a parent, keeping changes separate from the original. This way, you can boot to the differencing disk to try something out, and if it goes poorly you can just fall back to the original disk. Maik covers some other benefits in his article as well – you really should read it!

As it turns out, there is no way for SCCM to deploy to VHD natively at this time. Now, that’s not to say you couldn’t implement a solution that uses task sequence commands to deploy a pre-existing VHD, but the new VHD deployment templates in MDT2012 do not transfer over. Deploying a pre-existing VHD also resigns you to using a “thick” image, preventing exploitation of the real killer features in OSD.

Are there other options? In the course of our research we’ve identified some possibilities. One would simply use MDT 2012 to deploy a basic reference image including the ConfigMgr client to selected hardware using the deploy to VHD capability. From here, SCCM could be set up to quickly run a task sequence that layers on applications and customizations – in effect, this would split the normal deployment task sequence into two parts, the first run by MDT, and the second by SCCM. While this could potentially run smoothly, the fragmentation inherent in the design as well as considerations surrounding whether MDT and SCCM will both need PXE capability could eliminate this as a viable solution.

Alternatively, a more complex option would be to modify a deployment task sequence within SCCM to create and mount a VHD while in the Windows PE environment, and then deploy the reference image and execute task sequence steps as you normally would with a physical disk. It does appear something similar to this may have been done successfully with SCCM 2007. In addition, this tutorial could provide a valuable resource. This strategy is definitely not supported by Microsoft – in fact, after obtaining expert opinion we have ruled this out as an option in our case.

We’re still working on this one, so look for further info to come!



Contact Us

On Key

More Posts

Mastering Azure AD Connect - A Comprehensive Guide by WME
Active Directory

Mastering Azure AD Connect – A Comprehensive Guide

Modern businesses are fast moving toward cloud-based infrastructure. In fact, cloud-based business is not just a trend anymore but a strategic necessity. Microsoft’s Azure Active Directory (Azure AD) has become a frontrunner in this domain. It

Read More »
Security Best Practices in SharePoint
Office 365

Security Best Practices in SharePoint

Microsoft SharePoint is an online collaboration platform that integrates with Microsoft Office. You can use it to store, organize, share, and access information online. SharePoint enables collaboration and content management and ultimately allows your teams to

Read More »
The Ultimate Guide to Microsoft Intune - Article by WME
Active Directory

The Ultimate Guide to Microsoft Intune

The corporate world is evolving fast. And with that, mobile devices are spreading everywhere. As we venture into the year 2024, they have already claimed a substantial 55% share of the total corporate device ecosystem. You

Read More »
Protecting Microsoft 365 from on-Premises Attacks
Cloud Security

How to Protect Microsoft 365 from On-Premises Attacks?

Microsoft 365 is diverse enough to enrich the capabilities of many types of private businesses. It complements users, applications, networks, devices, and whatnot. However, Microsoft 365 cybersecurity is often compromised and there are countless ways that

Read More »
Be assured of everything

Get WME Services

Stay ahead of the competition with our Professional IT offerings.