|
|
Text/HTML
|
 |
|
On March 21, the first day of MMS 2011, I announced the immediate availability of the Deployment Research blog and Deployment Research Facebook page. Sites filled with video-tutorials on how to deploy operating systems. Information about this new site, as well a bunch of other deployment related community sites was by the way also printed (thank you FedEx) and put in the attendee-bag (Thank you Microsoft) for every MMS 2011 attendee, about 4000 people.
This also means that the deployvista.com blog will not be much active anymore. It will still exist, but the content will gradually be migrated over to the new site, cleaned-up and converted into the new format…
Happy deployment, and I hope to see you online in the forums…
Regards / Johan Arwidmark
Microsoft MVP – Setup & Deployment
|
|
 |
|
|
Blog_List
|
|
|
|
|
|
|
Blog_Archive
|
|
|
|
|
|
|
New_Blog
|
|
|
You must be logged in and have permission to create or edit a blog.
|
|
|
|
|
Using the $OEM$ folder with SCCM 2007 OS Deployments
|
|
|
Location: Blogs Johan Arwidmark |
 |
| Posted by: johan |
10/6/2008 |
So you want to add the $OEM$ folder to your SCCM 2007 OS Deployments?
Well, if you just add the $OEM$ folder to the package (any location) it will be skipped... The reason is because the "Setup Windows and ConfigMgr" action adds (or overwrites) the OemFilesPath=C:\_SMSTaskSequence\OSD\$OEM$ value in unattend.txt before starting Winnt32.exe
The workaround is simple. Just copy your $OEM$ folder to C:\_SMSTaskSequence\OSD as a Custom Action before the "Setup Windows and ConfigMgr" (You will have to create the OSD subfolder in C:\_SMSTaskSequence first)
If you add a well formatted cmdlines.txt file to C:\_SMSTaskSequence\OSD\$OEM$ it is smart enough to merge your cmdlines settings with its own settings (the OSDSETUPHOOK.)
If you need a sample script for copying the $OEM$ directory, check out this nice entry
Can you use $OEM$ Files with SCCM 2007 OS Deployments?
http://blog.project84.net/2008/10/16/CanYouUseOEMFilesWithSCCM2007OSDeployments.aspx |
|
| Permalink |
Trackback |
Comments (3)
|
Re: Using the $OEM$ folder with SCCM 2007 OS Deployments |
By jamierthompson on
12/7/2009 |
| Im using SCCM 2007 R2 SP2 and MDT 2010 and I'm having trouble getting the files in C:\_SMSTaskSequence\OSD\$OEM$ to merge during the task sequence. You mention if you add a well formatted cmdlines.txt it should be smart enough to merge, do you have an example of one, or do I need another TS variable to include the path for the OSDSETUPHOOK? |
|
|
Re: Using the $OEM$ folder with SCCM 2007 OS Deployments |
By VVG on
7/9/2010 |
Can you use $OEM$ Files with SCCM 2007 OS Deployments?
http://blog.project84.net/2008/10/16/CanYouUseOEMFilesWithSCCM2007OSDeployments.aspx
-----Firstly, Thank you so much for the post. I am unable to acess the above link. I get HTTP 404. Please help. |
|
|
Re: Using the $OEM$ folder with SCCM 2007 OS Deployments |
By VVG on
7/10/2010 |
I am using SCCM SP2 with R2. Here is what I did since I was not able to find the script to copy the OEM folder
I copied $OEM$ to referrence machine's C:\ then sysprepped and captured image. This Reference machine is a virtual PC.
I am now applying to this image to a Dell Optiplex 745 target.
In my task sequence I run below batch file that copied the $OEM$ folder to C:\_SMSTaskSequence\OSD
---------
setlocal
REM Step 1
mkdir c:\_SMSTaskSequence\OSD
mkdir c:\_SMSTaskSequence\OSD\$OEM$
REM Step2
xcopy /E/Y/v C:\$OEM$ C:\_SMSTaskSequence\OSD\$OEM$
-------------
it executes all the steps fine but it reboot afer Setup windows and Configmgr client to a Blue screen 0X7b.
Before it rebooted and bluescreened I did verify in the command prompt that $OEM$ folder and its content was successfully copied to C:\_SMSTaskSequence\OSD.
I am very helpless. any help is very appreciated.
Thanks again!
|
|
|
|
|
|
Search_Blog
|
|
|
|
|
|
|
|
|