I had a question regarding making an unattended win2k3 install cd.

I have a 3-in-1 (ent, std, web) install cd that I made.

My question is how does this change me following the winxp unattended guide?

Is the cd's dir structure different? Do I need extra paramenters or whatnot ?

How can I choose which install to use automatically?

I don't mind if the unattended part comes after me choosing which win2k3 version I want to install on bootup, I just wanted to know what changes/additions I have to make when following the guide.

Thanks

It should be same as win2k and xp, but i haven't gotten around to server 2003 yet. I figure a new server won't come out until around 2006, so i got time to learn win2k3.

-gosh

win2k unattended is a little bit different to XP..

There's only slight differences between win2k and xp unattended installs. Both OS use sysprep. You can use setup mgr to make an unattend file for both os. The main difference between win2k and xp unattended installs is xp has MUCH better documentation. But if you can do an unattended install for win2k, you'll have no problem doing an unattended install for xp or server 2003.

-gosh

and vice versa much information used in xp unattended can be used in win2k unattended.

well.. win2k winnt.sif has some different syntaxes.. and the setupmanager from xp could not be used for win2k, because of that.

also there are many switches for XP, which 2k does not support..

i know.. winnt.sif is just a "small part" of unattended setup. but.. it´s the most important =)

also the DirectX install guide from the XP unattended guide don´t work.

and there are many/some other issues..

like i told "win2k unattended is a little bit different to XP.. " see: "a little bit "..

well.. this was offtopic..

minghia:

do it like you should.. take a look at <cd>:\SUPPORT\TOOLS\Deploy.CAB

there is much info about unattended setup...

compare the info of the unattended guide on this side with the info in the deploy.cab and you´ll get your perfect sollution