Changing servers – GUID issues with Domain Name

0 pts.
Tags:
Active Directory
DataCenter
Desktops
DHCP
DNS
Hardware
Management
Microsoft Exchange
Microsoft Windows
Network management software
Network protocols
Networking
Networking services
OS
Security
Servers
SQL Server
Hello all, Basically, we have an old windows 2000 small business server, which is running exchange, SQL, ISA and much more. So we are running out of space on a few of teh drives and considering that we are using RAID we cant just add a drive and repartition the C drive to get more space. So the general consensus is that we buy a new server with windows 2003 and exchange 2003, etc... I spoke to a friend of mind who told me that when we change the server, we will have to update all of the client computers because of the new GUID for teh domain name. So even if we use the same domain name the clients wouldnt connect to it because it would have a different GUID. Im assuming this is true, and I am wondering if anyone knows a way around this. In other words, once the new server is up and running can I change the GUID of the domain name? Also please, if anyone could give me the best advice and/or plan to switch out these servers with the least amount of down time. Thanks Adam
ASKED: July 24, 2006  3:08 PM
UPDATED: July 25, 2006  9:54 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

You can make a disk image of the whole system, expand/repartition your drive, then restore the image to the new drive. This way you get to keep the GUID.

I never ran any imaging tools I have on a SBS but I’d assume there’s no issue, as it’s just a bundled win2000 server. I have run Win2000 server imaging many times and never had any issue, except when I need to move things to an entirely different machine.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TNGeorge
    This looks to me like, a time to make some changes. The suggestion to image the old system on to a reconfigured hard drive system, you would not be able to get it to run easily with all new hard ware, is a good idea that can be expanded. Your Win 2k system should be updated. How about a Win 2003 Server R2 with the hosting software addition so that it can host your old system, which you would migrate with the Windows tool and not mess up the original system until it all works. The virtual system then could be used until your done, at which time you add roles to the Win2003 system permit it to take over the domain and evolve the whole network forward? That way it costs you a new machine and OS and some work that should not destroy any thing important.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following