Systems Deployment

create a sysprep.inf file containing something like what you see below, and put this in the c:\sysprep of your image. When you execute SYSPREP, select reseal and "Mini-Setup":

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
TargetPath=\WINDOWS
ExtendOEMPartition=1, nowait

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
FullName="blah blah"
OrgName="blah blah Inc."
ProductKey=PUTYO-UROWN-SERIA-LNUMB-RHERE

[Display]
Xresolution=1024
YResolution=768
Vrefresh=75

[TapiLocation]
CountryCode=<your country code>
Dialing=Tone
AreaCode=<your area code>

[Identification]
JoinWorkgroup=WORKGROUP

(or set it to join a Domain with appropriate creds (this file gets deleted upon boot))

[Networking]
InstallDefaultComponents=Yes

[GuiRunOnce]
Command0=c:\temp\startup.vbe <some script you want to launch after setup

I actually did the same, just wondering why it would not work.

I could automate the serial key by editing oobeinfo.ini file as

[Version]
ProductKey =”XXXXX-XXXXX-XXXXX-XXXXX-XXXXX”

but i am still prompted for Admin Password and couple of other questions like internet connectivity...etc. not sure if they can be automated.

Also the Source Windows XP CD is embedded with SP2 unless that can cause it. I know that Sysprep folder gets deleted after it's complete but i don't know why the system dosn't understand the sysprep.inf file i create every time....is there some way to know whats happening there.

Thx

Well, that sysprep.ini file was generated using the MS utility called setupmgr.exe (which is in the deploy.cab file of W2k3 Tools). You SHOULD be able to use that utility to generate a sysprep.ini that will work for you, the ini generated should include admin creds written right into it, though you may opt to edit out the computername value and such specifics that that tool will put in that INI also. Hope this helps.

not sure if you've resolved your question. Here is are items you should be able to use to answer your last post:

Add this to the [UserData] section:
ComputerName=*
This will generate a random computer name automatically. (your product key should go there to; not sure why thats not working)

The Admin password entry should go under the [GuiUnattended] section:
AdminPassword="adminpassword"

Internet setting should be covered by adding these sections to the [Networking] section:
InstallDefaultComponents=Yes

If this doesn't work, it may be an SP2 thing and the format of the sysyprep.ini file. This is what I use for my Win XP SP1 sysprep process. Let us know if you are having any succcess

Ben

Thank you for the response

I am able to automate couple of inputs offered in Windows welcome wizard.
Though i created the sysprep.ini file but i am not sure of it's significance while doing -reseal.

When computer comes up first time after -reseal command i.e. the Windows welcome wizard, it seem to consider the file called oobeinfo.ini which is at C:\Windows\system32\oobe in my case.

On refereing the ref.chm file in WinXP Sp2 deploymernt tools i could customize the welcome wizard and was able to skip couple of question asked during that.

Finally i am looking for how can i avoid the screen of adding additional user information during Welcome wizard. I am not able to find much input on this in the help file.

Then minimizing the no. of images using -factory will be my next Project.

Not quite sure what you mean, as I am just testing out a WinXP SP2 deployment stragedy. In my inital testing of sysprep w/ SP2, here is my basic sysyprep.inf file (which results in no user interaction and a complete unattended install of the basic Windows XP SP2 installation):

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

[GuiUnattended]
AdminPassword="password"
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=1
OEMDuplicatorstring="Test Win XP SP2"
TimeZone=20
OemSkipWelcome=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="Company User"
OrgName="Company Name"
ComputerName=*

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

[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=612
LongDistanceAccess="9"

[RegionalSettings]
LanguageGroup=1
Language=00000409

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

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

This was purely created with the setupmgr.exe app. I have yet to start tweaking it beyond this. Hopefully this is of some help.

Be aware that the file is called sysprep.inf not .ini!

okie...got it..
Does any one know about oobeinfo.ini
Thats where it picks...inputs while windows welcome screen..
I could skip most of screens...by refering to ref.chm in win XP Sp2 deployment tools...
but ...can some one tell me ...if there is a way to skip the screen which as for adding additional users...to the computer...?

Come on guys!

I am sure some one can help me here

My Question is about welcome pages in Windows XP (Welcome Wizard) appears after running the PC for the first time after sealing it (using Sysprep -reseal). I know to customize the welcome pages using oobeinfo.ini file..

But not able to find a work around for one option which offers to add users to the install.

Does any one know to skip that page asking for additional users to be added to the Windows XP install?

Thanks
Karan

Using the sysprep.inf sample from above, I don't get any welcome screen. I actually get 'left' logged in as the local Administrator.

I concur with Ben, verify your sysprep.inf - you should not have to mess with any other files to control this. Perhaps you are working with XP Home Edition?

Guys!

It's not just about sysprep.inf.

Here is what I did

Installed a Fresh Windows XP with slipstreamed SP2
Installed couple of Standard Softwares (Office 2003, Adobe 7.0, WinZip)
ran sysprep.exe -factory with Reboot and no SID gen Option
after that i ran sysprep.exe -reseal with Shutdown and SID Gen Option
NOW
System is ready for imaging the Disk using whatever tool.
This is the knowlegde i have....about preparing the master image... Opinions are appreciated.

After i start this computer... a Windows Animation comes up then a welcome wizard with 12 questions....
How to Automate....these 12 steps...

I want to attach screen shots, can some one suggest me how...can i do that....it seems i do not have permissions

Hi Karan,
what do you want do hear? Several people are telling you to alter your sysprep.inf. Have you tried it?
The oobeinfo.ini file should be used only by OEM for preactivation. Read this:
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/oempreac.mspx
And now, please try things, Kyle and Ben suggested to you.
Regards, Nick

Hi Nick!

I tried modifying the sysprep.inf file. But it does not automate the mini wizard after i do.. sysprep.exe -reseal. I am not sure if i am doing it right. Do you have some step by step instructions... also i am trying this on a VMWare...instance.. that should not make it different though... I will post my sysprep.inf file....

Also my primary question stays...
If i use oobeinfo.ini... how can i avoid the screen which ask to add additional users to the operating system...


a section in oobeinfo.ini as below... actually tells the wizard to add users as local admins..

[UserInfo]
Identity000 = "UserName Goes Here"
Identity001 = "UserName Goes Here"

IF I SKIP THIS SECTION ....I HAVE TO FILL IN THE SCREEN PRESENTED IN THE WIZARD...
IS THERE A WAY I CAN AVOID ADDING ADDITIONAL USERS TO THE INSTALL... I JUST WANT DEFAULT LOCAL ADMINISTRATOR ACCOUNT AND NOTHING ELSE..

Ok as a solution what i accepcted as..is

If i specify values for Identity000 in [userinfo] section of oobeinfo.ini... then it does not give me the screen for adding additional users....

though...does any one know....how can we specify password for the accounts i specify in [userinfo] section of oobeinfo.ini?? since it gets created with blank password otherwise.

Thanks
Karan