Chris Nackers

MDT

If You Use $OEM$ and MDT 2012, Some Things You Need to Know

2012-08-29

From the archive (2012). Written for the tools of the time, so some details may be out of date.

Michael Niehaus has a post up about some changes in MDT 2012 that effect the behavior of the $OEM$ method. I’ve had a few posts on $OEM$ in the past, and you find those here.

Read his full post here.

I mentioned in the blog post at http://blogs.technet.com/b/mniehaus/archive/2012/07/21/mdt-2012-update-1-always-applying-images-with-imagex.aspx that MDT 2012 Update 1 no longer uses SETUP.EXE to install Windows 7 and above.  One side effect of this is that $OEM$ folders are no longer going to be copied, since that was something that SETUP.EXE did that the MDT LTIApply.wsf script doesn’t handle.

I’ve never been a big fan of using the $OEM$ folder structure, as it’s just as easy to add explicit XCOPY steps into the task sequence.  But for those of you out there that are using them, you can leverage the attached script (see the attachment link below) in your task sequence to do that.