OEM Drivers in RIPREP XP Images from 2K3 server

[Andy L]

I have no problems at all deploying a flat/cd based XP installations with
oem drivers to client machines using 2003 server - the pnp process works
flawlessly to find and add any drivers to the image that is needed. I have
also used sysprep quite a lot and had no problems deploying those images
using ghost, those images also found and added any drivers I specified in
OEMPnpDriversPath.

however... I am getting nowhere fast with RIPREP based images.

I have followed, to the letter, MS KB articles on adding OEM drivers to
RIPREP based images and the client still fails to find/install any of the
included drivers, and prompts for the location of drivers for each new piece
of hardware it finds.
I have used RIPREP with and without the /pnp option to create the image.
I have inspected the registry hive of the RIPREP'd image on the server, and
it does contain the correct string for all of the drivers
(%systemroot%\drivers\nic;%systemroot%\drivers\gfx... etc.) in the
DriverPath key, but it seems to ignore it.

1. Do RIPREP images work more like SYSPREP images, in that the drivers need
to be included in the master installation itself (ie: c:\drivers\nic) rather
than like the 'Flat/CD based' RIS installation method where an
$oem$\$1\drivers\nic folder is specified within/alongside the i386 folder
for the image on the RIS server? This seems logical, as an RIPREP image is
not an 'Installation' as such and so RIS perhaps does not integrate the
$oem$\$1 structure into the deployed filesystem.

2. I read in an MS KB article that to add OEM drivers to RIPREP images, you
need to create a sysprep.inf file in %systemroot%\sysprep containing

[Unattended]
OEMPnpDriversPath=drivers\nic (for example)

.... is that ALL the sysprep.inf file for a RIPREP image needs to contain, or
does it also need to contain the oempreinstall="yes" ?

3. Related to question 2, how much information can/does RIPREP use from the
c:\sysprep\sysprep.inf file? or does it ONLY go looking for the
OEMPnpDriversPath option. What if I included other sections like the
product key in this file - would it be used or simply ignored in favour of
what is specified in the riprep.sif in the image_name/templates folder on
the RIS server?

4. The RIPREP image also has an annoying habit of not quietly/automatically
installing a detected Plug and Play monitor - how do I fix that?

Any advice would be most appreciated.

Andy

 

[NIC Student]

Hi Andy,

OEM Drivers in RIS can be very frustrating, but it's normally that you
forgot one small part of the process. Since it appears that you have
located MS's articles on OEM/RIS, you may either be missing a step or are
using the wrong the drivers for the nic. What nic are you using/testing?

Try looking at my step-by-step that gives you just the nitty-gritty (use
Intel pro/100 vm link):

http://www.mvps.org/serverstuff/RIS/oemris.htm

The "readme" was written for Win2000sp3 server but it works for later
versions including 2003.

If you are using some other nic, please forward the drivers so I can add
them to the site.

--
Scott Baldridge
Windows Server MVP, MCSE

"Andy L" >I have no problems at all deploying a flat/cd based XP
installations with

oem drivers to client machines using 2003 server - the pnp process works
flawlessly to find and add any drivers to the image that is needed. I
have also used sysprep quite a lot and had no problems deploying those
images using ghost, those images also found and added any drivers I
specified in OEMPnpDriversPath.

however... I am getting nowhere fast with RIPREP based images.

I have followed, to the letter, MS KB articles on adding OEM drivers to
RIPREP based images and the client still fails to find/install any of the
included drivers, and prompts for the location of drivers for each new
piece of hardware it finds.
I have used RIPREP with and without the /pnp option to create the image.
I have inspected the registry hive of the RIPREP'd image on the server,
and it does contain the correct string for all of the drivers
(%systemroot%\drivers\nic;%systemroot%\drivers\gfx... etc.) in the
DriverPath key, but it seems to ignore it.

1. Do RIPREP images work more like SYSPREP images, in that the drivers
need to be included in the master installation itself (ie: c:\drivers\nic)
rather than like the 'Flat/CD based' RIS installation method where an
$oem$\$1\drivers\nic folder is specified within/alongside the i386 folder
for the image on the RIS server? This seems logical, as an RIPREP image
is not an 'Installation' as such and so RIS perhaps does not integrate the
$oem$\$1 structure into the deployed filesystem.

2. I read in an MS KB article that to add OEM drivers to RIPREP images,
you need to create a sysprep.inf file in %systemroot%\sysprep containing

[Unattended]
OEMPnpDriversPath=drivers\nic (for example)

... is that ALL the sysprep.inf file for a RIPREP image needs to contain,
or does it also need to contain the oempreinstall="yes" ?

3. Related to question 2, how much information can/does RIPREP use from
the c:\sysprep\sysprep.inf file? or does it ONLY go looking for the
OEMPnpDriversPath option. What if I included other sections like the
product key in this file - would it be used or simply ignored in favour of
what is specified in the riprep.sif in the image_name/templates folder on
the RIS server?

4. The RIPREP image also has an annoying habit of not
quietly/automatically installing a detected Plug and Play monitor - how do
I fix that?

Any advice would be most appreciated.

Andy

 

[Andy L]

Thanks, I've had a good read and I 'think' what I might be missing is
modifying the riprep.sif that riprep creates for the new image to include
the 'oempreinstall=yes' line - ala sysprep.

Funny thing is, MS KB article "adding oem drivers to xp" doesn't mention
oempreinstall=yes in the riprep images section.

Heres hoping...

Andy

Hi Andy,

OEM Drivers in RIS can be very frustrating, but it's normally that you
forgot one small part of the process. Since it appears that you have
located MS's articles on OEM/RIS, you may either be missing a step or are
using the wrong the drivers for the nic. What nic are you using/testing?

Try looking at my step-by-step that gives you just the nitty-gritty (use
Intel pro/100 vm link):

http://www.mvps.org/serverstuff/RIS/oemris.htm

The "readme" was written for Win2000sp3 server but it works for later
versions including 2003.

If you are using some other nic, please forward the drivers so I can add
them to the site.

--
Scott Baldridge
Windows Server MVP, MCSE

"Andy L" >I have no problems at all deploying a flat/cd based XP
installations with

oem drivers to client machines using 2003 server - the pnp process works
flawlessly to find and add any drivers to the image that is needed. I
have also used sysprep quite a lot and had no problems deploying those
images using ghost, those images also found and added any drivers I
specified in OEMPnpDriversPath.

however... I am getting nowhere fast with RIPREP based images.

I have followed, to the letter, MS KB articles on adding OEM drivers to
RIPREP based images and the client still fails to find/install any of the
included drivers, and prompts for the location of drivers for each new
piece of hardware it finds.
I have used RIPREP with and without the /pnp option to create the image.
I have inspected the registry hive of the RIPREP'd image on the server,
and it does contain the correct string for all of the drivers
(%systemroot%\drivers\nic;%systemroot%\drivers\gfx... etc.) in the
DriverPath key, but it seems to ignore it.

1. Do RIPREP images work more like SYSPREP images, in that the drivers
need to be included in the master installation itself (ie:
c:\drivers\nic) rather than like the 'Flat/CD based' RIS installation
method where an $oem$\$1\drivers\nic folder is specified within/alongside
the i386 folder for the image on the RIS server? This seems logical, as
an RIPREP image is not an 'Installation' as such and so RIS perhaps does
not integrate the $oem$\$1 structure into the deployed filesystem.

2. I read in an MS KB article that to add OEM drivers to RIPREP images,
you need to create a sysprep.inf file in %systemroot%\sysprep containing

[Unattended]
OEMPnpDriversPath=drivers\nic (for example)

... is that ALL the sysprep.inf file for a RIPREP image needs to contain,
or does it also need to contain the oempreinstall="yes" ?

3. Related to question 2, how much information can/does RIPREP use from
the c:\sysprep\sysprep.inf file? or does it ONLY go looking for the
OEMPnpDriversPath option. What if I included other sections like the
product key in this file - would it be used or simply ignored in favour
of what is specified in the riprep.sif in the image_name/templates folder
on the RIS server?

4. The RIPREP image also has an annoying habit of not
quietly/automatically installing a detected Plug and Play monitor - how
do I fix that?

Any advice would be most appreciated.

Andy

 

[Andy L]

Yes! that was it. oempreinstall=yes MUST be added to the riprep.sif in the
new image templates folder.

I also resolved two other issues:

1. Plug and Play monitor not installed automatically - this was due to the
target machine having an Intel Express chipset which supports two monitors -
I simply riprep'd the image from that machine which already had installed
the two Plug and Play monitors installed. As with many things in life, it's
easier to take away than to add.

2. Newly created RIPREP image not available for certain machines in RIS
menu - I was banging my head against the wall why the newly created image
from a later machine wasn't visible to other machines, then I noticed the
'Intel HT' technology badge. Doh. HyperThreading machines use a Different
HAL 'ACPI Multi-processor' (which kinda explains the two processors
installed in device manager) and not 'ACPI Uni-processor' - so it looks like
I need two images... unless someone knows off the top of their head if it's
possible to use the same image files but to deploy it using a different HAL?
Either that or for now I disable HyperThreading in BIOS, which I think I
have seen as an option.

Many thanks,

Andy

Thanks, I've had a good read and I 'think' what I might be missing is
modifying the riprep.sif that riprep creates for the new image to include
the 'oempreinstall=yes' line - ala sysprep.

Funny thing is, MS KB article "adding oem drivers to xp" doesn't mention
oempreinstall=yes in the riprep images section.

Heres hoping...

Andy

Hi Andy,

OEM Drivers in RIS can be very frustrating, but it's normally that you
forgot one small part of the process. Since it appears that you have
located MS's articles on OEM/RIS, you may either be missing a step or are
using the wrong the drivers for the nic. What nic are you using/testing?

Try looking at my step-by-step that gives you just the nitty-gritty (use
Intel pro/100 vm link):

http://www.mvps.org/serverstuff/RIS/oemris.htm

The "readme" was written for Win2000sp3 server but it works for later
versions including 2003.

If you are using some other nic, please forward the drivers so I can add
them to the site.

--
Scott Baldridge
Windows Server MVP, MCSE

"Andy L" >I have no problems at all deploying a flat/cd based XP
installations with

oem drivers to client machines using 2003 server - the pnp process works
flawlessly to find and add any drivers to the image that is needed. I
have also used sysprep quite a lot and had no problems deploying those
images using ghost, those images also found and added any drivers I
specified in OEMPnpDriversPath.

however... I am getting nowhere fast with RIPREP based images.

I have followed, to the letter, MS KB articles on adding OEM drivers to
RIPREP based images and the client still fails to find/install any of
the included drivers, and prompts for the location of drivers for each
new piece of hardware it finds.
I have used RIPREP with and without the /pnp option to create the image.
I have inspected the registry hive of the RIPREP'd image on the server,
and it does contain the correct string for all of the drivers
(%systemroot%\drivers\nic;%systemroot%\drivers\gfx... etc.) in the
DriverPath key, but it seems to ignore it.

1. Do RIPREP images work more like SYSPREP images, in that the drivers
need to be included in the master installation itself (ie:
c:\drivers\nic) rather than like the 'Flat/CD based' RIS installation
method where an $oem$\$1\drivers\nic folder is specified
within/alongside the i386 folder for the image on the RIS server? This
seems logical, as an RIPREP image is not an 'Installation' as such and
so RIS perhaps does not integrate the $oem$\$1 structure into the
deployed filesystem.

2. I read in an MS KB article that to add OEM drivers to RIPREP images,
you need to create a sysprep.inf file in %systemroot%\sysprep containing

[Unattended]
OEMPnpDriversPath=drivers\nic (for example)

... is that ALL the sysprep.inf file for a RIPREP image needs to
contain, or does it also need to contain the oempreinstall="yes" ?

3. Related to question 2, how much information can/does RIPREP use from
the c:\sysprep\sysprep.inf file? or does it ONLY go looking for the
OEMPnpDriversPath option. What if I included other sections like the
product key in this file - would it be used or simply ignored in favour
of what is specified in the riprep.sif in the image_name/templates
folder on the RIS server?

4. The RIPREP image also has an annoying habit of not
quietly/automatically installing a detected Plug and Play monitor - how
do I fix that?

Any advice would be most appreciated.

Andy

 

[NIC Student]

Nice job, Andy.

--
Scott Baldridge
Windows Server MVP, MCSE

"Andy L"

Yes! that was it. oempreinstall=yes MUST be added to the riprep.sif in
the new image templates folder.

I also resolved two other issues:

1. Plug and Play monitor not installed automatically - this was due to the
target machine having an Intel Express chipset which supports two
monitors - I simply riprep'd the image from that machine which already had
installed the two Plug and Play monitors installed. As with many things
in life, it's easier to take away than to add.

2. Newly created RIPREP image not available for certain machines in RIS
menu - I was banging my head against the wall why the newly created image
from a later machine wasn't visible to other machines, then I noticed the
'Intel HT' technology badge. Doh. HyperThreading machines use a
Different HAL 'ACPI Multi-processor' (which kinda explains the two
processors installed in device manager) and not 'ACPI Uni-processor' - so
it looks like I need two images... unless someone knows off the top of
their head if it's possible to use the same image files but to deploy it
using a different HAL? Either that or for now I disable HyperThreading in
BIOS, which I think I have seen as an option.

Many thanks,

Andy

Thanks, I've had a good read and I 'think' what I might be missing is
modifying the riprep.sif that riprep creates for the new image to include
the 'oempreinstall=yes' line - ala sysprep.

Funny thing is, MS KB article "adding oem drivers to xp" doesn't mention
oempreinstall=yes in the riprep images section.

Heres hoping...

Andy

Hi Andy,

OEM Drivers in RIS can be very frustrating, but it's normally that you
forgot one small part of the process. Since it appears that you have
located MS's articles on OEM/RIS, you may either be missing a step or
are using the wrong the drivers for the nic. What nic are you
using/testing?

Try looking at my step-by-step that gives you just the nitty-gritty (use
Intel pro/100 vm link):

http://www.mvps.org/serverstuff/RIS/oemris.htm

The "readme" was written for Win2000sp3 server but it works for later
versions including 2003.

If you are using some other nic, please forward the drivers so I can add
them to the site.

--
Scott Baldridge
Windows Server MVP, MCSE

"Andy L" >I have no problems at all deploying a flat/cd based XP
installations with
oem drivers to client machines using 2003 server - the pnp process
works flawlessly to find and add any drivers to the image that is
needed. I have also used sysprep quite a lot and had no problems
deploying those images using ghost, those images also found and added
any drivers I specified in OEMPnpDriversPath.

however... I am getting nowhere fast with RIPREP based images.

I have followed, to the letter, MS KB articles on adding OEM drivers to
RIPREP based images and the client still fails to find/install any of
the included drivers, and prompts for the location of drivers for each
new piece of hardware it finds.
I have used RIPREP with and without the /pnp option to create the
image.
I have inspected the registry hive of the RIPREP'd image on the server,
and it does contain the correct string for all of the drivers
(%systemroot%\drivers\nic;%systemroot%\drivers\gfx... etc.) in the
DriverPath key, but it seems to ignore it.

1. Do RIPREP images work more like SYSPREP images, in that the drivers
need to be included in the master installation itself (ie:
c:\drivers\nic) rather than like the 'Flat/CD based' RIS installation
method where an $oem$\$1\drivers\nic folder is specified
within/alongside the i386 folder for the image on the RIS server? This
seems logical, as an RIPREP image is not an 'Installation' as such and
so RIS perhaps does not integrate the $oem$\$1 structure into the
deployed filesystem.

2. I read in an MS KB article that to add OEM drivers to RIPREP images,
you need to create a sysprep.inf file in %systemroot%\sysprep
containing

[Unattended]
OEMPnpDriversPath=drivers\nic (for example)

... is that ALL the sysprep.inf file for a RIPREP image needs to
contain, or does it also need to contain the oempreinstall="yes" ?

3. Related to question 2, how much information can/does RIPREP use from
the c:\sysprep\sysprep.inf file? or does it ONLY go looking for the
OEMPnpDriversPath option. What if I included other sections like the
product key in this file - would it be used or simply ignored in favour
of what is specified in the riprep.sif in the image_name/templates
folder on the RIS server?

4. The RIPREP image also has an annoying habit of not
quietly/automatically installing a detected Plug and Play monitor - how
do I fix that?

Any advice would be most appreciated.

Andy