Imaging 2008 R2 without causing network conflicts?
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Already had changed computer name and IP prior to the initial network connection when it did cause conflict so looks like all I need to do now is sysprep.
Next time around that I intend to do a backup of the original server for the same purpose of creating a duplicate but test system I should do sysprep on the original win2008 r2 server first and then make an image? Maybe not in this case because it already has a production application?
Next time around that I intend to do a backup of the original server for the same purpose of creating a duplicate but test system I should do sysprep on the original win2008 r2 server first and then make an image? Maybe not in this case because it already has a production application?
authoritative restoration can help you in the best way..
see the article
http://technet.microsoft.com/en-us/library/cc779573%28WS.10%29.aspx
all the best
see the article
http://technet.microsoft.com/en-us/library/cc779573%28WS.10%29.aspx
all the best
Was this a DOMAIN CONTROLLER?
ASKER
The original server was NOT a domain controller (thankfully) !
Then you just corrupted the computer account. Disjoin from the network, rename the machine, and rejoin. You should be ok (DO sysprep first though).
You could of course also restore the server to a LAN that is completely separated from the original LAN. For a testing environment that should always be the way to go anyway, regardless of whether you clone your systems or do fresh installations.
ASKER
Yeah I thought of setting it up in a sepearte LAN but we need all users to be able to access and test with this duplicate system so they need to be on same LAN in order to connect.
Next time around that I intend to do a backup of the original server for the same purpose of creating a duplicate but test system I should do sysprep on the original win2008 r2 server first and then make an image? Maybe not in this case because it already has a production application?
Definitely not! You are not sysprep'in your original production machine at all! Next time you will backup your production server and restore on the desktop test machine which is not physically connected (until you complete the SID and IP changes)the network then you will run sysprep on the recovered test machine and make the changes!
1-Machine name
2-SID (Since Windows 7/2008 family involved Newsid software cannot be used. Sysprep will do the work perfectly)
3-IP
In addition, if the major app that you have mentioned hosting a web application with particular DNS entry then you may need to create a record for it. If not its not an issue. Probably you may need to update/change the apps name aswell.