1Jul/083
Successfully deploy a ghost Image to Many computers at the same time.
My Scenario: Need to format and install XP Pro on 33 Dell Dimension PC's, same model and components. Need to fix the "same computer name" problem because the computers will be joining the network.
Non-Explained solution:
Install XP on one computer, download all updates, drivers, install software needed in all computers, set up Sysprep, shut down, boot up Ghost and create image, Run GhostCast server, load up image, Boot Hirens Cd (or ghost network floppy) on the computers and Multicast the Image to All of the computers. Simple Huh? ![]()
Tutorial after the break.
What you need:
- A network =) and a computer in the network with enough space to host the ghost image (~6GB or ~3 with max compression)
- Norton GhostCast [download] - Comes with Symantec Ghost Corporate Edition 2003
- Windows Deployment Tools (SYSPREP) - Located In your Windows XP Cd under SUPPORT>Tools>DEPLOY.CAB or, [download here]
- Hiren's BootCD [download] (and an empty CD to burn it to) or Network Boot Disk.
Here are the steps:
- Install your OS, Drivers, Apps on a computer.
- Extract the contents of Deploy.CAB or SYSPREP.ZIP on a folder on your image computer.
- Run the Setup Manager(setupmgr.exe) and Create a new answer file.
- Select Sysprep Setup and your desired OS
- Fully automated.. - Change the desired settings and make sure to add a computer name

- Finish and Create your sysprep.inf file.
- If you want to fix the Computer name set up error, open the sysprep inf file you just created with a text editor (ie. notepad) and look for the line that contains ComputerName=[yourvalue], edit it and add a asterisk to the end of it. Save It(What this is doing is automating the whole set up but then the asterisk is going to cause an error, allowing us to input the desired computer name, and after that it is fully automated again!).

- Open Sysprep.exe and press Ok
- Check the "Use the Mini-Set Up" Option, Insert your Hirens Boot CD into your CD drive, and press the Reseal Option (caution: It shuts down your computer).

- Set up your BIOS to boot from your CD drive and start your computer from the cd.

- Select Disc Clone tools & Then Norton Ghost > Ghost with network support.

>
>
- You dont need to add a cd, and you dont need to log on to your domain either.. actually I recommend not doing it, because of the "multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed" error.
- Start GhostCast Server on the computer you will be having the computer image stored.
- Set your session name, set the create image option, browse where your image is going to be stored and press Accept Clients.

- Back on the other computer;press Ok, select Ghostcast>Multicast
(If you dont see this, is because the BootCD couln't detect your network card.. try restarting or good luck on making your network floppy
!! ) - Join the session you created in Step 14.

- Select the drive to create the Image, Press Ok
- Select Compression and Proceed with Image Creation.

- Once your image file is stored on your computer, start the computers you want this image to be replicated into and boot to Hiren's BootCD (Repeat steps 10-12 on all the computers).
- Repeat step 14, but this time select Restore Image and browse the image file you created in step 17.
- Join the Session in all of your computers and then; on your computer running ghostcast server, Press the [Send] Button.
- Once the image restore is complete you can go ahead and restart the computers and this will set up the computers automatically and ask you for the computer name(Ignore step 7 if you don't want the set up to do that)
Good Luck! ~anebg
October 26th, 2011 - 10:53
Thanks for the information.
I am currently in charge of managing a small school lab consists of shared computers, and found your post really useful.
By the way, I was wondering if I can use this method to deploy an image of hard drive with system rollback software like Returnil enabled on it. I mean, I want to prevent users from making permanent changes on the system partition, so that I can ensure that the computers remain clean between sessions.
Also, if I am allowed to do that, there would be a chance that I need to renew the rollback, for example, I would sometimes run Windows Update, or install an application for everyone to use. Can I use the same method used in the first deployment, so that I can easily apply changes to all computers?
In case if you have a better suggestion, I would be happy to hear that too. Please let me know.
Thank you.
October 26th, 2011 - 12:09
Technically, all that you would have to do is to install Returnil before you ship the image and every once in a while update all the software and re-deploy the image.
Or you could get into more interesting stuff like installing WSUS on your (if you have a) Domain Controller and allowing Returnil to apply updates through it.
Good luck!
October 26th, 2011 - 20:51
Thanks, again.
Actually, I was already thinking of doing that–to have Returnil set up before the deployment–and I haven’t tried it yet, because of some rising concerns on my mind.
What I am concerned of is Returnil’s behavior–on every reboot, it discards all changes made on the system partition. Because of this behavior, I have to disable it before installing either update or new software (which would definitely make changes on the system partition) and enable it again when I am done with those tasks.
Does any step on your post involves making changes on the system partition, so that I would have to temporarily disable Returnil for that period? (Possibly “Resealing” on System Preparation Tool? (Step 9))