Automate Install of PnP Drivers

I'm currently in the process of building a standard Windows 20003 Server
install that will work across 5 different servers by using sysprep and
scripting. Does anyone have any recommendations on how to automate the
installation of PnP drivers that are provided by the manufacturer and not on
the Windows 2003 Server CD?

I've come across a utility named devcon.exe that will work in my
environment, but I was hoping for something that would be more streamlined
(e.g., modify and ini or inf file that comes with Windows 2003 to include
these new drivers).

Thanks,
David

circa Wed, 17 Dec 2003 13:52:09 -0500, in
microsoft.public.windows.server.setup, David Krause
((E-Mail Removed)) said,
> I'm currently in the process of building a standard Windows 20003 Server
> install that will work across 5 different servers by using sysprep and
> scripting. Does anyone have any recommendations on how to automate the
> installation of PnP drivers that are provided by the manufacturer and not on
> the Windows 2003 Server CD?
>
> I've come across a utility named devcon.exe that will work in my
> environment, but I was hoping for something that would be more streamlined
> (e.g., modify and ini or inf file that comes with Windows 2003 to include
> these new drivers).
>
>
Devcon is unnecessary. Use [OEMPnPDriversPath] with your answer file
(s). For more info:

http://support.microsoft.com/default...b;en-us;254078

If you're using sysprep, check out the -factory switch.

Laura
--
Time flies like an arrow; fruit flies like a banana.
-Groucho Marx

Thanks for the information and it worked as defined in the attached article.

One thing that I found interested is that the -factory switch does not load
the
drivers defined in the OemPnPDriversPath, but the -reseal does load the
drivers. Interesting note for those planning to use this option in the
sysprep.inf

Thanks again for your help...David

"Laura A. Robinson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> circa Wed, 17 Dec 2003 13:52:09 -0500, in
> microsoft.public.windows.server.setup, David Krause
> ((E-Mail Removed)) said,
> > I'm currently in the process of building a standard Windows 20003 Server
> > install that will work across 5 different servers by using sysprep and
> > scripting. Does anyone have any recommendations on how to automate the
> > installation of PnP drivers that are provided by the manufacturer and
not on
> > the Windows 2003 Server CD?
> >
> > I've come across a utility named devcon.exe that will work in my
> > environment, but I was hoping for something that would be more
streamlined
> > (e.g., modify and ini or inf file that comes with Windows 2003 to
include
> > these new drivers).
> >
> >
> Devcon is unnecessary. Use [OEMPnPDriversPath] with your answer file
> (s). For more info:
>
> http://support.microsoft.com/default...b;en-us;254078
>
> If you're using sysprep, check out the -factory switch.
>
> Laura
> --
> Time flies like an arrow; fruit flies like a banana.
> -Groucho Marx

circa Thu, 18 Dec 2003 14:54:17 -0500, in
microsoft.public.windows.server.setup, David Krause
((E-Mail Removed)) said,
> Thanks for the information and it worked as defined in the attached article.
>
> One thing that I found interested is that the -factory switch does not load
> the
> drivers defined in the OemPnPDriversPath, but the -reseal does load the
> drivers. Interesting note for those planning to use this option in the
> sysprep.inf
>
> Thanks again for your help...David
>
>
The factory switch is what you use to add the modifications to the
base image, and reseal is what puts the machine "back" into a state
where it completes installation. *All* syspreps have to be resealed
in order to complete. The documentation for sysprep 2.0 is woefully
incomplete in providing "big picture" explanation, unfortunately. :-(

Laura
--
I find that the further I go back, the better things were, whether
they happened or not.
-Mark Twain