Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replacing an Old DC/File Server

Status
Not open for further replies.

Beau71

MIS
Jul 18, 2006
87
US
I am planning on replacing an old server that is on it's last leg. Currently, it acts as a DC (Not the only DC in the Domain) and a File Server.

I want to start making a list of To-Do's so that this is a smooth transition.

A majority of the logon scripts reside within the NETLOGON folder. All the user's profiles and home directories are also on this server.

My plans are to run two servers and slowly migrate over to the new one. But I would like suggestions and things that have gone wrong in the past for some of you.
 
I'm not sure what you're looking for - also not sure what else you have. Migrating off a 2000 or 2003 domain controller to a new 2003 R2 domain controller? You've really left a lot of detail out of this that would really be helpful.

Tell us what you have and what you're replacing it with and what your requirements are otherwise and we can better help you.
 
Old server, is Windows 2003 Standard SP1. It is 1 of 2 DC in our domain, it is also a GC server.
The hardware is almost 4 years old now, and I feel is a major point of failure should something go wrong with it. It has 2 xeon 3.0 GHz with 3.5 GB of RAM. It contains 271GB of user and company data. I would like something with a little more RAM so 2003 Enterprise would be a must.

I want to eventually eliminate this server all together and move to a new server or 2 new servers. I have never performed anything like this before. I have done exchange migrations and I have added/removed DCs to a domain, but I have never replaced a DC.

We are running in Windows 2003 Domain Functional level.

Let me know if you need to know anything else
 
I don't think Enterprise is a must, but I would recommend 64bit.

I'd certainly recommend moving that much data to a dedicated file server, and moving the DC functions to a separate box.

There are a couple of posts here that go into some detail as to what you'll want to do - even step by step.

All of your login scripts should be in the netlogon folder structure. If not, you should clean that up first.

And remember, robocopy is your friend.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
What are the advantages of a 64-bit Windows Server over a 32-bit.
 
What's the advantage of a Corvette over a Yugo? 64bit is far better. It can handle resource allocation better, supports more memory, etc. It's in your best interest to research it further, as it's certainly worth it if your apps (those being installed on that server) support it.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top