Guest michael Posted July 19, 2007 Posted July 19, 2007 I am trying to building a RIS image that is full automated but I am having one screen that will appear for user interaction. The screen is after the formatting and coping files and the GUI part of the install starts. The screen says, "Welcome to the Windows XP Setup Wizard" I have found that this only happens when I have the OemPreinstall=Yes, set in the Unatteneded section of the restndrd.sif file. If I turn this setting to =Off then the prompt does not happen but I do not get my oem drivers to install. Please let me know what I need to do to remove this prompt from my install. Here is a copy of my ristndrd.sif: [Data] AutoPartition=1 MsDosInitiated="1" UnattendedInstall="Yes" floppyless="1" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" OriTyp="4" LocalSourceOnCD=1 [setupData] OsLoadOptions="/noguiboot /fastdetect" SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [unattended] UnattendMode=FullUnattended ComputerType=Retail OemSkipEula=Yes OemPreinstall=Yes DriverSigningPolicy=Ignore OemPnPDriversPath=Drivers\745\Broadcom;Drivers\745\Video;Drivers\745\Audio;Drivers\745\Chipset; TargetPath=\WINDOWS FileSystem=LeaveAlone NtUpgrade=No OverwriteOemFilesOnUpgrade=No [GuiUnattended] AdminPassword=REMOVED EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=%TIMEZONE% OemSkipWelcomes=1 [userData] ProductKey=REMOVED FullName=REMOVED OrgName=REMOVED ComputerName=%MACHINENAME% [Display] BitsPerPel=32 Xresolution=1280 YResolution=1024 Vrefresh=60 [setupMgr] DistFolder=C:\windist DistShare=windist [identification] JoinDomain=REMOVED DoOldStyleDomainJoin=Yes [Networking] InstallDefaultComponents=Yes ProcessPageSections=Yes [RemoteInstall] Repartition=Yes [OSChooser] Description="Windows Professional XP SP2" Help="This will install Windows Professional in a standard configuration." LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType=Flat
Guest Greg O Posted July 20, 2007 Posted July 20, 2007 Re: RIS OemPreinstall Problems On Jul 19, 4:10 pm, michael <mich...@discussions.microsoft.com> wrote: > I am trying to building a RIS image that is full automated but I am having > one screen that will appear for user interaction. > > The screen is after the formatting and coping files and the GUI part of the > install starts. The screen says, "Welcome to the Windows XP Setup Wizard" > > I have found that this only happens when I have the OemPreinstall=Yes, set > in the Unatteneded section of the restndrd.sif file. If I turn this setting > to =Off then the prompt does not happen but I do not get my oem drivers to > install. > > Please let me know what I need to do to remove this prompt from my install. > Here is a copy of my ristndrd.sif: > > [Data] > AutoPartition=1 > MsDosInitiated="1" > UnattendedInstall="Yes" > floppyless="1" > OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" > OriTyp="4" > LocalSourceOnCD=1 > > [setupData] > OsLoadOptions="/noguiboot /fastdetect" > > SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" > > [unattended] > UnattendMode=FullUnattended > ComputerType=Retail > OemSkipEula=Yes > OemPreinstall=Yes > DriverSigningPolicy=Ignore > OemPnPDriversPath=Drivers\745\Broadcom;Drivers\745\Video;Drivers\745\Audio;Drivers\745\Chipset; > TargetPath=\WINDOWS > FileSystem=LeaveAlone > NtUpgrade=No > OverwriteOemFilesOnUpgrade=No > > [GuiUnattended] > AdminPassword=REMOVED > EncryptedAdminPassword=Yes > OEMSkipRegional=1 > TimeZone=%TIMEZONE% > OemSkipWelcomes=1 > > [userData] > ProductKey=REMOVED > FullName=REMOVED > OrgName=REMOVED > ComputerName=%MACHINENAME% > > [Display] > BitsPerPel=32 > Xresolution=1280 > YResolution=1024 > Vrefresh=60 > > [setupMgr] > DistFolder=C:\windist > DistShare=windist > > [identification] > JoinDomain=REMOVED > DoOldStyleDomainJoin=Yes > > [Networking] > InstallDefaultComponents=Yes > ProcessPageSections=Yes > > [RemoteInstall] > Repartition=Yes > > [OSChooser] > Description="Windows Professional XP SP2" > Help="This will install Windows Professional in a standard configuration." > LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" > ImageType=Flat This may help: You see, once Setup kicks in, it does a quick check to see if it can fire up your network card; for some reason, it won't use the TFTP transfer ability built into PXE to copy the Setup files. As the NIC is newer than the drivers that Setup knows about, Setup can't initialize the card, and stops. But wait-what about that OEMPnPDrivers command? If you put the drivers for the new NIC into $OEM$ and pointed to them with OEMPnPDrivers, then Setup ought to be able to use those drivers, right? Well, not exactly. Windows 2000, XP, and Server 2003 like their drivers digitally signed, and many sets of drivers don't come with digital signatures. You can work around that by adding this line to the ristndrd.sif script: DriverSigningPolicy = Ignore Put that in the [unattended] section. Then put the NIC drivers on the RIS server in $OEM$ as before, but Microsoft recommends a more specific procedure. Create a directory \$OEM$\$1\Drivers\NIC and put the NIC drivers there. Create an OEMPnpDrivers command that looks like OemPnp- DriversPath=\Drivers\Nic in the ristndrd.sif file, and then you ought to be able to get RIS started on a system with a new NIC. (And yes, I did recommend that you keep the names of driver directories short due to the 40-character limit on the OemPnpDriversPath command, but I wanted this text to be clear, so I used a longer name. You'd do fine with a directory named \$OEM$\$1\DR\NIC instead of \$OEM$\$1\Drivers\NIC ..) Apparently a driver has to be in the I386 directory for the text mode portion of Setup to see it, so Microsoft says in Knowledge Base article 246184 that you've got to put the INF and SYS files from the network driver into the I386 directory on the RIS server. You may have to do a bit of experimenting to find out exactly which SYS and INF files you actually need in the I386 directory, because you don't want to have to put oeminfo.inf in I386 -after all, it seems like every board comes with an oeminfo.inf ..
Guest michael Posted July 20, 2007 Posted July 20, 2007 Re: RIS OemPreinstall Problems I have managed to get the Text Mode to work just fine by adding the NIC to the i386 folder. My problem seems to be when the GUI Part of the install starts and shows the user prompt. Again this only happens when I have the OemPreinstall value set to YES. When I have this setting turned on my OEM Drivers work and install properly. Also I do have the DriverSigningPolicy=Ignore. But the User Prompt comes up at the being of the set. But when I turn off OemPreinstall=NO, the prompt does not happen but none of my drivers install. "Greg O" wrote: > On Jul 19, 4:10 pm, michael <mich...@discussions.microsoft.com> wrote: > > I am trying to building a RIS image that is full automated but I am having > > one screen that will appear for user interaction. > > > > The screen is after the formatting and coping files and the GUI part of the > > install starts. The screen says, "Welcome to the Windows XP Setup Wizard" > > > > I have found that this only happens when I have the OemPreinstall=Yes, set > > in the Unatteneded section of the restndrd.sif file. If I turn this setting > > to =Off then the prompt does not happen but I do not get my oem drivers to > > install. > > > > Please let me know what I need to do to remove this prompt from my install. > > Here is a copy of my ristndrd.sif: > > > > [Data] > > AutoPartition=1 > > MsDosInitiated="1" > > UnattendedInstall="Yes" > > floppyless="1" > > OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" > > OriTyp="4" > > LocalSourceOnCD=1 > > > > [setupData] > > OsLoadOptions="/noguiboot /fastdetect" > > > > SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPA-TH%" > > > > [unattended] > > UnattendMode=FullUnattended > > OemSkipEula=Yes > > OemPreinstall=Yes > > DriverSigningPolicy=Ignore > > OemPnPDriversPath=Drivers\NIC;Drivers\Video;Drivers\Audio; > > TargetPath=\WINDOWS > > FileSystem=LeaveAlone > > NtUpgrade=No > > OverwriteOemFilesOnUpgrade=No > > > > [GuiUnattended] > > AdminPassword=REMOVED > > EncryptedAdminPassword=Yes > > OEMSkipRegional=1 > > TimeZone=%TIMEZONE% > > OemSkipWelcomes=1 > > > > [userData] > > ProductKey=REMOVED > > FullName=REMOVED > > OrgName=REMOVED > > ComputerName=%MACHINENAME% > > > > [Display] > > BitsPerPel=32 > > Xresolution=1280 > > YResolution=1024 > > Vrefresh=60 > > > > [setupMgr] > > DistFolder=C:\windist > > DistShare=windist > > > > [identification] > > JoinDomain=REMOVED > > DoOldStyleDomainJoin=Yes > > > > [Networking] > > InstallDefaultComponents=Yes > > ProcessPageSections=Yes > > > > [RemoteInstall] > > Repartition=Yes > > > > [OSChooser] > > Description="Windows Professional XP SP2" > > Help="This will install Windows Professional in a standard configuration." > > LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" > > ImageType=Flat > > This may help: > > You see, once Setup kicks in, it does a quick check to see if it can > fire up your network card; > for some reason, it won't use the TFTP transfer ability built into PXE > to copy the Setup files. As the > NIC is newer than the drivers that Setup knows about, Setup can't > initialize the card, and stops. > But wait-what about that OEMPnPDrivers command? If you put the drivers > for the new NIC > into > $OEM$ > and pointed to them with OEMPnPDrivers, then Setup ought to be able to > use those drivers, > right? Well, not exactly. Windows 2000, XP, and Server 2003 like their > drivers digitally signed, and > many sets of drivers don't come with digital signatures. You can work > around that by adding this line > to the > ristndrd.sif > script: > DriverSigningPolicy = Ignore > Put that in the [unattended] section. Then put the NIC drivers on the > RIS server in > $OEM$ > as > before, but Microsoft recommends a more specific procedure. Create a > directory > \$OEM$\$1\Drivers\NIC > and put the NIC drivers there. Create an OEMPnpDrivers command that > looks like OemPnp- > DriversPath=\Drivers\Nic in the > ristndrd.sif > file, and then you ought to be able to get RIS > started on a system with a new NIC. (And yes, I > did > recommend that you keep the names of driver > directories short due to the 40-character limit on the > OemPnpDriversPath command, but I wanted > this text to be clear, so I used a longer name. You'd do fine with a > directory named > \$OEM$\$1\DR\NIC > instead of > \$OEM$\$1\Drivers\NIC > ..) > Apparently a driver has to be in the > I386 > directory for the text mode portion of Setup to see it, so > Microsoft says in Knowledge Base article 246184 that you've got to put > the INF and SYS files from > the network driver into the > I386 > directory on the RIS server. You may have to do a bit of experimenting > to find out exactly which SYS and INF files you actually need in the > I386 > directory, because > you don't want to > have > to put > oeminfo.inf > in > I386 > -after all, it seems like every board comes with an > oeminfo.inf > .. > >
Recommended Posts