/build/static/layout/Breadcrumb_cap_w.png

WinXP Sysprep



Hello,

I have created an image of WinXP plus my standard apps that I want to sysprep and deploy to multiple, identical machines. I have used the setup manager MS provides from the WINXP CD:\SUPPORT\TOOLS\deploy.cab to create a sysprep.ini answer file. I hope to get to the point where, after a successful application of this drive image, the newly imaged machine will boot up, and go through the MS mini-setup screen (where you are usually asked to ok the EULA and put in the XP registration code) automatically, as I have already specified the XP registration in the answer file. After running Sysprep, and choosing the "reseal" option to generate a unique SID, the machine will reboot and go into the mini-setup, where it will ask for the XP registration (like its not seeing or using the sysprep.ini) This sysprep.ini I created along with the sysprep.exe and setupcl.exe are all at the root of the C: drive for imaging.

Any ideas?

0 Comments   [ + ] Show comments

Answers (13)

Posted by: FoBoT 19 years ago
Yellow Belt
0
the .ini and sysprep files need to be in c:\sysprep
after it runs, it deletes this directory (and thus the .ini file inside it)
Posted by: churchill72 19 years ago
Senior Yellow Belt
0
All of the correct files are in the c:\sysprep directory. That is:

1. sysprep.exe
2. sysprep.ini
3. setupcl.exe

Upon rebooting after running sysprep (from c:\sysprep) I am still prompted for the EULA agreement and then the WinXP registration code (which is specified in the sysprep.ini answer file) and then, following that, it goes through a few more setup questions related to computer name and other network settings which, as I said before, should be pulled from the answer file. Anyone know why this is happening?
Posted by: BRoadruck 19 years ago
Senior Yellow Belt
0
Are you using a Corporate XP Key?
Posted by: churchill72 19 years ago
Senior Yellow Belt
0
Yes, we have a corporate wide key.
Posted by: BRoadruck 19 years ago
Senior Yellow Belt
0
Post your sysprep.ini file in here, XXXX out anything that is site specific. Also, trim out any mass storage devices you may have, I don't need any of them.

Brian
Posted by: kazmark 19 years ago
Yellow Belt
0
Make sure you have this in the .inf file and it will work


[Unattended]
OemSkipEula=Yes
OemPnPDriversPath=C:\i386\drivers
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINNT

[GuiUnattended]
AdminPassword=******
OEMSkipRegional=1
TimeZone=85
OemSkipWelcome=1

[UserData]
ProductKey="*****-*****-*****-*****-*****"
FullName="My"
OrgName="Computer"
ComputerName=computer


You will need to fill the the info your self
Posted by: cnull 19 years ago
Yellow Belt
0
This is mine and it works great. See if you can find anything here that may help!

____________________________________________________

;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386
OemSkipEula=YES
TargetPath=\WINNT

[GuiUnattended]
AdminPassword=********
OEMSkipRegional=1
TimeZone=15
AutoLogon=Yes
AutoLogonCount=0
OEMDuplicatorstring=**********

[UserData]
FullName="*************"
OrgName=*****
ProductID=*****-*****-*****-*****-*****

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=60

[Identification]
JoinDomain=DOMAIN

[Networking]
InstallDefaultComponents=No

[NetClients]
MS_MSClient=params.MS_MSClient

[TapiLocation]

[OEM_Ads]
Background=image.bmp

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0

______________________________________________
Posted by: Michael_W 19 years ago
Yellow Belt
0
Hello,

I've just noticed your question about sysprep and the productkey. You posted your sysprep.inf file content to the messageboard and I've noticed the following:

[UserData]
ProductID=*****-*****-*****-*****-*****

This Should be:

[UserData]
ProductKey="*****-*****-*****-*****-*****"

This was a change in servicepack 1. You have to use the deployment tools provided with this servicepack!!

Hope this helps.

Regards,
Michael Waterman
Posted by: robpow 19 years ago
Yellow Belt
0
Don't know if it is an XP SP2 sysprep thing but ours is called sysprep.inf, not sysprep.ini

Try and use the setup manager to generate it.

Also, the ProductKey or ProductID is dependent on what media the original XP installation was done with, OEM and Volume License media have got different names.

Cheers,
Matt
Posted by: roysmith123 19 years ago
Senior Yellow Belt
0
I noticed that you do not have the following in your sysprep.inf file.
[Unattend]
UnattendMode=Fullunattended
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
UpdateInstalledDrivers=Yes
OemPnPDriversPath=%systemroot%\system32\drivers
DriverSigningPolicy=ignore
Posted by: roysmith123 19 years ago
Senior Yellow Belt
0
I've currently got everything working on my sysprep unattended mode, but now I need to make it work with Ghost's capability to apply a computer name to the machine. I've had problems in the past with Ghost not joining the Domain correctly, but it would name the machine correctly. In Sysprep.inf, there is a line that states "computername=*", I realize that that means autogenerated, but in order for Ghost to name the computer, would I have to remove this, or is there some other command needed.
Posted by: tomulcak 18 years ago
Yellow Belt
0
Where does the i386 folder go? I'm also having problems getting sysprep to run a full unattended.
Posted by: tomulcak 18 years ago
Yellow Belt
0
I've had this working before, but I just don't know what I did to break it. We have an Enterprise key for xp. Any assistance would be greatly appreciated. This is my sysprep.inf:

;SetupMgrTag
[Unattended]
UnattendedMode=FullUnattended
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
UpdateInstalledDrivers=no
DriverSigningPolicy=ignore
OemPnPDriversPath="Drivers\audio;Drivers\nic;Drivers\video;Drivers\video\1;Drivers\video\2;Drivers\video\3"


[GuiUnattended]
AdminPassword="password"
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1

[UserData]
ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
FullName="xxxxxxx"
OrgName="xxxxxxx"
ComputerName=*

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

[Identification]
JoinDomain=ChemPoint.com

[Networking]
InstallDefaultComponents=No

[NetClients]
MS_MSClient=params.MS_MSClient
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ