Re: sysprep.inf and drivers problem

Sysprep cannot move a computer account to a new OU..

But there is of course a workaround :)

I use an ADSI script (from within WinPE) after the image laydown
process, but before rebooting into sysprep minisetup to move the
computer account to another OU. Then sysprep minisetup just will
update the computer account in it's new location

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment


On Tue, 31 Oct 2006 07:08:02 -0800, Jeffrey B
<JeffreyB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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\Chipse
t
;
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: Group Policy Loopback Not Applying
    ... The computer account in question was definitely located in the ... another computer into that OU and found the loopback policy worked as ... figured I would run sysprep again. ... May there be something in a batch file running making a change, a security setting being applied, etc? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Computer Accounts no longer working
    ... Of course the deletion replication event comes plowing through eventually ... You can simply reset the computer account rather than delete it. ... The lab is then reimaged, which includes>> Sysprep, etc to change SIDs, and names added to the correct domain with the>> same computer name as before. ... >> - change computer to a Workgroup member ...
    (microsoft.public.win2000.active_directory)
  • Re: sysprep.inf and drivers problem
    ... been incorrect, my drivers are now loading after i fixed that path up, ... that part of sysprep looks like this... ... during sysprep minisetup. ... The issue that i am having is that after i run sysprep and load the ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Locked Out
    ... Do both of these computers have the same name (and possibly SID)? ... sure each has a unique name, if cloned and sysprep wasn't run, run ... sysprep so new SIDs are generated, reset the computer account in ... > machine to input all of the network information. ...
    (microsoft.public.win2000.general)
  • Re: Advice on domain joining
    ... I'm not sure sysprep will do what I need. ... >>then move its Computer account as needed. ...
    (microsoft.public.win2000.networking)