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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failover using W2k3 Server

Status
Not open for further replies.

ngagne

Technical User
Joined
Sep 14, 2001
Messages
323
Location
US
Since there is no group for 2003 Server, I figured I would post this here.

Currently, we have a system running W2K Server as the PDC. This is the only server on our network currently. It has come to a point where we need to implement another, more powerful server as our PDC and demote the current server to a "failover" status. Simply put, I would like to do this:

1.) Build the new server using W2K3 Server.
2.) Replicate the AD to the new server (Server 1) from the old.
3.) Demote the old server (Server 2).
4.) Promote Server 1 to PDC.
5.) Rebuild Server 2 with 2k3 Server.
6.) Promote Server 2 as a secondary DC.

In the event of a failure of Server 1, is it possible to instigate an automatic failover of Server 1 to Server 2, while remaining transparent to the clients WITHOUT using CSC?

What I am trying to accomplish is a simple means of providing as much uptime as possible if Server 1 goes down. If Servers 1 and 2 are trusted nodes, and provided that AD replication is in place, can users log on to Server 2 and continue to work while Server 1 is repaired? Server 1 currently serves as a logon server, Exchange Server, and file server. I would like to mimic these features on the new server (i.e. Exchange Server on Server 2 would take over mail handling if Server 1 was down, and using DFS and FRS users would still have access to their files on the server).

Any help here is appreciated.

TIA,
Nate

 
BTT...anyone?

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top