Troubleshooting RIS: why doesnt $oem$\$1 work

Discussion in 'Microsoft Windows 2000 Deployment' started by folkvord@gmail.com, Jun 6, 2005.

  1. Guest

    Hi!

    I've installed and configured RIS on a Windows 2003 server, and I've
    created two images (the default copied from my winxp select-cd, and one
    created with riprep on a pc install with complete office and so on).

    The riprep-image seemed to work fine untill I tried using it on a pc
    with a different NIC. At first the client wouldn't even boot from the
    RIS-server, but following the instructions from the manufacturer I was
    able to fix that.

    The manufacturer also provided info on how to deploy the drivers with
    the image, so that the client can find and install the neccessary
    drivers from after the install.

    I've followed these instructions, and checked with the docs from
    Microsoft over and over again, but this is still not working.

    If I've understood this correctly, anything i put in the directory
    <image>\$oem$\$1 should be copied to the first harddrive (c: in my
    setup) on the client, no matter what. Is this correct ?
    (I can't find any of the contents of the $1 directory on my c:\ after
    the install)

    Furthermore, when the client boots after the install and find new
    hardware, it should locate the drivers i've copied using the
    $$-directory, if these directories are present in "OEMPnPDriversPath".
    Is this correct as well ?

    Here is my current setup. Can anyone see what I am doing wrong here ?

    Image is located at:

    d:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD

    where I have the two directories

    i386
    $oem$

    the structure for the $oem$ directory is:

    D:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD\$OEM$\$1\Drivers\network

    My ristndrd.sif contains the following settings in the [unattended]
    section:

    [Unattended]
    UnattendMode=FullUnattended
    DriverSigningPolicy = Ignore
    OEMPreinstall=Yes
    OEMPnPDriversPath = \Drivers\display;\Drivers\network
    FileSystem = LeaveAlone
    ExtendOEMPartition = 0
    TargetPath = \WINDOWS
    OemSkipEula = yes
    InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
    LegacyNIC = 1


    ----------------


    I would appreciate any help, since I am kind of stuck now :)

    Thanx,
    Oystein
     
    , Jun 6, 2005
    #1
    1. Advertisements

  2. > If I've understood this correctly, anything i put in the directory
    > <image>\$oem$\$1 should be copied to the first harddrive (c: in my
    > setup) on the client, no matter what. Is this correct ?
    > (I can't find any of the contents of the $1 directory on my c:\ after
    > the install)
    >
    > Furthermore, when the client boots after the install and find new
    > hardware, it should locate the drivers i've copied using the
    > $$-directory, if these directories are present in "OEMPnPDriversPath".
    > Is this correct as well ?
    >
    > Here is my current setup. Can anyone see what I am doing wrong here ?
    >
    > Image is located at:
    >
    > d:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD
    >
    > where I have the two directories
    >
    > i386
    > $oem$
    >
    > the structure for the $oem$ directory is:
    >
    > D:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD\$OEM$\$1\Drivers\network
    >


    Hi!

    I've just tried to install the image based on the select-cd, and then
    the files are copied onto my hard-drive. If I try to install from the
    image created with riprep then I have no luck.

    So this seems to work as intended, at least for the first image I've
    created. Is there any setting in the sif-file that can prevent the
    copying of files. I would like this to work for my customized images
    as well, but I can't figure out why it's not working for both of the
    images.

    Ø
     
    ?ystein Folkvord, Jun 14, 2005
    #2
    1. Advertisements

  3. Guest Guest

    If the RIS image was created with RIPREP, you must perform these steps on
    both the RIPREP image and the RISETUP image that corresponds to the RIPREP
    image.

    Just a kind note that you should also put driver files to both i386 folder
    and $OEM$\$1\Drivers\network folder on the following two images:

    d:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD (Assume this is
    RIPREP image)

    d:\RemoteInstall\Setup\Norwegian\Images\WINXP_RISETUP (Assume this is the
    CD-ROM based image)
     
    Guest, Jun 15, 2005
    #3
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Oli Restorick

    Re: RIS deploying Windows2003 from a Windows2000 RIS server

    Oli Restorick, Jul 23, 2003, in forum: Microsoft Windows 2000 Deployment
    Replies:
    1
    Views:
    592
    Bennie Chen
    Aug 4, 2003
  2. Drew

    Different HAL RIS images run on one RIS Server

    Drew, Jul 25, 2003, in forum: Microsoft Windows 2000 Deployment
    Replies:
    0
    Views:
    849
  3. Microsoft

    RIS Problem: 2000 domain with 2003 RIS Server

    Microsoft, Aug 28, 2003, in forum: Microsoft Windows 2000 Deployment
    Replies:
    1
    Views:
    2,373
    Jeff Davis
    Sep 1, 2003
  4. Ondrej Sevecek

    RIS "Troubleshooting tool" example

    Ondrej Sevecek, Nov 26, 2004, in forum: Microsoft Windows 2000 Deployment
    Replies:
    1
    Views:
    335
    Johan Arwidmark
    Nov 27, 2004
  5. Shayne D. Swann

    RIS autopartition - no doesnt work

    Shayne D. Swann, May 9, 2005, in forum: Microsoft Windows 2000 Deployment
    Replies:
    1
    Views:
    494
    Oli Restorick [MVP]
    May 10, 2005
Loading...

Share This Page