Trying to get SYSPREP.INF file to work to be able to push one image to multiple machines

B

Brian

I am trying to use the SYSPREP.INF file and the OEMPNPDRIVERSPATH line
to have the workstations push the search paths for the driver files
into the registry. I have tried several different thing and cannot
get this to work. I have tried the -pnp switch when running SYSPREP
and this has not helped. I have checked the registry
(HKLM\Software\Microsoft\Windows\CurrrentVersion) when being prompted
for the driver files, and the information from the OEMPNPDriversPath
in the SYSTEM.INI file is not there. It is just not working. What am
I doing wrong? I am working with Windows 2000 SP2 and SYSPREP 1.1. I
have attached the SYSPREP.INF file that I am using. Thanks in advance
for any direction.

;SetupMgrTag
[Unattended]
DriverSigningPolicy=Ignore
OemSkipEula=Yes
OemPnPDriversPath="drivers;drivers\network\l5;drivers\video\l5;drivers\usb\l5"
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=PASSWORD
AutoLogon = yes
AutoLogonCount = 6
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
FullName="FULLNAME"
ComputerName=*
OrgName="ORGNAME"
ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

[TapiLocation]
CountryCode=107
AreaCode=XXX

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=win2000dist

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[GUIRunOnce]
Command0="c:\winnt\zmg\1strun.vbs"
 
O

Oli Restorick [MVP]

Have you tried adding the line "OemPreinstall=Yes" to the [Unattended]
section of the inf file?

I'm not 100% sure whether this is required for the OEMPnPDriversPath to be
processed, but it is required for processing the $OEM$ directory, which is
how drivers often get copied to the C: drive.

Also, why are you still using Windows 2000 SP2? Are you aware that SP4 is
out and there are many seriously vulnerabilities which you may not be
protected from by sticking on SP2? Unless there's a very good reason for
sticking with SP2, I'd recommend you get to SP4.

Regards

Oli
 
B

Brian

Thanks Oli, I can't remember for sure if I tried the
"OemPreinstall=Yes" (I have tried so many things) I will try it again
to see if it will work.

Is there a specific location that I have to put the Driver files. In
my SYSPREP.INF file, the OemPnPDriversPath has been
"drivers;drivers\network\l5;drivers\video\l5;drivers\usb\l5". The
actual location of the folder is C:\Drivers. From everything that I
have read, I think this is correct. Should the "Drivers" folder be
somewhere else to get it to work properly?

As far as the SP2, I am assisting the desktop department, and they
have decided that they do not have the time nor the need to upgrade to
SP4. I have not been able to figure out their exact reasoning.
(although I do agree with you)

Thanks.
Brian


Oli Restorick said:
Have you tried adding the line "OemPreinstall=Yes" to the [Unattended]
section of the inf file?

I'm not 100% sure whether this is required for the OEMPnPDriversPath to be
processed, but it is required for processing the $OEM$ directory, which is
how drivers often get copied to the C: drive.

Also, why are you still using Windows 2000 SP2? Are you aware that SP4 is
out and there are many seriously vulnerabilities which you may not be
protected from by sticking on SP2? Unless there's a very good reason for
sticking with SP2, I'd recommend you get to SP4.

Regards

Oli


Brian said:
I am trying to use the SYSPREP.INF file and the OEMPNPDRIVERSPATH line
to have the workstations push the search paths for the driver files
into the registry. I have tried several different thing and cannot
get this to work. I have tried the -pnp switch when running SYSPREP
and this has not helped. I have checked the registry
(HKLM\Software\Microsoft\Windows\CurrrentVersion) when being prompted
for the driver files, and the information from the OEMPNPDriversPath
in the SYSTEM.INI file is not there. It is just not working. What am
I doing wrong? I am working with Windows 2000 SP2 and SYSPREP 1.1. I
have attached the SYSPREP.INF file that I am using. Thanks in advance
for any direction.

;SetupMgrTag
[Unattended]
DriverSigningPolicy=Ignore
OemSkipEula=Yes

OemPnPDriversPath="drivers;drivers\network\l5;drivers\video\l5;drivers\usb\l5"
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=PASSWORD
AutoLogon = yes
AutoLogonCount = 6
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
FullName="FULLNAME"
ComputerName=*
OrgName="ORGNAME"
ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

[TapiLocation]
CountryCode=107
AreaCode=XXX

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=win2000dist

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[GUIRunOnce]
Command0="c:\winnt\zmg\1strun.vbs"
 
O

Oli Restorick [MVP]

Hi Brian

The driver location would be fine. Personally, I use abbreviations for the
folder names (to keep the path short).

I would dispute your desktop department's reasoning. If you read the
Microsoft Product Support Lifecycle
(http://support.microsoft.com/default.aspx?pr=lifecycle), specifically the
text related to hotfixes, you'll find that the business would be exposed to
considerable risk by not having hotfixes available for the old service pack.

Microsoft has been generous with providing patches for non-support SP levels
with the most severe patches.

They may say "We have a firewall, so we're protected". Ask them if they
have any laptops in the company at all. As soon as a laptop is removed from
the company's network and plugged in (through dial-up, wireless, or
whatever), the company firewall is providing no protection whatsoever. As
soon as the infected laptop comes back into the company network, your
business is likely to be down for the day.

Still, when they have to reinstall every machine because of some virus, they
might find time to install a recent service pack while they're at it.

Sorry if that sounds harsh (especially given that you already agree with
me), but the "we don't have time" attitude soon changes once you've had a
virus outbreak.

Since you're doing a deployment, now is exactly the right time to do the
service pack rollout.

Cheers

Oli




Brian said:
Thanks Oli, I can't remember for sure if I tried the
"OemPreinstall=Yes" (I have tried so many things) I will try it again
to see if it will work.

Is there a specific location that I have to put the Driver files. In
my SYSPREP.INF file, the OemPnPDriversPath has been
"drivers;drivers\network\l5;drivers\video\l5;drivers\usb\l5". The
actual location of the folder is C:\Drivers. From everything that I
have read, I think this is correct. Should the "Drivers" folder be
somewhere else to get it to work properly?

As far as the SP2, I am assisting the desktop department, and they
have decided that they do not have the time nor the need to upgrade to
SP4. I have not been able to figure out their exact reasoning.
(although I do agree with you)

Thanks.
Brian


Oli Restorick said:
Have you tried adding the line "OemPreinstall=Yes" to the [Unattended]
section of the inf file?

I'm not 100% sure whether this is required for the OEMPnPDriversPath to
be
processed, but it is required for processing the $OEM$ directory, which
is
how drivers often get copied to the C: drive.

Also, why are you still using Windows 2000 SP2? Are you aware that SP4
is
out and there are many seriously vulnerabilities which you may not be
protected from by sticking on SP2? Unless there's a very good reason for
sticking with SP2, I'd recommend you get to SP4.

Regards

Oli


Brian said:
I am trying to use the SYSPREP.INF file and the OEMPNPDRIVERSPATH line
to have the workstations push the search paths for the driver files
into the registry. I have tried several different thing and cannot
get this to work. I have tried the -pnp switch when running SYSPREP
and this has not helped. I have checked the registry
(HKLM\Software\Microsoft\Windows\CurrrentVersion) when being prompted
for the driver files, and the information from the OEMPNPDriversPath
in the SYSTEM.INI file is not there. It is just not working. What am
I doing wrong? I am working with Windows 2000 SP2 and SYSPREP 1.1. I
have attached the SYSPREP.INF file that I am using. Thanks in advance
for any direction.

;SetupMgrTag
[Unattended]
DriverSigningPolicy=Ignore
OemSkipEula=Yes

OemPnPDriversPath="drivers;drivers\network\l5;drivers\video\l5;drivers\usb\l5"
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=PASSWORD
AutoLogon = yes
AutoLogonCount = 6
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
FullName="FULLNAME"
ComputerName=*
OrgName="ORGNAME"
ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

[TapiLocation]
CountryCode=107
AreaCode=XXX

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=win2000dist

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[GUIRunOnce]
Command0="c:\winnt\zmg\1strun.vbs"
 
N

Nicolas

Brian said:
I am trying to use the SYSPREP.INF file and the OEMPNPDRIVERSPATH line
to have the workstations push the search paths for the driver files
into the registry. I have tried several different thing and cannot
get this to work. I have tried the -pnp switch when running SYSPREP
and this has not helped. I have checked the registry
(HKLM\Software\Microsoft\Windows\CurrrentVersion) when being prompted
for the driver files, and the information from the OEMPNPDriversPath
in the SYSTEM.INI file is not there. It is just not working. What am
I doing wrong? I am working with Windows 2000 SP2 and SYSPREP 1.1. I
have attached the SYSPREP.INF file that I am using. Thanks in advance
for any direction.

Hi,

Just to be sure, is your sysprep.inf file in c:\sysprep ?
 

Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top