Re: sysprep.inf and drivers problem



John,

I like the option where you can specify which OU to put the workstation on
when joining it to the domain... Is there away to tell it to move it to a
particular OU base on the computer name during sysprep?



"Johan Arwidmark" wrote:

Regarding the join domain issue, add the following:

[Identification]
CreateComputerACcountInDomain=Yes
JoinDomain=CONTOSO
MachineObjectOU= "OU=Workstations, dc=contoso, dc=com"
DomainAdmin=Contoso\JoinAccount
DomainAdminPassword=password

MachineObjectOU is optional and the join account must have the
necessay permissions to the OU, or to the default computers container
if not usin an OU.

The OemPnPDriversPath looks ok, you can try putting "" around it, like
this:
OemPnPDriversPath="\Drivers\Dell\LatD600\Audio;\Drivers\Dell\LatD600\Modem;\Drivers\Dell\LatD600\Nic"

You can review netsetup.log for troubleshooting join domain issues
during sysprep minisetup.

Skip the -pnp switch when sealing the computer, it is obsolete in most
cases...

During minisetup you can press SHift+F10 to verify the drivers really
are there... you might want to put drivers on C:\, not c:\sysprep for
troubleshooting

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment



On 21 Sep 2006 22:02:25 -0700, nperisa@xxxxxxxxx wrote:

I am having some issues with sysprep and drivers not loading. I am
running it on XP SP2 with the latest sysprep.exe

This is my sysprep.inf file:

;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386
ExtendOemPartition=1
TargetPath=\WINDOWS
DriverSigningPolicy=Ignore
UpgradeInstalledDrivers=Yes
OemSkipEula=Yes


OemPnPDriversPath=C:\sysprep\Drivers\D620\Audio;C:\sysprep\Drivers\D620\CardbusSmartCard;C:\sysprep\Drivers\D620\chipset;C:\sysprep\Drivers\D620\Modem;C:\sysprep\Drivers\D620\Networkcard;C:\sysprep\Drivers\D620\SystemSoftware;C:\sysprep\Drivers\D620\Touchpad;C:\sysprep\Drivers\D620\Video;C:\sysprep\Drivers\D620\Wireless;C:\sysprep\Drivers\D810\6515Cardbus;C:\sysprep\Drivers\D810\Audio;C:\sysprep\Drivers\D810\Chipset;C:\sysprep\Drivers\D810\Modem;C:\sysprep\Drivers\D810\systemsoftware;C:\sysprep\Drivers\D810\Touchpad;C:\sysprep\Drivers\D810\Video;C:\sysprep\Drivers\D810\Wireless;C:\sysprep\Drivers\GX620\Audio;C:\sysprep\Drivers\GX620\Chipset;C:\sysprep\Drivers\GX620\Modem;C:\sysprep\Drivers\GX620\NIC;C:\sysprep\Drivers\GX620\Video;C:\sysprep\Drivers\nc6000\02microcardbus;C:\sysprep\Drivers\nc6000\Cardbus;C:\sysprep\Drivers\nc6000\smartcardbus;C:\sysprep\Drivers\nc6000\SystemSoftware;C:\sysprep\Drivers\NC6120\Audio;C:\sysprep\Drivers\NC6120\cardreader;C:\sysprep\Drivers\NC6120\Chipset
;
C:\sysprep\Drivers\NC6120\PCI;C:\sysprep\Drivers\NC6120\video


[GuiUnattended]
AdminPassword="abc123"
EncryptedAdminPassword=NO
OEMSkipRegional=1
OEMDuplicatorstring=XP06
TimeZone=255
OemSkipWelcome=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXX
FullName="XXXX"
OrgName="XXXXX"
ComputerName=

[TapiLocation]
CountryCode=61
Dialing=Tone
AreaCode=02

[RegionalSettings]
LanguageGroup=1
Language=00000c09

[Identification]
JoinDomain=domainname

[Networking]
InstallDefaultComponents=Yes

[Sysprep]
BuildMassStorageSection=Yes

[SysprepMassStorage]


The issue that i am having is that after i run sysprep and load the
image onto other machines, the drivers do not load. In fact, it doesnt
even ask me to join the domain i specified, it completely skips that
part. So i am assuming there is something wrong with my sysprep.inf
file.

1> Is the the drivers path that i have specified too long? i have
pointed it to where the inf file for the driver is

2> Is there any reason why it would completely skip joining the domain?

Any advice would be greatly appreciated.


.



Relevant Pages

  • Re: Sysprep
    ... "Adam Leinss" wrote: ... Does sysprep search the OemPnPDriversPath recursively or must ... >> each sub dir containing drivers be specified. ... > directories you explicitly specify. ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Sysprep
    ... > each sub dir containing drivers be specified. ... > impression from what I read that each dir that contains drivers ... Sysprep does not recursively search subdirectories, ... directories you explicitly specify. ...
    (microsoft.public.win2000.setup_deployment)
  • RE: Adding Sata-support on an universal image for zti? [Solved]
    ... Then i built a sysprep.inf with the sysprep -bsmd flag to populate the ... 82801FR SATA AHCI Controller ","disk1" ... have read im supposed to add the drivers to sysprep.inf. ... would expect since the drivers isnt really there yet). ...
    (microsoft.public.sms.admin)
  • Re: Getting Multiple Desaktop Models to work with same OSD WIM Image
    ... (using the OSD capture wizard which starts sysprep). ... the other mass storage drivers before I place the SMS Image capture CD ... not having a list of mass storage controllers. ...
    (microsoft.public.sms.tools)
  • LI2.6.151686 Wont Boot After Modem Driver Inatall Attempts
    ... On the last attempt with the .tar.gz file the drivers apparently loaded successfully ... linuxant drivers as I can't boot up the 2.6.15 kernel. ... The only good thing about this new kernel is that it booted the first time after installation. ... Please specify options before other arguments. ...
    (Debian-User)