RE: How do I create a Backup Domain Controller?



Hello Bob,

First I recommend you refer to the following information to your questions:

1. I guess I should start with the basics by asking if it possible to have
one DC back up another?
A: Yes.

2. By backup, I mean that if one DC is shutdown, can users still log on to
the domain by somehow automatically finding another DC?
A: Yes.

3. I'm thinking this is possible by configuring another machine using the
"configure your server" wizard called "Creating an additional domain
controller for an existing domain".
A: Yes.

4. I would think DNS must be in place on the BDC so that client machines
can find the BDC when the PDC is shutdown.
A: You can install DNS on the second DC.

5. I suspect that my GC is not being fully replicated (if at all) to the
BDC because when the PDC is shutdown, I'm unable to use AD-U&C to change
user passwords or create new users. When I try this, I get messages that
the global server is not operational. Using "AD Sites and Services" and
viewing "NTDS Settings" properties of each DC, I see that the connections
tab has the other server listed for replications to-and-from. I notice
however that the "Global Catalog" check box on the "General" tab is only
checked on the PDC; not the BDC. I don't know if that is good or bad.
A: If in a single Forest, a single domain, you needn't worry about GC as GC
only is used in a complex AD environment. You can leave GC alone.

Regarding your scenario, I recommend you setup the shares for Roaming
Profiles and Redirection Folders on a File Server rather than DC.

In the meantime, I recommend you first read some articles to have a clear
idea about AD and DNSR knowledge before you configure the servers:

Active Directory Collection
<Windows Server TechCenter > Windows Server 2003 Technical Library >
Windows Server 2003: Technical Reference > Windows Server 2003 Technical
Reference > Technologies Collections>
http://technet2.microsoft.com/WindowsServer/en/library/7cb7e9f7-2090-4c88-8d
14-270c749fddb51033.mspx?mfr=true

DNS Design for the CDC Scenario
<Network Services > Network Services Planning Guide>
http://www.microsoft.com/technet/itsolutions/wssra/raguide/NetworkServices/i
gnspg_2.mspx?mfr=true


Other Info
==========
The following articles describe the mechanism that Windows XP
Professional/2000 uses to locate a domain controller in a Windows-based
domain:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314861

How Domain Controllers Are Located in Windows
http://support.microsoft.com/kb/247811/EN-US/

I hope this helps.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.



Relevant Pages

  • RE: NT4-->W2K3 Upgrade, Domain Change Revisted
    ... The domain name can be changed in Windows NT4. ... Stop all BackOffice services such as Exchange, SQL Server, and IIS. ... is necessary for each BDC to successfully change to the new domain name. ... If the name can be changed during upgrade it would save ...
    (microsoft.public.windows.server.migration)
  • Re: FSMO roles and BDC.
    ... It isn't a BDC unless it is running NT rather than Win2000+. ... I know I was using wrong terminology but the DC that has the FSMO roles is a win2k server and the other DC is win2k server and it also has exchange2003. ... To reiterate what herb said, Exchange on a DC, while supported, is NOT considered a best practice. ... Now I've seen some people recommend no more than one GC and others recommend every DC is a GC. ...
    (microsoft.public.windows.server.general)
  • Re: In-place upgrade vs migration to Windows 2003
    ... Yes, for the foreseeable future, ALL NT BDC's will remain Windows Nt until ... initial server will be affected by the 4gb partition limitation since it was ... previously an upgraded Windows NT BDC. ... > My personal preference is to upgrade. ...
    (microsoft.public.windows.server.migration)
  • Re: nt 4 upgrade to windows 2003 server question
    ... The following procedure describes how to safely rename a Windows NT domain. ... Stop all BackOffice services such as Microsoft Exchange Server, ... This will cause the entry for the new domain to ... necessary for each BDC to successfully change to the new domain name. ...
    (microsoft.public.windows.server.general)
  • RE: HELP: smooth migration from NT 4 to a new server on Windows 2003
    ... I think you can install Windows NT BDC on the new server that you want to ... it to PDC. ...
    (microsoft.public.windows.server.migration)