Sysprep not reading the file

[Guest]

I am having problems with my sysprep.inf file. I think it is not even being
used. No matter what I do it always makes me go through the gui setup and
enter the prduct key.

I have the file in C:\SYSPREP\*.*

the contents are as follows

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\WINDOWS\i386
TargetPath=\WINDOWS

[GuiUnattended]
AdminPassword=
EncryptedAdminPassword=No
OEMSkipRegional=1
OEMDuplicatorstring=AssuranceData-XP-Pro-SP2-1
TimeZone=35
OemSkipWelcome=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="Assurance Data"
OrgName="Assurance Data"
ComputerName=*

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0

 

[Adam Leinss]

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

It's ProductID, not ProductKey.

Adam

 

[Guest]

this did not work either.

Jon M Honhart

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

It's ProductID, not ProductKey.

Adam

 

[Adam Leinss]

this did not work either.

Take a look at this sample sysprep.inf file (this one works!):
http://stealth.kirenet.com/~aleinss/sysprep.inf.

Describe how you are sysprepping your image...the steps you are doing
when you close the image and what type of media you are using (OEM,
Retail, Volume).

Also, is it picking up the other settings?

Adam

 

[Guest]

I have a dir on root of c:\Sysprep with all the files from the *.cab and this
file.
We are VL. I installed XP pro with sp2 VL. I double click the sysprep
until and hit reseal and reboot to test that the mini setup does what i think
it should. What i want it to do is gen a random computer name and never ask
for anything.

Jon M Honhart

 

[Adam Leinss]

I have a dir on root of c:\Sysprep with all the files from the
*.cab and this file.
We are VL. I installed XP pro with sp2 VL. I double click the
sysprep until and hit reseal and reboot to test that the mini
setup does what i think it should. What i want it to do is gen a
random computer name and never ask for anything.

Try running sysprep from the command line and use "sysprep -mini -pnp -
clean". I believe -reseal is used by OEM builders and should not be
needed in a corporate environment.

Adam

 

[Adam Leinss]

in
Actually, leave off the -clean, just try "sysprep -mini -pnp".

Adam

 

[Guest]

that is it.

jmh

 

[Guest]

Hi Adam,

You seem to understand the intricacies of Sysprep. So here it goes.

I purchased HP Business Desktops each with a COA sticker, no volume
licensing, all workstations are exactly the same hardware wise

I have a fresh install and configuration of the workstation. The computer
was joined to the network, applications were installed, Application were
configured and OS was configured. Then the workstation was removed from the
domain and placed back into WORKGROUP workgroup. Security settings will not
allow a blank password for the Administrator account. So it was changed to
the one in the Sysprep.inf.

Sysprep is used to create a master image of the particular HP's model on an
actual spare hard drive. The master image on the hard drive used with a hard
drive duplicator to quickly reimage a replacement drive on a per incident
basis. Frequent replacement was due to the workstations being shipped with
hard drives with a manufacturing defect. Using Sysprep to prepare a quick
restore solution.

What is be best way and the exact step-by-step to use Sysprep in this
situation? Some options/modes are unnecessary as you mentioned.

Some reason previous use of Sysprep will not apply the Sysprep.inf file. I
want to fully comprehend Sysprep so I may avoid this in the future.

Do I need to use the ProductKey on the chasis' COA sticker? Based on this
scenario, how can I avoid messing with the Activation? I don't mind having
to enter the ProductKey off of the COA sticker. How can I tell if the system
as already been activated. Will using the "-activated" eliminate my having
to mess with it. The only problem is that image will be using the one OEM
COA Product Key.

- I prefer to be prompted for the name of the computer prior to creating the
machine account
- Don't want to be prompted for Domain admin and password. I would prefer
to provide that in the Sysprep.inf file.

There is a lot of questions but they didn't seem to get answered with any of
the documentation on Microsoft's website and what I can find on the Internet.

Thanks to all who reply,
Chris A. Zanowick
Enterprise Manager