Announcement Banner
UNSOLVED

kmosley

updated

23 years ago

K

kmosley

5 Posts

0

13806

July 7th, 2003 18:00

Optiplex GX270 NIC RIS problem

I'm attempting to install a RIS image to a new Dell Optiplex GX270 machine and I'm getting the following error:
"The operating system image you selected does not containt the necessary drivers for your network adapter. Try selecting a different operating system image..."

My RIS server is Win2K SP3 and the image I'm trying to install is a WinXP SP1 cd-based image. I know that the RIS server works becuase I can dump this image to other PCs that have NIC drivers included on the WinXP CD. This is the first PC I have that has a NIC with an OEM driver.

I've downloaded and tested the latest Dell drivers on this machine in Windows and confirmed that 1) these are the correct drivers and 2) they are digitally signed.

I've place all of the driver files in both of these directories:
  E:\RemoteInstall\Setup\English\Images\WinXP.pro\$oem$\$1\Drivers\Nic
and
  E:\RemoteInstall\Setup\English\Images\WinXP.pro\i386

I've also updated the "E:\RemoteInstall\Setup\English\Images\WinXP.pro\i386\templates\ristndrd.sif" file with the following
parameters:
    [Unattended]
    OemPreinstall = yes
    OemPnpDriversPath = "Drivers\Nic"
(also tried \Drivers\NIC)
    DriverSigningPolicy=Ignore

I've restarted the BINL service and confirmed the creation of the PNF file that is associated with the driver in the i386 directory during the RIS install attempt.

I've also removed all other CD-based images from the server to ensure that there is no confusion about the image being installed.

I've done all of this according to the MS KB articles 254078 and 315279 but I am still not able to install this image on the machine. What am I missing? Is there some form of logging or some other form of diagnoses that I can use to figure out why this isn't working? I've looked through these forums and found other people with this problem, but it seems that their problem was fixed by one of the above steps.

Thanks in advance.
Kurt
  • droid256

    73 Posts

    394

    0

    Posted July 7th, 2003 20:00

    I'm not sure if this will help, but you must use the W2K drivers in the folder E:\RemoteInstall\Setup\English\Images\WinXP.pro\i386

    XP drivers do not seem to work for this phase of RIS.

    Droid

  • kmosley

    5 Posts

    394

    0

    Posted July 8th, 2003 14:00

    That did it! Thanks a ton. I would have never thought of that.

    Thanks again,

    Kurt

  • H.I.S.

    2 Posts

    394

    0

    Posted September 29th, 2003 12:00

    I am having issues with the SX260 and RIS Win2003. I cannot get the drivers to load for text mode for the Intel nic.

    I have put all the files from the Intel 1000 dir from the drivers I downloaded from Intel into the I386 dir of the image and in

    $oem$\$1\drivers\nic\ of the image dir. Still Nothing. What am I missing?

     

     

    Here is my risprep.sif file

    [data]

    floppyless = "1"

    msdosinitiated = "1"

    OriSrc = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

    OriTyp = "4"

    LocalSourceOnCD = 1

    [SetupData]

    OsLoadOptions = "/noguiboot /fastdetect"

    SetupSourceDevice ="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

    SysPrepDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%SYSPREPPATH%"

    SysPrepDriversDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%SYSPREPDRIVERS%"

    [Unattended]

    OemPreinstall = YES

    DriverSigningPolicy = Ingore

    OemPnpDriversPath = "\Drivers\Nic"

    NoWaitAfterTextMode = 0

    FileSystem = LeaveAlone

    ExtendOEMPartition = 0

    ConfirmHardware = no

    NtUpgrade = no

    Win31Upgrade = no

    TargetPath = \WINNT

    OverwriteOemFilesOnUpgrade = no

    OemSkipEula = yes

    InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

    [UserData]

    FullName = "%USERFIRSTNAME% %USERLASTNAME%"

    OrgName = "%ORGNAME%"

    ComputerName ="%MACHINENAME%"

    ProductID = BLANK

    [GuiUnattended]

    OemSkipWelcome = 1

    OemSkipRegional = 1

    TimeZone = %TIMEZONE%

    AdminPassword = "*"

    [LicenseFilePrintData]

    AutoMode = PerSeat

    [Display]

    ConfigureAtLogon = 0

    BitsPerPel = 32

    XResolution = 1024

    YResolution = 768

    VRefresh = 75

    AutoConfirm = 1

    [Networking]

    ProcessPageSections=Yes

    [Identification]

    JoinDomain = No

    CreateComputerAccountInDomain = No

    DoOldStyleDomainJoin = Yes

    [NetProtocols]

    MS_TCPIP=params.MS_TCPIP

    [params.MS_TCPIP]

    ; transport: TC (TCP/IP Protocol)

    InfID=MS_TCPIP

    DHCP=Yes

    [NetClients]

    MS_MSClient=params.MS_MSClient

    [params.MS_MSClient]

    InfID=MS_MSClient

    [NetServices]

    MS_Server=params.MS_Server

    [params.MS_Server]

    ; service: SRV (Server)

    InfID=MS_Server

    BroadcastsToLanman2Clients = No

    [ServicesSection]

    [RemoteInstall]

    Repartition = Yes

    UseWholeDisk = Yes

    [OSChooser]

    Description ="Windows 2000 Pro Image"

    Help =""

    LaunchFile ="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"

    ImageType =SYSPREP

    Version="5.0 (2195)"

    SysPrepSystemRoot="Mirror1\UserData\WINNT"

    ProductType=0

  • kmosley

    5 Posts

    394

    0

    Posted September 29th, 2003 14:00

    Have you restarted the BINL service on the RIS server? Have you confirmed creation of the PNF files in the I386 folder? Those are the only two things that I make sure I do that you didn't mention.

    I've found that Microsoft has a number of KB articles on this issue and all of them seem to leave out one step or another in their instructions. Article 254078 seems to be the most complete.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;254078

    The only thing that this article leaves out in my experience is that when you are using RIS to deploy WinXP you have to put Win2K drivers in the I386 directory and WinXP drivers in the OEM directory. I guess the text mode setup still uses the same driver base as Win2K. The OEM directory is used after text mode setup finishes.

  • kmosley

    5 Posts

    394

    0

    Posted September 29th, 2003 14:00

    Also, I just noticed this:

    DriverSigningPolicy = Ingore

    Try correcting the spelling to "Ignore".

    I'm not sure if your driver is signed or not, but this should be corrected anyway. Also, if you are replacing one of the original Windows drivers with your updated driver, then your driver MUST be signed. I'm not sure if there is a way around this, but I remember reading it.

  • H.I.S.

    2 Posts

    394

    0

    Posted September 29th, 2003 15:00

    I fixed the spelling , but still nothing. I read through the article you gave the link to.  It says to modify the ristndrd.sif file. I have been modifying the risprep.sif file because this image was a desktop build with all programs loaded on it - not a clean load. Is this wrong? Also, there are no PNF files in the setup\english\images\imagename\i386 folder.
  • kmosley

    5 Posts

    394

    0

    Posted September 29th, 2003 20:00

    The driver procedure is different for RIPREP images than it is for CD-based RIS images. I'm not as familiar with the procedure for RIPREP images but I can tell you what I know. I do believe there is a section in that MS article I referred to that gives more details for the RIPREP images.

    RIPREP uses the original CD-based image for it's text mode setup. Therefore, you have to put the Win2K drivers in the i386 directory of the ORIGINAL CD-BASED image to get the RIPREP image to see the drivers during it's text mode setup. This i386 directory is also where you would see the PNF files. You don't have to put anything in the i386 folder of the RIPREP image. You still modify the risstndrd.sif file for this image to make it work properly. Since you have to have the CD-based image working before the RIPREP image will work, I'd start by testing this image on your client.

    RIPREP uses a method more like SYSPREP to handle the gui-mode setup for the image dump to the client so the image for RIPREP has to be setup more like SYSPREP. This is the part I'm not so sure about but you should be able to try both options to see how it should work. The $OEM$ folder either goes in the image folder at the same level as i386 and you modify the riprep.sif OR the $OEM$ folder goes in the SYSPREP folder in the image data and you modify the sysprep.inf in that sysprep folder. I'm not sure but in either case, you should be able to get to the GUI mode setup since the CD-based image is used for the text setup portion.

  • albsurfer

    1 Message

    394

    0

    Posted November 4th, 2004 17:00

    1. Make sure that your NIC files are the Generic Intel versions from the Intel website. Intel also provides a document and an INF file for the GigaNic.  The locations for the Nic driver is correct.  The two ristndrd.sif files in the source CD directory on the RIS server, and the image riprep.sif file, must contain the path OEMPNPDriversPath = \drivers\nic in order to work correctly. 

    2. The correct Setupldr.exe that needs to be renamed to ntldr is obtained from Microsoft PSS.  The link that has been floating around is incorrect.  It is not a downloadable file.  I am using XP Pro SP1 and SP2 images on RIS Server 2003, however, Server 2000 is affected also.  I had to obtain this file from PSS to finish fixing the NIC error.  I believe that one other file is listed in the article as a fix.