Discussion Locked

New & moved PC deployments

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our organization has purchased several new Dell PCs with XP Pro preinstalled (each with its own license). I need to deploy these to users and add additional software they currently have installed. Also, their old systems will be moved to other users who use different software. What is the best way to complete these deployments without having to manually wipe and install everything many times? Sysprep and cloning? I was concerned about license keys. We are a non-profit so cost is important. Our network is a Windows Server 2003 Active Directory environment. Thanks for any help and ideas.

15 replies

by sawan gupta

1. Add the new systems to the existing domain. 2. Configure the RIS (Remote Installation Server).
3. Whenever the user will login on to the new systems, he/she will get a prompt to install the softwares which he/she is allowed to use (and which are currently not available on that system).

Regards,
Sawan Gupta

by charliespencer

Sawan's correct, the easiest way in the long run is a Remote Installation Server. However, depending on how many machines and how often you do upgrades, it may be faster to go with Sysprep'ed clones. If you don't know how to use RIS or don't have a server set up, you may lose more time learning that utility than using the imaging tools you're already comfortable with.

by tech_lady

I've never done either one, but I'm anxious to learn and cut my time spent! I briefly looked at RIS, and if what I read is correct, it requires quite a bit of disk space which is low on our server right now, and I don't think it's set up either. Right now I have 5 new PCs and will be moving the 5 PCs they replace & possibly moving a couple more. We plan to order another batch of 5 & do the same thing shortly. I was looking at using open source Clonezilla together with Sysprep to prepare my image. Any experience with this? Since we're non-profit and haven't paid for imaging software I was looking at open source. Thanks for all the help.

by charliespencer

If you're only dealing with ten new systems and ten or twelve used ones, then installing, configuring, and learning RIS is a waste of your time.

I've no experience with Clonezilla, although someone else here may sound off. MS provides a lot of info about using Sysprep, but basically:

*Follow your imaging tool's instructions for making a boot disk
*Configure a PC with all the software you want on it.
*Copy the Sysprep installation files to the system
*Insert the bootable CD and then run Sysprep
*Reboot the system from the boot disk and make an image.
*Reboot the system from the hard drive and allow Sysprep to do it's thing.
*Boot the subsequent systems with imaging boot CD, install the image, reboot from the hard drive and wait while Sysprep runs.

by forum surfer

In the short term, Palmetto is correct. With imaging, it will be far easier and you will get results faster.

I would also look into Windows Deployment Service. RIS acts as more of an automated installer, whereas WDS is an imaging service. We use it and love it. It is a bit tricky to setup properly. Luckily for you, if you haven't done either...it's all tricky so that kind of evens the playing field.

:)

Sounds like you should try experimenting with the open source products that you mentioned since you have limited server resources. You never know till you try. Good luck!

WDS does have some long term benefits. I can use it to deploy server 08, 03, Xp and Vista. If you're a larger shop this is very beneficial. Although now that we've moved to more virtual servers, the automation is handled differently. But for those actual new hardware based Microsoft servers, it is very handy.

by charliespencer

I'd never heard of WDS. RIS is overkill for my site, but I'll look into WDS. Maybe it's what I need. I assume it will do W7?

by tech_lady

Wow! Thanks for all the information and help. I'll look into WDS for future, but for now I think I'll try the OpenSource Cloning & Sysprep route. I'll let everyone know how it goes. I currently oversee about 50 workstations and 7 servers at 7 locations, but one main Dell PowerEdge 2800 server here. This will be a good experience for me and (hopefully)a timesaver. ;)

by dmambo

I use UBCD4Win (free!). It has DriveImageXml. I had no experience in this when I looked into it, but now it takes me about an hour to get a fully configured machine out to a user.

When I need a new image, I get the PC all set up, sysprep it, and then boot to the UBCD and create an image stored on a NTFS USB notebook drive. It's pretty easy. In order to create the boot CD, you do need a CD copy of XP.

by charliespencer

I use Bart-PE and Ghost32 myself, but aren't both of these combinations a bit of overkill if all you're doing is imaging? Wouldn't using the imaging utilities "Make Boot CD" tool be easier than configuring UBCD or Bart? The BIOS should recognize the USB drive.

by tech_lady

I'm working on getting the systems I ordered and received replaced at no charge. I accidentally ordered 'desktops' instead of 'mini-towers' and we prefer the latter. Same cost, so we're sending them back. I'll report how it goes AFTER I get the new systems and can do the first system setup, sysprep & cloning. So, for now the project is on hold, but it should not be more than a few days. Thanks again for all the ideas and input to a newbie in the imaging world.:)

by charliespencer

you can practice on it. No need to wait on the new iron, and you'll be more relaxed practicing new skills on a system that won't be going into use.

Don't hesitate to post questions as you go. Remember to use the 'Ask a Question' button instead of 'Start a Discussion'.

by ron k.

As you know, the question was posted almost at the very same time as I submitted my article to you. I was sitting on pins and needles waiting to see if it was going to be published so that I could provide a link here. You beat me to it.
I hope that it's helpful.

by ron k.

Some minor details are missing but as everyone's migration will likely be unique I didn't think they were worth including.
For instance, during a 40GB migration, XP MCE to XP Pro, -not described in the blog- there were 166,000+ files to be moved and over 311,000 settings. The number of files didn't surprise me as that's easy to determine. The number of settings was a little bit shocking.

This discussion is closed to new replies.