cloned machines and sysprep

I know that its good practice to sysprep machines that are cloned but what symptoms would you get if you had several pc's on the network that were cloned from the same image and not syprepped? I understand about SID's being the same etc.

Its not something I would do - I'm just asking if sysprepping a pc that does not like the network and keeps hanging, very slow browsing the network etc.
This pc has been renamed a couple of times but not sysprepped recently.

any ideas?

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

Devilsbane

I've done it before and experienced no issues. As long as you rename the computers. In my experience, my image had a batch file in the run once part of the registry that renamed the computer and then joined it to the domain.

hyperrawr9000

I had a problem once with my VM labs after cloning 5-6 copies of a win 2003 server. The first 2 worked fine but the rest were giving me errors when I tried to join them to the domain. I dont remember what the errors were but the solution i found on google required me to regenerate the SIDs with a tool that microsoft no longer offers because they say that duplicate SIDs dont cause problems anymore or something like that.

crrussell3

This article is worth reading: The Machine SID Duplication Myth (and Why Sysprep Matters) - Mark's Blog - Site Home - TechNet Blogs

neathneathneath

crrussell3 wrote: »

This article is worth reading: The Machine SID Duplication Myth (and Why Sysprep Matters) - Mark's Blog - Site Home - TechNet Blogs

An awesome article.

Thanks all, maybe its just a network card / switch incompatibility problem i've got with an oldish pc.

Thanks.