Cloning 2003 server

Hi I cloned a 2003 server and had issues with accessing the original server again

Changed IP and computer name, in hindsight I left it on the same production network

Is there a guide to sysprep and clone a 2003 server , if the steps could be outlined that would be great

I didnt change production network as didnt think it was necessary, why is this important thanks
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
If you had changed the IP Address and Computer Name of the CLONE (but make sure you removed from the Domain OFF the network) there should not have been any issues.

Was this a domain joined Windows computer ?

What issues did you have accessing the original computer ?

If you started the CLONED computer on the original network, it would have caused issues with the original computer on the network, and the Domain.

You must make sure the CLONED computer is never restarted on the production network initially, and all changes need to be performed whilst it's not on the network, only after removing from domain, changing computer name, and changing IP Address OFF the network, should it be re-connected back to production network.

As for Sysprep, just run it and Shutdown.
Indie101Author Commented:
Thanks Andrew, got the error message "Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, computer a\c not found"

This was a domain member server, apologies meant to include that in question

I changed IP and computer name of the cloned machine straightaway should i have powered off original 2003 server before doing this

I shouldnt have had cloned pc on the same network,point taken, i didnt take it off the network,

Going back is it a case of taking off the network and making the changes, or do I need to use sysprep, thanks again
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It is recommended to use Sysprep, that's what Microsoft recommend.

BUT, always do it when the computer is not connected to the network!
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Lee W, MVPTechnology and Business Process AdvisorCommented:
Actually, sysprep is unsupported for use on production machines.  It's intended to be used after configuring the system as you want it BEFORE cloning (imaging is the correct term).
Indie101Author Commented:
So I guess the only option is to do as above and remove cloned pc from the network before changing IP and computer name

I will power down the original before doing so, thanks
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No need to powered down original.

Just make sure the CLONE when you power on is disconnected from network!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.