Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So far I have not used cloning as an option for new computers, but now I have a problem because i need to install about 50 computers with the same setting and installed programs.

How do you troubleshoot a computer name after cloning, SID changing, diferent hardware etc.. Nevermind if its xp, vista, 7, 8 or linux... Wich metods are you guys use for stuffs like this ?

sory for bad english if it is

share|improve this question

closed as off-topic by kce, Tim Brigham, TomTom, MadHatter, mdpc Dec 9 '13 at 19:46

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking product, service, or learning material recommendations are off-topic because they tend to become obsolete quickly. Instead, describe your situation and the specific problem you're trying to solve." – kce, Tim Brigham, TomTom, MadHatter, mdpc
If this question can be reworded to fit the rules in the help center, please edit the question.

Windows Deployment Services. This will address all of your concerns regarding hostname, SID, etc.

(There are other options, such as Altiris Deployment Solution, and others, but WDS should get you started on a path.)

share|improve this answer
That will not use definitly, cooust to much money and licence for server etc. and i will use cloning this time its spending money. What do u use for cloning @danbig? – sergio Dec 9 '13 at 17:10
Reliable and functional cloning or imaging solutions are not likely to be cheap. – DanBig Dec 9 '13 at 17:11
I say you must be joking for bringin wds in talk, its spending money for nothing or something but wds zomg, acronis could make things good. – sergio Dec 9 '13 at 17:14
@sergio: Your time is money. – Iain Dec 9 '13 at 17:22
Well what money? 50 computers and no active directory is a ouch in itself. As in - not professional. Voting to close. – TomTom Dec 9 '13 at 18:43

Nevermind if its xp, vista, 7, 8 or linux...

No, this DOES matter. If you're deploying linux, you're stuck with the abomination known as clonezilla, which has serious limitations.


If you're deploying Win 7/8 you're in luck because you can use Microsoft's free tools to deploy, no need for a server, MDT lite touch can be hosted from any Windows 7 system. If WDS really is out of the question, then you would just use MDT to build the WinPE boot media for you.

computer name after cloning, SID changing, diferent hardware etc

Computer name can be dealt with using MDT lite touch, you would use a variable to assign names with serial numbers, location, or even formfactor.

If the reference image is built and sysprepped in a VM, its hardware agnostic,

If you organize drivers in MDT in make/model hirearchies you can use the driver group variables to point them at the right folders based on the %Make% %Model% Variables detected by WMI at boot in WinPE.

MDT lite touch will build the images for you, and then you can roll out those images with MDT again.

Use The Microsoft Deployment Toolkit. WDS is optional, as its really only needed for PXE boot and multicasting. If you're looking for a FREE solution, it's hard to beat Microsoft's Deployment Toolkit, which is series of consoles and scripts to manage and automate the Windows Assesment and Deployment Toolkit.

While Alteris is a decent product, many of the features of MDT make it a somewhat outdated product.

Key benefits of MDT lite touch:

  • Speed up deployments- MDT is fast, It can image a system in 10min flat.
  • Improve standardization - Reducing Image count allows you to standardize the environment you support.
  • Automate deployments - Tedious and monotonous tasks are easily automated with MDT
  • Reduce Costs - MDT is free, and since it saves you time, it saves you money.
  • Scalable deployments - Start small, and take it to the next level with a deployment database down the road. or WDS integration.

But more than just imaging, MDT does more...

It names workstations, installs software on the fly for you (reducing image count) joins to the domain for you, (and it's free).

share|improve this answer

Want it cheap? What you're not paying on products/solutions is definitely gonna cost you more time. Here are some solutions I used in the past.

  • Sysprep + cloning
  • dd/CloneZilla/PING + newsid.exe
  • Automated USB drive deployment with WinPE, sysprep/WAIK and lots of testing + planning

Changing hardware will result in a different image usually. Changing already deployed software will result in a different image usually. Changing Windows version will result in a different image usually...

so much factors.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.