- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Re: $OEM$ folder structur moved in RDP 1.40 integr...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2003 06:52 AM
тАО08-25-2003 06:52 AM
$OEM$ folder structur moved in RDP 1.40 integration module
Simply copying this folder structure to the C:\ drive and then leaving it there after the install seems armature to me. By default, the Microsoft Unattended process looks for this $OEM$ folder structure to reside beneath the source install location (i386). Not only that, certain files in the unattended install are expected to be there, like cmdlines.txt or the bmp file used to brand the install. I have yet to find an alternate location that this file will be automatically picked up by the install process.
Now files I have created under the i386\$OEM$ don't get picked up by the install, or copied to the specified locations like $1 (system32). I have to setup a manually procedure to take care of this. Am I doing this wrong?
One last thing, if you are going to copy a folder to the C:\ drive of the server, why call it $OEM$? I mean, choose your own name so it is less confusing. How about c:\support. That way people won't expect that they can drop files and directories into the $OEM$ folder and have them work like any other unattended install.
Feedback on why this was done would be great. If I am not accurate in my findings, I would appreciate the correction as well.
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2003 06:17 AM
тАО08-27-2003 06:17 AM
Re: $OEM$ folder structur moved in RDP 1.40 integration module
This directory cannot be renamed, it is simply an alternate location that the instalation process looks to foir drivers that are not on the Windows media.
OemFilesPath
Value:
Specifies the path to the \$OEM$ folder (containing OEM files) if it does not exist under the i386 folder of the distribution share point. The path can be a UNC name.
For more information about the \$OEM$ folder, see the Microsoft Windows 2000 OEM Preinstallation Kit (OPK) User Guide if you are a computer manufacturer. Otherwise, see the Microsoft Windows 2000 Deployment Guide.
OemPnPDriversPath
Value: "
Specifies the path to folders that contain Plug and Play (PnP) drivers that do not ship on the Windows 2000 CD. The folders must contain all the files necessary to install the particular devices???catalog files, .inf files, and drivers.
For example, if you have a folder called \Drivers with subfolders called \Audio and \Net, you would specify OemPnPDriversPath = "drivers\audio;drivers\net" in the answer file. Setup adds:
??? %systemdrive% to each of the folder names
??? the path for each subfolder to the PnP device search path.
Note When using this parameter, be sure that the folders are available during GUI-mode Setup or Mini-Setup???you can use the \$OEM$\$1 folder structure mechanism for this. For best results, make sure your drivers are signed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2003 07:14 AM
тАО08-28-2003 07:14 AM
Re: $OEM$ folder structur moved in RDP 1.40 integration module
I did get my custom scripts integrated with HP's new way of doing things, I was just curious as to the reason for the change.
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-28-2003 08:54 AM
тАО08-28-2003 08:54 AM
Re: $OEM$ folder structur moved in RDP 1.40 integration module
The reason for keeping the $OEM$ drivers in a different folder from the OS files is that the $OEM$ files change very often to get new driver versions that support the latest ProLiants. The Microsoft Windows files don't change (or only change if you slipstream in a new service pack).
For example, RDP 1.30 had the ss.630 drivers, RDP 1.40 had the SS.640 drivers. Some customers don't want to change the deployment scripts for all their existing servers just because they need new support software to deploy the latest ProLiant. This arrangement gives them that ability.
As we release new versions of the ProLiant Integration Module (PIM), you can retain your customized jobs that use older version of the drivers, or modify the "ss" variable in the deployment jobs to point to the new "ss" tree.
Does that help?
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2003 08:25 AM
тАО08-29-2003 08:25 AM
Re: $OEM$ folder structur moved in RDP 1.40 integration module
Thanks again for the explanation though.