Imaging 2008 R2 without causing network conflicts?
Posted on 2012-12-30
I have a production windows 2008 R2 with a major production application installed that I cloned for purpose of creating a test environment. I used the built-in backup\imaging from windows 2008 R2 (works same in windows7) and restored it to a desktop PC.
As soon the desktop was connected to the network the production machine lost domain trust relationship (by the way I didn't connect it to the network-somebody else did by mistake).
I know changing the computer name is not sufficient as there is a SID that I think should be changed. Can I use windows SYSPREP on the cloned desktop in this situation (i think sysprep is typically for pre-imaging but don't want to do this on production system as I was able to get production running again after deleting & re-joining the domain).
I heard about a program called NewSid but it is retired.
Since I do need this test desktop to be on our network how can safely join it to the domain without causing problems again for the production original?