2000 to XP Upgrade Unattended

[Netwacky87]

Evening All!!!

 

Got a problem with an upgrade task thats gotta be done in about a weeks time!!!

 

I want to upgrade our 2000 computers (about 85/100) to XP, i want to do this; remotely, unattended, over the network and easily

 

Now, im getting a little stuck ive followed this guide but nowt luck!!

 

Here's how to perform an unattended upgrade from Windows 2000 to Windows XP - Windows XP Setup

 

Any help appreciated!!!

 

Mart

[powdarrmonkey]

Can you give some more information? What happens when you run it, any errors?

[Netwacky87]

Nope non at all, ALTHOUGH i should point out that im puttin this into a .bat file in the XP folder, if thats any help?

[strawberry]

the batch file needs to be called, ideally at logon. Use something like ranger remote control or bozteck vnc scan to log onto stations and attached the batch file as the startup script for the user account.

[powdarrmonkey]

I'd do it at startup, then a) you dont have to log every machine on and b) a user can't log off half way through upgrade

[Michael]

Although the guide you've linked to should work (in theory) the amount of network traffic it will generate is huge. You'd be much better off formatting a workstation, installing Windows XP (with Service Pack 3) - you may also want to checkout my Post XP SP3 Pack too then run Sysprep (with the answer file), then create an image from this point.

 

You'll find the re-imaging process to be much quicker (with all applications newly installed), rather than installing XP on each workstation, which in practice takes about 40 mins - 1 hour. It will probably take longer because of the amount of network bandwidth used!

[Netwacky87]

Hiya Michael,

 

Trouble is i need to have this all done within a week so i just want to literally do it all unattended!

 

Can anybody suggest any other way of doing this fast? aswell must point out that the computers all have different hardware

 

Not good! Although....if it comes down to it, ill just have to go around one by one (but please....save me work! lol)

 

Mart

[ChrisH]

Go to the forums on MSFN - Where People Go To Know and get reading. Basically you need to create create a super install disk for XP.

Things you will need to use are

Nlite

BTS Driver Packs

 

Identify groups of machines that are the same and Install one of each of these types. Then clone to the others.

I have had success recently using drive image XML with a BartPE Disc and and external hard drive. I use this method for small one of batches at the mo while I convert from RIS to WDS.

 

The keep the drivers option on the driver packs may cut down on the images you will have to create.

 

You will of course need to sysprep. Theres an example file in the WDS thread.

[SYNACK]

If you want to do it unattended with inplace installs the simplest and easiest way would be to deploy the winnt32.msi file from a central server to all of your clients using GPO. It will just install like any other deployed software.

 

How to use Group Policy to deploy Windows XP in a Windows Server 2003-based network

 

customizing the winnt32.msi - MSFN Forums

 

If your not using volume media you may need to do this:

JSI Tip 6339. The Winnt32.msi package prompts for a Product ID when you use Non-Select Media?

Edited August 16, 2008 by SYNACK

[powdarrmonkey]

What's the urgency? I really, *really* wouldn't hurry into something like this...

[Netwacky87]

What's the urgency? I really, *really* wouldn't hurry into something like this...

 

I have deployed Office 2007 over the summer and im sure you kno, ive gotta upgrade all the windows 2000 machines! Dont ask me...Boss's decision lol

[Michael]

I have to agree with the others; a project like this should of been planned months and months ago. Don't get me wrong, I have re-imaged that many machines in a week - but with ready made images (and tested) for each model of hardware.

 

Re-imaging and doing things from new will pay off. Deploying Office 2007 will undoubtedly be easier as part of an image as many users have experienced problems deploying it.