{UserData]
ProductID="1111-2222-3333-etc"
[GUIunattended]
AdminPassword="*"
This article has tons of info on it:
http://www.svrops.com/svrops/documents/xpunattend.htm
--
Scott Baldridge
"NIC Student"
Microsoft Picture It! MVP, MCSE
>.
>
Microsoft offers you some help in creating the unattend.txt file with a
utility called Setupmgr.exe. This program can be found on the XP Pro CD
under Support\Tools in the Deploy.cab file. Setup Manager will walk you
through creating an unattend.txt file. However, it doesn't support every
aspect of unattend.txt so you might have to edit the file in Notepad after
using Setup Manager to add stuff like the product id, the domain to join,
the admin pw, etc.
--
Scott Baldridge
"NIC Student"
Microsoft Picture It! MVP, MCSE
> Which box or boxes do you click to finish the sysprep exe.
> >
Here is the general procedure for creating a image
1. Install Windows XP
2. Configure it with the applications and settings you want
3. Expand deploy.cab from the Windows XP CD-ROM to c:\sysprep
4. Run c:\sysprep\setupmgr.exe and choose to create a sysprep.inf. You
should supply all the information you want to preset. Anything you don't
provide you in the sysprep.inf you will get prompted for
5. Backup the c:\sysprep folder since we will delete this afterwards so if
you need to make changes you have your files
6. Run c:\sysprep\sysprep.exe
7. Choose to regenerate sids and click reseal
8. Computer will shut down
9. Use your imaging software to create a image
10. Deploy the image to the machine
11. On 1st boot you will run through the sysprep mini-wizard. If you have
all the information you need in your sysprep.inf this should be automated.
Some notes
You need to ensure that the machines you are deploying to are the same HAL
as the source machine. If you are deploying to the same model# as where you
are creating your image you should probably be okay.
If the target machine is different then you may have to use the
sysprepmassstorage section to account for different mass storage drivers.
You can run sysprep -bsmd prior to step #6 to populate the sysprep.inf with
all the inbox mass storage drivers to account for this.
--
Scott McArthur [MSFT]
"NIC Student" <nos...@nospam.land> wrote in message
news:eBpU2Y1A...@TK2MSFTNGP10.phx.gbl...
I am having the same problem.....Did you ever get a
resolution for this?
>.
>