• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3929
  • Last Modified:

SYSPREP does not use SYSPREP.INF created by setupmgr.exe

Help. I have configured sysprep (verion 2.0) within C:\sysprep for a WinXP SP2 machine. I have all the required files including setupcl.exe, sysprep.exe, i386 folder, sysprep.inf within c:\sysprep.

I am trying to automate and have sysprep automate the complete setup, add to domain with unique PC name etc. I cannot seem to get this working. After generating the sysprep.inf file. I douleclick sysprep.exe and click Use Mini-Setup and then RESEAL. The machine shuts down but then goes through the complete MINI setup which includes EULA aggreement, admin PW, etc. I have added the following in the sysprep file:
[Unattended]
    OemSkipEULA=Yes
[GuiUnattended]
    AdminPassword=specialsssssss
    AutoLogon=Yes
    AutoLogonCount=1
    OEMSkipRegional=1
    OemSkipWelcome=1
    OEMDuplicatorstring="HP Evo xw6000"
    TimeZone=85
[UserData]
    FullName="User"
    OrgName="SPECIAL HOUSE plc"
    ProductKey=xxxx-xxxxx-xxxxx-xxxxx-xxxx
    ComputerName=DR1
[Identification]
    JoinDomain=RANDOM
    DomainAdmin=addit
    DomainAdminPassword=additpw
    CreateComputerAccountInDomain=Yes

Has anyone got any idea on what I am doing wrong. I have read all the MS reference and I can't understand what I am missing. Any feedback would be most appreciated.

Thanks,

jel
0
15moorgate
Asked:
15moorgate
  • 3
  • 3
2 Solutions
 
gemartiCommented:
[GuiUnattended]
AdminPassword=specialssssssss  should be     AdminPassword="specialsssssss"

[Identification]
DomainAdmin=addit should be "addit" or "Domain\addit"
DomainAdminPassword=additpw should be DomainAdminPassword="additpw"


From the command line enter the following:

c:\sysprep\sysprep.exe -mini -reseal -quiet

it's easier than using the gui interface, in my opinion.
0
 
gemartiCommented:
Also just for the heck of it try:

[Unattended]
    OemSkipEula=Yes

instead of

[Unattended]
    OemSkipEULA=Yes


I don't think it makes a difference, but my sysprep.inf doesn't uses the caps and it works fine.
0
 
15moorgateAuthor Commented:
Guys, thanks for feedback. I will try these settings first thing tomorrow as I am in GMT zone. I will update tomorrow.

The impression I get from my symptons is that the SYSPREP does not even register that the SYSPREP.INF exists.

jel
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
15moorgateAuthor Commented:
Guys, thanks very much for your input. I now have the SYSPREP working but just one error that complains it cannot change the administrator password. After this error the SYSPREP rountine completes succefully and adds to domain with random generated PC name etc.

The -quiet -mini -reseal finally picked up the prepared SYSPREP.INF. Thanks very much for your invaluable input. I have 20 machines that this will benefit during our Disaster Recovery testing etc.

jel.
0
 
gemartiCommented:
I'm not sure what you mean; your trying to change the administrator's password with sysprep?

Do you have a script that runs on your second logon which is supposed to change the password?

0
 
15moorgateAuthor Commented:
Thanks again.

jel
0
 
FisherInvestmentsCommented:
fyi to change your password with sysprep the machine you are running it against must have a BLANK admin password.  Make sure you choose to encrypt the password in your inf file.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now