Discussion Locked

New Domain or Promote/Demote with DCPromo

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a site, that I want to Add a second server to, problem is the old 2003 box might have a few unknow issues, takes over 1 minute to login to the system, and often pauses without reason.

So, the Old server is a 2003 standard box, with SP2 on it, I have Exchange Server 2003 also on it.
My thoughts are:
1. Add new server to the domain via dcpromo, install Exchange Server on it, move User & Email data, adjust the users likes from the old server. Then I would demote the old server, Dcpromo the New server to PDC, reload the old one and install it as a BDC with DFS and SQL Replication (SQL not existing yet). Leaving the Exchange on the New server.

2. Install the New server, with a new .local domain name. Setup Exchange Server, Create the user base, copy the data from the old server to the new. Use EXMerge to pull old Exchange Data, and manually reinsert that data to each users new account on the NEW server.

Then I would need to touch all 33 systems to manually remove them off the old domain, reboot, and attach them to the new domain.

Using option 2, I feel I would insure less longterm issues that might pull from the old domain, like the 'long login problem', but It would take twice as long unless someone has a better suggestion.

The site is about to add a $12,000 app with SQL Express to it, and having the most on speed, and No outages or troubles is where this needs to go.

2 replies

by sebastian zdrojewski

I would most definitively pass for the "add a new DC to the domain and stabilize it" option. This because moving accounts, workstations, settings, emails (!!) to another server can be a real pain. I would add the new domain controller, promote it to master of all operations, make it Global Catalog and primary DNS for the forest and make sure the new infrastructure is working properly, as well as if the authentication issue has been solved (maybe the logon process takes long time because the DC is too heavily loaded and unable to distribute quickly the GPOs). Then install Exchange (well, actually I would install it on another server), move the mailboxes from the old information store(s) and then make it the primary mail server. Uninstall Exchange, demote the old DC from being a GC, verify if the structure is still working properly. If everything is done well until this point there should be no kind of outage (as well as for next steps). Once the new server is in production, unload AD from the old DC and rebuild it from scratch (maybe after doing an ASR backup to avoid situations like "oh damn!! I forgot there is a critical service on the server!!"). Rebuild AD and you should have the situation restored. What I should not suggest is to put SQL Server on the same server running DC, what for sure I would NOT do is to put SQL Server on the same server running Exchange (even if Express). For some best practice and customer customer sites (as well as my own) I found that for a reasonably small environments (<100 users/clients) the DCs can be virtualized if you have issues with hardware (cost/space).

by dumphrey

and I have found that Exchange and dhcp on one sever works well with SQL on its own server and A DC with DNS on a thirds server. I actually have a virtual copy of our DC on my laptop I can use when planning longer server downtime for the DC, and in case of emergencies.

But I would definately give Exchange a fast disk, this seems to help its performance. We have our server running on a 3Ghz Zeon with 2 GB of ram, and processor usage is never over 20%, and averages about 4%. But thats only dealing with maybe 2000 mail a day, we havea good hardware spam filter in line before the mail server. A good multi core server could run a DC and exchange server on the same hardware if you had seperate physical disk arrays for them and around 4 GB of ram.

This discussion is closed to new replies.