Solved

Restoring server for dev purposes

Posted on 2013-01-09
8
217 Views
Last Modified: 2013-01-15
Hi,

I'm suppose to restore a server from a backup, change its name, give it a different domain and plug it in back to live network however I think there will be an issue with it. If I change the restored computer name, eventually it'll contact the domain and change its name there hence affecting the production server, right?

I obviously don't want to test it because it might screw everything up so I'd rather ask if this is the case or how can I do it, to have dev server cloned from production on the same network?

Thanks.
0
Comment
Question by:JurajUQU
  • 5
  • 2
8 Comments
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 38761465
Your best bet would be a clear install... run it from the Windows CD, delete the Windows partition ald others found, recreate the Windows partition the same size or larger and perform a full install. If you don't do a clean install, it will be more work in the long run and a few headaches on the way.

Before doing all that, I suggest downloading a the latest Bios and drivers so when you install, you will be bettter prepared.

If it's a Dell, you can go to www.dell.com/support and enter the service tag. It will bring up all the drivers and bios updates.

Hope this helps!
0
 
LVL 5

Author Comment

by:JurajUQU
ID: 38761468
I think you misunderstood me. I have the production server and it's working fine, I just want to restore it into virtual environment and have a clone of it for testing purposes.
0
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 38761495
Oh, that's much different. You will need to change the name, IP and other items before it will run properly.
0
 
LVL 5

Author Comment

by:JurajUQU
ID: 38761539
Could you be more specific what items? Would it mess up with my current setup?
0
 
LVL 26

Assisted Solution

by:Leon Fester
Leon Fester earned 200 total points
ID: 38762130
The main thing that can go wrong when cloning a physical to virtual (P2V) is the SID of the new computer.

Granted you will change the name and IP's, but the SID will be copied from the old server.
You don't mention how you'll be restoring, but if you've got virtual systems available then rather look at the native tools available to complete this task.
VMware and Hyper-V both have instructions and tools on how to do this.

Some links that may help to answer this and other questions:
http://www.vmware.com/products/converter/overview.html
http://communities.vmware.com/message/1129526
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1000528
http://searchservervirtualization.techtarget.com/tip/Top-5-tips-for-P2V-conversion-success
http://technet.microsoft.com/en-us/library/bb740912.aspx
0
 
LVL 5

Author Comment

by:JurajUQU
ID: 38764779
I'll be using Shadow Protect to accomplish this and yes, I'm going virtual with the dev/test system.

But even if I'll change SID, won't it affect connectivity to the domain of an existing production machine? That is my biggest fear as it would obviously create lot of problems for me and our operation.
0
 
LVL 5

Accepted Solution

by:
JurajUQU earned 0 total points
ID: 38765781
OK so I've done following:

Restored the server into virtual environment with networking
Removed from the AD
Change its name
Ran sysprep to change SID
Changed SN for Windows to get activated and not create conflict with the prod server
Delete any mentions of the AD in registry (though I think this wasn't necessary)
Deleted all the old profiles (ditto)
Made sure that all the services running there are pointing to the dev server
Joined back to the domain

And it works fine!
0
 
LVL 5

Author Closing Comment

by:JurajUQU
ID: 38777617
dvt_localboy reminded me to change the SID from which I've developed a step-by-step solution that worked
0

Join & Write a Comment

The saying goes a bad carpenter blames his tools. In the Directory Services world a bad system administrator, well, even with the best tools they’re probably not going to become an all star.  However for the system admin who is willing to spend a li…
Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now