Microsoft KB Archive/229725

{|
 * width="100%"|

Using Cmdlines.txt and $oem$ Folder Structure with Remote Install Images

 * }

-

The information in this article applies to:


 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional
 * Microsoft Windows 2000 Server

-

SUMMARY
You can use the Cmdlines.txt file and the $oem$ folder structure to run commands, copy files, and add new drivers during an automated Setup. You can use these features by:


 * 1) Creating a distribution share on a server (ServerName\ShareName\Dist).
 * 2) Copying the contents of the I386 folder from the CD-ROM to the Dist folder.
 * 3) Creating the $oem$ folder below the Dist folder.

During Setup, the files can then be located and used. However, using this structure with Remote Install images requires that the $oem$ folder be placed one level up.

MORE INFORMATION
During a normal unattended Setup with the OemPreinstall key set to "Yes" in the [unattended] section, Setup looks for these files using the following path:

"\$win_nt%.~ls\$oem$" However, the Remote Install image path is structured as follows:

"\\%ServerName%\Reminst\Setup\English\Images\Win2000.pro\I386" Placing the \$oem$ folder below \i386 in the above path results in the following location during Setup, which is not found:

"\$win_nt$.~ls\I386\$oem$" To correct this situation, place the $oem$ folder at the same level as the \I386 folder. NOTE: The default template for Remote Install has the Oempreinstall key set to "No." Make sure the value is changed to "Yes."

Additional query words:

Keywords : kbenv kbsetup

Version : WINDOWS:2000

Platform : WINDOWS

Issue type : kbinfo

Technology :