OEM folder
-
Friday, October 05, 2012 11:54 AM
Dear All,
we are using in our comapny two sometimes 3 different branches model of laptops/desktops ( HP, Dell, IBM)what i need to do is creating OEM OS for those machines,
can you please explain where i have to add the OEM($$, $!) folder on the MDT?
and is it possible to add Multiply OEM folders in one Image?
thank you
All Replies
-
Friday, October 05, 2012 2:32 PM
MDT 2010 looks in the following locations within the deployment share, in the order specified, to find an $OEM$ folder:
· Control\task_sequence (where task_sequence is the name or ID of the task sequence that MDT 2010 is installing). Create $OEM$ folders in this location to create a custom folder for each build.
· Operating Systems\Name (where Name is the name of the operating system MDT 2010 is installing). Create $OEM$ folders in this location to create a custom folder for each operating system.
· Platform (where Platform is either x86 or x64). Create $OEM$ folders in this location to create a custom folder for each platform.
· $OEM$, which is at the root of the deployment share and is the default $OEM$ folder if a folder is not found in the previous locations.
An $OEM$ folder contains supplemental files. The following list describes each folder that you can create within an $OEM$ folder to organize these files:
· $$. Windows Setup copies the contents of this folder to %SystemRoot% on each destination computer. It replicates all the folders, subfolders, and files that this folder contains in the %SystemRoot% folder of each destination computer. For Windows Setup to copy a file to %SystemRoot%\System32 on each destination computer, for example, put the file in $OEM$\$$\System32.
· $1. Windows Setup copies the contents of this folder to %SystemDrive% on each destination computer. It replicates all the folders, subfolders, and files that this folder contains in the %SystemDrive% folder on each destination computer. This is typically drive C on most computers.
· Drive. Drive is a drive letter (C, D, E, and so on). Windows Setup copies the contents of this folder to the root of the corresponding drive on each destination computer. It replicates all the folders, subfolders, and files that this folder contains in the corresponding drive during the setup process. For example, Windows Setup copies any files put in $OEM$\D to the root of drive D on each destination computer.
Microsoft recommends that these folders not be used. The folders rely on a very specific disk configuration on the destination computer. Use $1 to represent %SystemDrive%, instead. In most installations, $OEM$\$1 and $OEM$\C write to the same location: the root of drive C.
· TEXTMODE. For Windows XP and Windows Server 2003, this folder contains hardware-specific files that Windows Setup and text-mode setup install on the destination computer during the text-mode phase of the installation process. These files may include OEM HALs, mass-storage device drivers, and the Txtsetup.oem file. The Txtsetup.oem file describes how to load and install these files. List these files in the [OemBootFiles] section of the answer file.
Per this article: http://myitforum.com/cs2/blogs/cnackers/archive/2010/10/29/copy-content-to-target-computers-using-oem-folders.aspx
-
Friday, October 05, 2012 2:50 PM
MDT 2010 looks in the following locations within the deployment share, in the order specified, to find an $OEM$ folder:
· Control\task_sequence (where task_sequence is the name or ID of the task sequence that MDT 2010 is installing). Create $OEM$ folders in this location to create a custom folder for each build.
· Operating Systems\Name (where Name is the name of the operating system MDT 2010 is installing). Create $OEM$ folders in this location to create a custom folder for each operating system.
· Platform (where Platform is either x86 or x64). Create $OEM$ folders in this location to create a custom folder for each platform.
· $OEM$, which is at the root of the deployment share and is the default $OEM$ folder if a folder is not found in the previous locations.
An $OEM$ folder contains supplemental files. The following list describes each folder that you can create within an $OEM$ folder to organize these files:
· $$. Windows Setup copies the contents of this folder to %SystemRoot% on each destination computer. It replicates all the folders, subfolders, and files that this folder contains in the %SystemRoot% folder of each destination computer. For Windows Setup to copy a file to %SystemRoot%\System32 on each destination computer, for example, put the file in $OEM$\$$\System32.
· $1. Windows Setup copies the contents of this folder to %SystemDrive% on each destination computer. It replicates all the folders, subfolders, and files that this folder contains in the %SystemDrive% folder on each destination computer. This is typically drive C on most computers.
· Drive. Drive is a drive letter (C, D, E, and so on). Windows Setup copies the contents of this folder to the root of the corresponding drive on each destination computer. It replicates all the folders, subfolders, and files that this folder contains in the corresponding drive during the setup process. For example, Windows Setup copies any files put in $OEM$\D to the root of drive D on each destination computer.
Microsoft recommends that these folders not be used. The folders rely on a very specific disk configuration on the destination computer. Use $1 to represent %SystemDrive%, instead. In most installations, $OEM$\$1 and $OEM$\C write to the same location: the root of drive C.
· TEXTMODE. For Windows XP and Windows Server 2003, this folder contains hardware-specific files that Windows Setup and text-mode setup install on the destination computer during the text-mode phase of the installation process. These files may include OEM HALs, mass-storage device drivers, and the Txtsetup.oem file. The Txtsetup.oem file describes how to load and install these files. List these files in the [OemBootFiles] section of the answer file.
Per this article: http://myitforum.com/cs2/blogs/cnackers/archive/2010/10/29/copy-content-to-target-computers-using-oem-folders.aspx
Thank you so much,
i have create $OEM$ folder on each squence however when i deploy the installation on OEM hardware it doesn't pick up the OEM !
Note: i am using multiple $OEM$
-
Tuesday, October 09, 2012 12:29 PM
Actually I think you might be going down the wrong path on that (pun :P ) . $OEM$ folders are pretty much deprecated in MDT, there are a couple different batter ways of handling platform or vendor specific software or driver adds.
This is common:
http://www.toddlamothe.com/deployment/driver-management-mdt-2010.htm
http://blogs.technet.com/b/askcore/archive/2012/03/07/how-to-manage-out-of-box-drivers-with-the-use-of-selection-profiles-in-microsoft-deployment-toolkit-2010-update-1.aspx
Also any task in the task sequence can be set to run conditionally based on any number of variables, %MAKE% and/or %MODEL% being two of them.
-
Tuesday, October 09, 2012 3:00 PM
Dear JoeZeppy
thank you for the answer, however it talking about drivers and i need OEM wallpapers and activation on the $$ folder to be copied for the OEM hardware i have!
thank you
-
Tuesday, October 09, 2012 4:55 PM
Then your options are to have a separate task sequence for each make, and put your $oem$ folder in the Control\<Task Sequence> folder for each, or to write some type of install/copy script task and use the conditionals as pictured above to only run the task if the %make% or %model% matches.
I have a few tasks that only run if the system is a laptop, or only if it's a VM. Setting them to run only if %MAKE% = HP is just as easy.
.png)
