-
OK, so if I move your $OEM$ folder to the I386\$OEM$, integrate it with my $OEM$ stuff I only have to modify the two sets of code that erik_demon mentioned to point to that folder. And the OEM (not $OEM$) folder...what's your recommendation then? Do I move it as well? I smell a FAQ...
-
OK, let me show my cards here...I'm building an unattended XP install to be installed using RIS or SMS Operating System Deployment Feature Pack. Which do I need? And if I do it by network which requires it IN i386, will the BTS_DriverPack integration stuff fail? What should I set my OemFilesPath to in order to force $OEM$ to be in the root of the CD? Thanks peeps! John
-
Hmm, in reading the Windows Deployment documentation (ref.chm I think) it says the $OEM$ needs to be IN the i386 unless you specify a different location in the "OemFilesPath" value under the UNATTENDED section...Is that not true? If I move all of my stuff to %CDROM%\$OEM$ do I need to specify a differen OemFilesPath value? The Microsoft documentation seems to contradict what that link says about the OEM folders...
-
So, I'm a little confused. After using method 2 I have $OEM$ in the root of CD. I have my own $OEM$ folder for my custom unattended install in i386\$OEM$. Can I move your $OEM$ to i386\$OEM$ and combine it with mine? Is there something that requires your $OEM$ to be in the root of the CD or what? Thanks! John
-
I've got an unattended Server 2003 disk created using XPCREATE. It works great, installs all of my hotfixes and registry tweaks and pretty much does what I'm looking for with one exception: The adapter keeps defaulting to DHCP even though the WINNT.SIF I created (using setupmgr) specifies a static IP address and DHCP=No. Any thoughts? It's obviously seeing my WINNT.SIF cuz other parts of it complete properly. Thanks! winbatch Here's my WINNT.SIF