Copying $OEM$ files and folders with MDT 2012 Update 1

2012 1 no longer uses SETUP.EXE to install 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 LTIApply.wsf doesn’t handle.

I’ve never been a big fan of using the $OEM$ 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 (CopyOEM.zip) in your task sequence to do that.

To set this up, first copy the into your share. Then, add a new step to the task sequence right after the “Install Operating System” step to run the script. It should look like this:

CopyOem

Now, it will follow the original logic for locating the appropriate $OEM$ to use, checking in this order:

  • %DeployRoot%\Control\%TaskSequenceID%\$OEM$
  • %SourcePath%\$OEM$
  • %DeployRoot%\%Architecture%\$OEM$
  • %DeployRoot%\$OEM$

where %DeployRoot% is the path to the share, %TaskSequenceID% is the ID of the task sequence (e.g. WIN8), %SourcePath% is the path within the share for the operating system being used, and %Architecture% is either X86 or X64, depending on the being used.

Once it finds a folder, it will look for two folders in that $OEM$ folder and copy them to the appropriate place for the new OS:

  • $1 will be copied to the root of the volume that the new OS was applied to.
  • $$ will be copied to the folder on the volume that the new OS was applied to.

The doesn’t deal with any other folders because it’s too messy to do that from within PE – drive letters aren’t the same as what they would end up being in the full OS

Download: CopyOEM.zip

Source: Copying $OEM$ files and folders with MDT 2012 Update 1

Translate »
%d bloggers like this: