WillShakespeare
MIS
Hi All,
Here's the sitch:
We have recently gotten rid of our NT 4.0 machines, and are now totally W2K. All works fine.
However, if our main DC goes down, we have SLA to fix within 4 hours. ALthough this may or may not be possible, we also have to supply a workaround within 30 minutes. In this case, that would mean logging on to another backup server, and carrying on with business.
Problem is that when we installed the GC on a second W2K DC, and then brought down the main DC, no one could log on.
Can anyone list steps, or point me to decent information, about how to create a 2nd Backup AD DC to take care of logons when our main server goes down? Please?
Also, and importantly, we cannot create a new server. We would simply have to promote one of our existing servers for this task. DCPROMO is what we would use for this.
Thanks in advance all,
Will
![[morning]](/data/assets/smilies/morning.gif "[morning] [morning]")
Here's the sitch:
We have recently gotten rid of our NT 4.0 machines, and are now totally W2K. All works fine.
However, if our main DC goes down, we have SLA to fix within 4 hours. ALthough this may or may not be possible, we also have to supply a workaround within 30 minutes. In this case, that would mean logging on to another backup server, and carrying on with business.
Problem is that when we installed the GC on a second W2K DC, and then brought down the main DC, no one could log on.
Can anyone list steps, or point me to decent information, about how to create a 2nd Backup AD DC to take care of logons when our main server goes down? Please?
Also, and importantly, we cannot create a new server. We would simply have to promote one of our existing servers for this task. DCPROMO is what we would use for this.
Thanks in advance all,
Will