The answer is yes! Incidentally, is there really any limit to what you can do with ConfigMgr?? Well I suppose that is like asking, "How much wood could a woodchuck chuck if a woodchuck could chuck wood?", but anyway let's move on.
My first clue for solving this came from deployvista.com, "Using the $OEM$ folder with SCCM 2007 OS Deployments". To summarize you need to place your $OEM$ files into C:\_SMSTaskSequence\OSD\$OEM$ in order for Windows Setup to use the files. Here is what I did:
The guts of the script is pretty simple stuff and it works because when you set a Package in a Run Command Line Task the current directory is the path to whatever package you've select. In this case the current directory is the MDT Settings package containing our $OEM$ files.
'//---------------------------------------------------------------------------- '// See if we can find the $OEM$ Directory '//---------------------------------------------------------------------------- sDest = OEnvironment.GetOSDV4("_SMSTSMDATAPATH") & "\OSD\$OEM$" oLogging.CreateEntry "$OEM$ Files will be copied to " & sDest, LogTypeInfo '//---------------------------------------------------------------------------- '// Make sure the Destination exists '//---------------------------------------------------------------------------- MKDir sDest '//---------------------------------------------------------------------------- '// Get the Source Location and Copy the files '//---------------------------------------------------------------------------- sSource = oShell.CurrentDirectory & "\$OEM$" oLogging.CreateEntry "$OEM$ Files will be copied from " & sSource, LogTypeInfo 'Copy the folder oFSO.CopyFolder sSource, sDest
Remember Me
a@href@title, strike
Page rendered at Wednesday, January 07, 2009 2:46:05 PM (E. Australia Standard Time, UTC+10:00)
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.