shamshasan Posted October 3, 2004 Posted October 3, 2004 Problem: (Brief Description)======I am trying to use Remote Installation Services (RIS) to carry out an unattended install of Windows XP OS from my test Server (which I also built). I keep facing this error message after choosing which image to install:The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your system administrator.Setup cannot continue. Press any key to exit.I have read a couple of white papers on many support sites to assist me. However i cannot seem to get past this stage. Definitely gone through: "246184 How to Add Third-Party OEM Network Adapters to RIS Installations" on Microsoft Support. I also * considered and applied carefully instructions and information given specifically by my OEM (DELL) about my device in creating my answer/SIF file, and* created the /$oem$/$1/... directory as per required for the RIS Install to obtain the driver.* was lucky enough to find this site ... i've looked through the two forums: (1) Unattended Windows, and (2) Device Drivers under MSFN -> Unattended Windows Discussion & Support to get advice.... Still no success Appreciate any help I can get. Details follow:(Thanks!!!)-=-=-=-=-=-= DETAILS =-=-=-=-=-=-=-=-=-=-=-=-=-=-:: SETUP OF THE TWO MACHINES (DETAILS) ::1) SERVER: has DHCP and DNS as well as Active Directory working. => I don't believe details of this machine is needed asides from the fact that it's running Windows Server 20032) CLIENT: (that i'm trying to remote install WinXP on) DELL - Optiplex GX270 => Tech Specs: OptiPlex GX270 Desktop Product Details - Tech SpecsAs far as i'm aware and tested DHCP and DNS are working. See nslookup_tested.GIF attached.:: SETTINGS PRIOR TO CREATING RIS IMAGE ::I made sure that my Disk was partitioned in 2 parts. (1) part was partitioned and formatted, and (2) was left unpartitioned (> 40 GB) (1) For all other systems as well as the Windows Server 2003 OS installation => DHCP server + DNS server + Active Directory also installed on this partition (2) Reserved for RIS => (Entire) disk was made dynamic and then this unpartioned space, (2), was formatted prior to installing Remote Installation Services:: CREATED RIS IMAGE THUS ::01) Start -> run -> risetup -> (takes me to:) 'Remote Installation Services Setup Wizard'02) 'Add a new OS image to this remote installation server' => I am on my 6th attempt of creating an image! (just while reading different white papers and trying to create my image in different ways)03) Path (for Installation Source Files Location) :: Windows XP CD :: 'D:\'04) Folder name :: Attempt#xx -> Friendly description :: '...' -> (On 'Previous Client Installation Screens Found' screen:) Use the new client installation screens, and overwrite the old ones05) (Check settings on:) 'Review Settings' screen06) Tasks that were completed: Copying Windows installation files Updating Client Installation wizard screen files Creating unattended Setup answer file Starting the required remote installation services Authorizing DHCP07) 'E:\RemoteInstall\Setup\English\Images\Attempt#xx\i386' exists< Next steps follow after reading "246184 How to Add Third-Party OEM Network Adapters to RIS Installations" on Microsoft Support. >08) Created '...\Attempt#xx\$oem$\$1\Drivers\nic\' and extracted 'Intel PRO/1000 Network Drivers' files (Intel Gigabit LOM, v.7.0.34.0, A00) into this folder. => drivers: Network: Intel Gigabit LOM, Driver, Windows XP, OptiPlex GX270 - Driver Download PAGE09) Copied E1000325.inf and E1000325.sys files into '...\i386\' folder10) Edited '...\Images\Attempt#xx\i386\templates\ristndrd.sif' and added the following lines:[Unattended] OemPreinstall = yes OemPnpDriversPath = Drivers\Nic< Next steps follow after reading the 'Unattend.txt' + 'PushXP.TXT' provided along with the driver installation files by OEM. >11) 'Unattend.txt' :: (PushXP.TXT is also attached at the end) :: this is what is provided by the OEM for Unattend install. PushXP.TXT goes more in depth. => Note: The details in PushXP.TXT define the Unattend install via bootable floppy disk (according to my understanding)[Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes OemPnPDriversPath=\drivers\net\E1000 TargetPath= * DriverSigningPolicy=Ignore Filesystem=LeaveAlone OverwriteOemFilesOnUpgrade=No; This switch prevents the user setup dialog from running when XP; starts for the first time. UnattendSwitch=Yes [GuiUnattended] AdminPassword=* AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 TimeZone=4 OemSkipWelcome=1 [UserData] FullName=Computer1 OrgName=CompanyName ComputerName=Computer1; PRODUCT ID is required for most installations. ProductID="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" [Identification] JoinWorkgroup=WORKGROUP; *Use the following for a domain installation; JoinDomain=MYDOMAIN; CreateComputerAccountInDomain=Yes; DomainAdmin=Installer; DomainAdminPassword=install [Networking] InstallDefaultComponents=Yes12) I also created '...\$oem$\$$\Help' && '...\$oem$\$$System32' as per the details in PushXP.TXT => Note: the RIS install was also tried without these folders and it didn't work.13) I changed OemPnPDriversPath=\Drivers\Nic to OemPnPDriversPath="\drivers\net\E1000" as per detailed in the OEM provided Unattend.txt + PushXP.txt. Also made sure the actual directories reflected this change. => Note: It didn't work with the other settings either anyway. 14) My answer file looks like this now:[data] floppyless = "1" MsDosInitiated="0" OriSrc = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%" OriTyp = "4" LocalSourceOnCD = 1 DisableAdminAccountOnDomainJoin = 1 UnattendedInstall="Yes" [SetupData] OsLoadOptions = "/noguiboot /fastdetect" SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [Unattended] OemPreinstall=Yes FileSystem = LeaveAlone ExtendOEMPartition = 0 TargetPath = \WINDOWS OemSkipEula = yes InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%" LegacyNIC = 1 UnattendMode=GuiAttended OemPnPDriversPath="\drivers\net\E1000" DriverSigningPolicy=Ignore OverwriteOemFilesOnUpgrade=No UnattendSwitch=Yes [UserData] ProductID=<BLANKED OUT> FullName="Shams" OrgName="CMUQ" ComputerName=OffcTst [GuiUnattended] AdminPassword=<BLANKED OUT> EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=150 AutoLogon=Yes AutoLogonCount=1 OemSkipWelcome=1 [Display] BitsPerPel = 16 XResolution = 800 YResolution = 600 VRefresh = 60 [Networking] InstallDefaultComponents=Yes [NetServices] MS_Server=params.MS_PSched [Identification] JoinWorkgroup=WORKGROUP [RemoteInstall] Repartition = Yes UseWholeDisk = Yes [OSChooser] Description ="try 06" Help ="Automatically installs Microsoft Windows XP Professional without prompting the user for input." LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType =Flat Version="5.1 (0)" [TapiLocation] CountryCode=974I hope i've covered all the details. Again, any help is MUCH appreciated!Thanks! Shams -=-=-=-=-=-=-= PushXP.TXT :: BEGINS =-=-=-=-=-=-=-=-Windows* XP Push Install Instructions=======================================Contents:I. IntroductionII. Setting up an install directory on the file serverIII. Deployment MethodsIV. Microsoft documentation for unattended installations of Windows XP.I. Introduction A "Push", or unattended installation of Windows XP provides a means for network adminstrators to easily install Windows XP on similarly equipped systems. The network administrator can create a bootable diskette that will automatically log into a central server and install the operating system from an image of the Windows XP installation directory stored on that server. This document provides instructions for a basic unattended installation of Windows XP that includes the installation of drivers for the Intel® PRO/1000 Family of network adapters. The elements necessary for the Windows XP unattend installation are: - A Windows XP Server with a shared image of the Windows XP Installation CD. - An unattended installation configuration file that provides Windows XP setup with information it needs to complete the installation. The name of this file is UNATTEND.TXT - A DOS boot diskette that contains Microsoft Network Client software for connecting to the Windows XP server and AutoExec commands to automatically start the Windows XP installation.II. Setting up an Install Directory on the File Server The server must be setup with a distribution folder that holds the required Windows XP files and which clients can reach when connecting via TCP/IP or IPX. For illustration purposes, the examples in this readme use the network share D:\PUSHXP. To create this share, create a directory on the server, (EX: D:\PUSHXP). Next, use the "My Computer" applet in Windows XP to locate the D:\PUSHXP folder. Right-click on the folder and select "Sharing". Select "Share this folder", Give it a share name (EX: PUSHXP). This share name will be used to connect to this directory from the remote target systems. By default, the permissions for this share will be for "Everyone" to have "Full Control". Adjust permissions as necessary and click OK. To prepare the distribution folder: 1. Copy the entire contents of the Windows XP CD to D:\PUSHXP. Use Windows Explorer or XCOPY in order to maintain the same directory structure as on the CD. When the copy is complete, the Windows XP installation files should be in the D:\PUSHXP directory and the I386 and other installation directories should be subdirectories of the D:\PUSHXP directory. 2. Copy Unattend.txt from the Intel media (found in the same directory as these instructions) into the shared directory D:\PUSHXP\I386. 3. Edit the Unattend.txt file with Notepad or another text-editor to include your customizations. At a minimum you should change the items in the [userData] section of the file. 4. Create the driver install directory structure and copy the driver files to it. Make folders beneath the new PUSHXP\I386 as follows: \$OEM$\$$\Help \$OEM$\$$\System32 \$OEM$\$1\Drivers\Net\E1000 Copy the driver files from the Drivers disk CD to the $OEM$\$1\Drivers\Net\E1000 directory. Use XCOPY /S or Windows Explorer to maintain the directory structure. When finished the $OEM$\$1\Drivers\Net\E1000 directory should contain the NET8254x.INF file, the E1000NT5.SYS driver file and other files necessary for installing the driver.III. Deployment Methods 1. Make sure that you have a copy of a network bootable MS-DOS floppy that will connect to the Z:\PUSHXP directory and use it to boot the destination system (the one you want to push install to) and connect to this shared network directory. 2. Run the command: (assumes prompt at \\Server\PUSHXP\i386): winnt /u:Z:\I386\unattend.txt /s:Z:\I386 /t:c (where Z: equals mapped drive) Important Note: In the above procedure, setup runs the installation in unattended mode and also detects the plug and play network adapters. All driver files are copied from the shared directory to the target system directories and installation of the OS and Network Adapters continues without user intervention.IV. Microsoft documentation for unattended installations of Windows XP. For a complete description of the parameters supported in Unattend.txt see the DEPLOY.CHM document in the DEPLOY.CAB cabinet file on the Windows XP CD. To obtain the document, use Internet Explorer 5.0 or greater to open DEPLOY.CAB in the \SUPPORT\TOOLS directory on the CD. Other documents and utilities in the DEPLOY.CAB file provide details and tools for setting up a variety of unattended installation methods.[unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes OemPnPDriversPath=\drivers\net\E1000 TargetPath= * DriverSigningPolicy=Ignore Filesystem=LeaveAlone OverwriteOemFilesOnUpgrade=No; This switch prevents the user setup dialog from running when XP; starts for the first time. UnattendSwitch=Yes[GuiUnattended] AdminPassword=* AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 TimeZone=4 OemSkipWelcome=1[userData] FullName=Name OrgName=Organization ComputerName=Computer1; PRODUCT ID is required for most installations. ProductID="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"[identification] JoinWorkgroup=WORKGROUP; *Use the following for a domain installation; JoinDomain=MYDOMAIN; CreateComputerAccountInDomain=Yes; DomainAdmin=Installer; DomainAdminPassword=install[Networking] InstallDefaultComponents=Yes-=-=-=-=-=-=-= PushXP.TXT :: ENDS =-=-=-=-=-=-=-=-
kenedy Posted October 3, 2004 Posted October 3, 2004 Putting network adapter drivers in i386 folder is enough to make text-mode setup running. OemDriversPath is for GUI mode. Try to put all driver files in i386 folder, not just sys and inf. Also you can try driver from Intel (from personal experience - they work good with RIS).
shamshasan Posted October 3, 2004 Author Posted October 3, 2004 OemDriversPath is for GUI mode.Didn't know that... coolTry to put all driver files in i386 folder, not just sys and inf.Tried that, didn't work.So all i'm trying to do is get the idea of RIS and how it works. While my SIF file has some things automated i don't mind doing a psuedo-attend install where i will need to manually type in some of the details. So, from ... Putting network adapter drivers in i386 folder is enough to make text-mode setup running. i'm getting that simply the following steps should be all i need?1) use risetup to create RIS image2) just put the network adapter drivers in the i386 folderand that should be enough to make it work? Oh! The Server and Client machine are connected via a Switch and Ethernet. So, the Client machine needs to communicate through the network driver so that would need to be installed (definately).... .... i'm still lost.
kenedy Posted October 3, 2004 Posted October 3, 2004 So, are you getting initial PXE boot screens (password/domain prompt, image selection)?If yes, then RIS is working fine. WindowsXP just have no driver for that network adapter, so right after PXE Boot phase - error message is displayed.
shamshasan Posted October 3, 2004 Author Posted October 3, 2004 So, are you getting initial PXE boot screens (password/domain prompt, image selection)?If yes, then RIS is working fine. WindowsXP just have no driver for that network adapter, so right after PXE Boot phase - error message is displayed.You are correct... but i knew this already and the answer (supposedly) lies in this white paper: Microsoft Knowledge Base Article - 246184 How to Add Third-Party OEM Network Adapters to RIS Installations.While i learnt stuff through that white paper and i'm sure that the steps i took thereafter were important in the process it doesn't seem to work. I'm missing something and that's what i hope some of the experts here could help me out with.Note: While the white paper details how to, 'Add Third-Party OEM Network Adapters to RIS Installations,' white papers are usually always general and OEMs usually have their own specifications that they want you to follow. Hence i detail my route towards preparing my RIS image with the specific machines. As i mentioned I have been and still am reading up what ever i can to solve this problem. However my reading has sort of flatlined where i'm just coming against the same details again and again. btw, thanks for your help man! still not working... need help people! Shams
kenedy Posted October 3, 2004 Posted October 3, 2004 Seems to me that everything you are doing is correct. At least it works for me.Only difference I see is that you use drivers from DELL. Try downloading this driver and extract everything under \pro2kxpm\PRO1000\WS03XP2K folder to i386 (WinZip/WinRar can open that file)http://downloadfinder.intel.com/scripts-df...e&ProductID=401
Nicguy Posted July 6, 2006 Posted July 6, 2006 The text mode portion relies only on the driver files contained in the i386 directory...nothing else. I've seen one OEM require a modification to the INF file in order to get the driver to load correctly in RIS during the text mode, but I'm not certain if Intel does. Just make sure whatever network drivers (inf and sys files only required) are located in the i386 directory on your RIS image also loads OS present. Make sure you restart your RIS service after placing the appropriate driver. If a .PNF file isn't created with a comparable name to the INF file you included, then you haven't restarted your RIS service (BINLSVC) yet.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now