automatic installation 1

[Bignewbie]

Hi guys,

could someone help me find the details on how to make winxp complete the installation itself without me having to input in the computer name, serial number, etc.? I need to install winxp on 10 pcs, cloning the harddrive would have been ok, unfortunately these pc dont have the same configurations, such as video cards, some have even serial mouse and some have ps/2. thanks in advance!



biggie




The Man of Tomorrow is forged by his battles today.

 

[DallasKelsey]

First, you need to create an administrative installation point (can't remember how to do this) which means you will need a server that can hold the files necessary--essentially the contents of the \i386 directory on the XP setup CD--and then you will want connectivity, preferably with NICs that handle 10/100Mb connections. You will then need to boot these PCs somehow to connect to the server via LAN without an OS on their harddrives--either a PXE or RIS boot using the PC's NIC or via floppy/zip or even CD boot from a disk that has the appropriate files to boot to the network on it (consult your NIC or PC manufacturer if you do not know how to do that).

Then consult these sites for resources regarding setting up and distributing XP via unattended installation:

http://www.msfn.org/unattended/xp/members.htm

http://www.microsoft.com/technet/tr...prodtechnol/winxppro/reskit/prbc_cai_nmip.asp

http://support.microsoft.com/default.aspx?kbid=291997&product=winxp

If you do not have the Enterprise version of the media, you will still need to activate each installation (whether via file or manually)--otherwise, this step isn't necessary. If you install with no code, the installation will pause on each system and ask for a registration code/product ID.

Finally, you may consider a third-party tool to hlpe you do this--I use Deployment solution from Altiris (

http://www.altiris.com/).

You can go there and download a trial--which I *think* allows for up to 10 PCs...


Dallas S. Kelsey, III
DKelsey-at-CHGLaw-dot-com
Cox, Hodgman, & Giarmarco, P.C.
Troy MI 48084

 

[bcastner]

You do not need:

. a server with an "administrative installation point"
. an "Enterprise" code
. a "third-party" tool

The Microsoft deployment tools for XP have all you need. I do agree with DallsKelsey on one issue, that is that you should look to the msfn.org site for assistance:

http://www.msfn.org/unattended/xp/gettingstarted.htm

You can use the deployment tools to enter multiple license keys and create an unattended answer file for product CD-keys, you can even depending on license encrypt the keys:

Service Pack 1 adds an encryption feature to unattended setups of Windows XP. This feature is applicable to customers with volume licensing agreements with Microsoft such as Microsoft Select, Microsoft Enterprise Agreement, and Microsoft Open License. Customers who place a VLK in an unattended setup file (unattend.txt) will be able to encrypt the VLK such that it will be time-limited (in increments of 5–60 days) and not visible as plain text. This feature provides customers deploying Windows XP with an additional layer of protection by obscuring the VLKs in unattended installations.

How to Use VLK Encryption
Scenario 1
To protect for 30 days SMS-based, RIS-based, or network file share-based installs using the volume licensing version of Windows XP:

From the command prompt, run:
winnt32/encrypt:"XXXXX-XXXXX-XXXXX-XXXXX-XXXXX:30"/unattendath_to_destination_unattend_file[/Q]
The resultant hash value is written to the specified unattend file, overwriting any existing ProductKey or ProductID entries.
A message box displays whether the process succeeds or fails due to an error.
If the /Q switch is used, information about the success or failure is written to the file %Windir%\Winnt32.log
The product key entry in the unattend.txt file is functional for 30 days after the date of encryption.

A script to re-encrypt the key regularly could be created to ensure that a new encrypted key is always available for the install. The Task Scheduler could also be used to schedule this task to be repeated automatically.
Scenario 2
To protect for five days a CD-based install using the volume licensing version of Windows XP:

From the command prompt, run:
winnt32/encrypt:"XXXXX-XXXXX-XXXXX-XXXXX-XXXXX:5"/unattendath_to_destination_unattend_file[/Q]
The resultant hash value is written to the specified unattend file, overwriting any existing ProductKey or ProductID entries.
A message box displays whether the process succeeds or fails due to an error.
If the /Q switch is used, information about the success or failure is written to the file %Windir%\Winnt32.log.
The product key entry in the unattend.txt file is functional for five days after the date of encryption.

The unattend file could then be placed on a floppy disk or burned to a custom CD image to provide a short-lived CD for CD-based installations.

http://support.microsoft.com/?kbid=299840

http://support.microsoft.com/?kbid=302577

And Daniel Petri's notes:

http://www.petri.co.il/activate_with_sysprep_installations.htm

 

[kippy13]

Will this work on PC's of different hardware configs?Eg will a different boot disk be needed for each NIC?
Would manually doing this task be quicker?

***************************************
Looking for the best answers:
faq222-2244
Keeping your system clear of malware:
faq608-4650
***************************************

 

[bcastner]

Kippy13,

The question was unattended install, not a "ghost" or RIS image push down.

 

[kippy13]

Apologies, I have not come across this before and I didnt see unattended install mentioned in the first post.
I intend to read up on all the links you mention above and perhaps do some testing.
Thanks as always.

***************************************
Looking for the best answers:
faq222-2244
Keeping your system clear of malware:
faq608-4650
***************************************

 

[DallasKelsey]

My bad... I guess I assumed that someone setting up 10 PCs with different hardware configurations will not have or qualify for a select or enterprise level agreement. I suppose one could be a MOLP cumstomer with 10 PCs, but that was not mentioned either.

It is true that RIS/PXE/Admin installation point is not required--I re-read my post and can see where that could be the conclusion. It is not required. Neither, however, is doint it any one specific way. More than one way to skin a cat, you know.

However, network-based installs can simplify rollouts of multiple PCs...and you can have multiple PCs build themselves simultaneously using these scenarios--provided their hardware is not horribly divergent.

A third party tool is not required, and I did not say it was. They can, however, and do automate 95% of the BS and tend to take the time required to deliver the finished systems way, WAY down, particularly for a newbie--and howabout creating/editing the Unattended.txt file via GUI? Not required, but helfpul, nonetheless.

And yes, this will work for different hardware configurations, but there are some situations where one will need to provide for 3rd party drivers and so forth (especially when using the occaional SCSI controller instead of IDE drives to host the OS). And yes, each diferent NIC will require a different boot disk--unless, of course, they are UNDI compliant and can use standard PXE drivers to boot. Again, this depends on the NIC and the manufacturer. Also don't forget that service packs CAN be delivered ex post facto--though it may be a better approach to set them up during rollout.

Dallas S. Kelsey, III
DKelsey-at-CHGLaw-dot-com
Cox, Hodgman, & Giarmarco, P.C.
Troy MI 48084

 

[JillofAllTrades]

bcastner - Thanks for the valuable info on making installation CD's that expire! I have been struggling with providing an upgrade CD to certain remote users. ;-)

Christine

 

[bcastner]

You are welcome Christine.