Windows 2003 Server Deploy - $OEM$ question!

[Guest]

H

I am trying to do a custom installation CD for Windows 2003 server. However, i have read all articles ( so it feels ) about the $OEM$ folder structure. OemPreInstall = Yes is set..... the folder structure is with the $OEM$ folder and the subfolders at the same level as the i386 folder on the CD ( as specified at http://unattended.msfn.org/ ) even tho this is for WinXP. I have also read the MS article: http://support.microsoft.com/?kbid=234536 which says it will not work. After completing the setup of Win2003, the $OEM$ structure is not on harddrive

So my question is: Is this a new "power feature from MS" ( as in a bug" ) or is it that this will not work on Windows 2003 custom CD installation even though it works fine on Win2K SP4 or later, XP etc etc ???? Or what am I doing wrong

P.S I have not specified OemfilesPath, just because it doesnt say that I have to..

 

[Oli Restorick [MVP]]

Hi there

Article 234536 is mostly wrong. The bit that doesn't work (in 2000/XP at
least) is the textmode driver support for mass storage devices. The rest of
the OEM functionality should work.

I must admit, I haven't tried this with Windows Server 2003, but I probably
should try.

Have you checked the resources on the Windows Server 2003 CD (specifically
the deploy.cab file) for any clues?

Oli

HI

I am trying to do a custom installation CD for Windows 2003 server.

However, i have read all articles ( so it feels ) about the $OEM$ folder
structure. OemPreInstall = Yes is set..... the folder structure is with the
$OEM$ folder and the subfolders at the same level as the i386 folder on the
CD ( as specified at http://unattended.msfn.org/ ) even tho this is for
WinXP. I have also read the MS article:
http://support.microsoft.com/?kbid=234536 which says it will not work. After
completing the setup of Win2003, the $OEM$ structure is not on harddrive!

So my question is: Is this a new "power feature from MS" ( as in a bug" )

or is it that this will not work on Windows 2003 custom CD installation even
though it works fine on Win2K SP4 or later, XP etc etc ???? Or what am I
doing wrong?