• Chapter 1. Installing and Configuring Windows Server 2003
  • software development Company Server 2003
  • Chapter 1. Installing and Configuring Windows Server 2003
  • New Features in Windows Server 2003
  • Best Practices
  • Moving Forward
  • Version Comparisons
  • Hardware Recommendations
  • Installation Checklist
  • Functional Overview of Windows Server 2003 Setup
  • Installing Windows Server 2003
  • Post Setup Configurations
  • Functional Description of the Windows Server 2003 Boot Process
  • Correcting Common Setup Problems
  • Chapter 2. Performing Upgrades and Automated Installations
  • New Features in Windows Server 2003
  • NT4 Upgrade Functional Overview
  • Upgrading an NT4 or Windows 2000 Server
  • Automating Windows Server 2003 Deployments
  • Moving Forward
  • Chapter 3. Adding Hardware
  • New Features in Windows Server 2003
  • Functional Description of Windows Server 2003 Architecture
  • Overview of Windows Server 2003 Plug and Play
  • Installing and Configuring Devices
  • Troubleshooting New Devices
  • Moving Forward
  • Chapter 4. Managing NetBIOS Name Resolution
  • New Features in Windows Server 2003
  • Moving Forward
  • Overview of Windows Server 2003 Networking
  • Name Resolution and Network Services
  • Network Diagnostic Utilities
  • Resolving NetBIOS Names Using Broadcasts
  • Resolving NetBIOS Names Using Lmhosts
  • Resolving NetBIOS Names Using WINS
  • Managing WINS
  • Disabling NetBIOS-over-TCP/IP Name Resolution
  • Chapter 5. Managing DNS
  • New Features in Windows Server 2003
  • Configuring a Caching-Only Server
  • Configuring a DNS Server to Use a Forwarder
  • Managing Dynamic DNS
  • Configuring Advanced DNS Server Parameters
  • Examining Zones with Nslookup
  • Command-Line Management of DNS
  • Configuring DHCP to Support DNS
  • Moving Forward
  • Overview of DNS Domain Structure
  • Functional Description of DNS Query Handling
  • Designing DNS Domains
  • Active Directory Integration
  • Configuring DNS Clients
  • Installing and Configuring DNS Servers
  • Configuring Secondary DNS Servers
  • Integrating DNS Zones into Active Directory
  • Chapter 6. Understanding Active Directory Services
  • New Features in Windows Server 2003
  • Active Directory Support Files
  • Active Directory Utilities
  • Bulk Imports and Exports
  • Moving Forward
  • Limitations of Classic NT Security
  • Directory Service Components
  • Brief History of Directory Services
  • X.500 Overview
  • LDAP Information Model
  • LDAP Namespace Structure
  • Active Directory Namespace Structure
  • Active Directory Schema
  • Chapter 7. Managing Active Directory Replication
  • New Features in Windows Server 2003
  • Replication Overview
  • Detailed Replication Transaction Descriptions
  • Designing Site Architectures
  • Configuring Inter-site Replication
  • Controlling Replication Parameters
  • Special Replication Operations
  • Troubleshooting Replication Problems
  • Moving Forward
  • Chapter 8. Designing Windows Server 2003 Domains
  • New Features in Windows Server 2003
  • Design Objectives
  • DNS and Active Directory Namespaces
  • Domain Design Strategies
  • Strategies for OU Design
  • Flexible Single Master Operations
  • Domain Controller Placement
  • Moving Forward
  • Chapter 9. Deploying Windows Server 2003 Domains
  • New Features in Windows Server 2003
  • Preparing for an NT Domain Upgrade
  • In-Place Upgrade of an NT4 Domain
  • In-Place Upgrade of a Windows 2000 Forest
  • Migrating from NT and Windows 2000 Domains to Windows Server 2003
  • Additional Domain Operations
  • Moving Forward
  • Chapter 10. Active Directory Maintenance
  • New Features in Windows Server 2003
  • Loss of a DNS Server
  • Loss of a Domain Controller
  • Loss of Key Replication Components
  • Backing Up the Directory
  • Performing Directory Maintenance
  • Moving Forward
  • Chapter 11. Understanding Network Access Security and Kerberos
  • New Features in Windows Server 2003
  • Windows Server 2003 Security Architecture
  • Security Components
  • Password Security
  • Authentication
  • Analysis of Kerberos Transactions
  • MITv5 Kerberos Interoperability
  • Security Auditing
  • Moving Forward
  • Chapter 12. Managing Group Policies
  • New Features in Windows Server 2003
  • Group Policy Operational Overview
  • Managing Individual Group Policy Types
  • Moving Forward
  • Chapter 13. Managing Active Directory Security
  • New Features in Windows Server 2003
  • Overview of Active Directory Security
  • Using Groups to Manage Active Directory Objects
  • Service Accounts
  • Using the Secondary Logon Service and RunAs
  • Using WMI for Active Directory Event Notification
  • Moving Forward
  • Chapter 14. Configuring Data Storage
  • New Features in Windows Server 2003
  • Functional Description of Windows Server 2003 Data Storage
  • Performing Disk Operations on IA32 Systems
  • Recovering Failed Fault Tolerant Disks
  • Working with GPT Disks
  • Moving Forward
  • Chapter 15. Managing File Systems
  • New Features in Windows Server 2003
  • Overview of Windows Server 2003 File Systems
  • NTFS Attributes
  • Link Tracking Service
  • Reparse Points
  • File System Recovery and Fault Tolerance
  • Quotas
  • File System Operations
  • Moving Forward
  • Chapter 16. Managing Shared Resources
  • New Features in Windows Server 2003
  • Functional Description of Windows Resource Sharing
  • Configuring File Sharing
  • Connecting to Shared Folders
  • Resource Sharing Using the Distributed File System (Dfs)
  • Printer Sharing
  • Configuring Windows Server 2003 Clients to Print
  • Managing Print Services
  • Moving Forward
  • Chapter 17. Managing File Encryption
  • New Features in Windows Server 2003
  • File Encryption Functional Description
  • Certificate Management
  • Encrypted File Recovery
  • Encrypting Server-Based Files
  • EFS File Transactions and WebDAV
  • Special EFS Guidelines
  • EFS Procedures
  • Moving Forward
  • Chapter 18. Managing a Public Key Infrastructure
  • New Features in Windows Server 2003
  • Moving Forward
  • PKI Goals
  • Cryptographic Elements in Windows Server 2003
  • Public/Private Key Services
  • Certificates
  • Certification Authorities
  • Certificate Enrollment
  • Key Archival and Recovery
  • Command-Line PKI Tools
  • Chapter 19. Managing the User Operating Environment
  • New Features in Windows Server 2003
  • Side-by-Side Assemblies
  • User State Migration
  • Managing Folder Redirection
  • Creating and Managing Home Directories
  • Managing Offline Files
  • Managing Servers via Remote Desktop
  • Moving Forward
  • Chapter 20. Managing Remote Access and Internet Routing
  • New Features in Windows Server 2003
  • Configuring a Network Bridge
  • Configuring Virtual Private Network Connections
  • Configuring Internet Authentication Services (IAS)
  • Moving Forward
  • Functional Description of WAN Device Support
  • PPP Authentication
  • NT4 RAS Servers and Active Directory Domains
  • Deploying Smart Cards for Remote Access
  • Installing and Configuring Modems
  • Configuring a Remote Access Server
  • Configuring a Demand-Dial Router
  • Configuring an Internet Gateway Using NAT
  • Chapter 21. Recovering from System Failures
  • New Features in Windows Server 2003
  • Functional Description Ntbackup
  • Backup and Restore Operations
  • Recovering from Blue Screen Stops
  • Using Emergency Management Services (EMS)
  • Using Safe Mode
  • Restoring Functionality with the Last Known Good Configuration
  • Recovery Console
  • Moving Forward
  • Who Should Read This Book
  • Who This Book Is Not For
  • Conventions
  • Acknowledgments
  • About the Author
  • About the Technical Reviewers
  • Index
  • Index A
  • Index B
  • Index C
  • Index D
  • Index E
  • Index F
  • Index G
  • Index H
  • Index I
  • Index J
  • Index K
  • Index L
  • Index M
  • Index N
  • Index O
  • Index P
  • Index Q
  • Index R
  • Index S
  • Index SYMBOL
  • Index T
  • Index U
  • Index V
  • Index W
  • Index X
  • Index Z
  • Preface
  • Previous Section Next Section

    Special Replication Operations

    After you set up your sites and deploy your domain controllers, there shouldn't be much else to do but bask in a job well done. One or two things may crop up, though, that demand your attention.

    Manually Creating Connections

    Given enough time, the KCC will create an intra-site replication topology that converges changes as rapidly as possible. The ISTG will do the same for inter-site replication.

    If a domain controller goes down, it may take a while for the KCC to recognize the problem and begin work to heal the replication ring. If the KCC or ISTG fails to respond in time to forestall an emergency, you can intervene and create a connection manually.

    When you build a manual connection, you interfere with the automatic operation of the KCC. This isn't necessarily a bad thing. The network will not melt down if you make a mistake. But you may find that a domain controller gets into unexpected replication difficulties caused by your actions. Consider all manual interventions carefully before proceeding.

    Moving Server Objects Between Sites

    You may be part of a central IT group that builds new servers for remote locations and then ships them for installation by a local tech or an outsourcing agent. During the domain controller promotion, the local IP address of the server defines its site affiliation. This site may not be correct for the ultimate destination.

    If you change the IP network of a domain controller, or build a new site that is assigned the IP network of an existing domain controller, you need to move the Server object for the domain controller to a new Site container along with the NTDS Settings object and the Connection objects. This is done using the AD Sites and Services console. Drag and drop the server object onto the Server container under the target site.

    After moving a Server object, give the KCC lots of time to set up the new replication topology and change the replication transport from high-speed RPC to low-speed RPC. If you try to force replication before the KCC does its work, you'll get an error. Wait at least a half hour (two KCC intervals) then try again. If it still fails, check the Event log. You may see an error such as the one in Figure 7.19.

    Figure 7.19. Event Log entry showing failure of the KCC to build a connection.


    If you get a connection error, make sure you didn't accidentally associate the site with the wrong IP address. Check DNS to ensure that the SRV records are in their proper places and that the server is configured to point at a functioning DNS server. Also, if this is the first domain controller in the new site, it will become both the bridgehead and the ISTG, which will take a while to configure automatically.

    Manually Controlling Replication Topology

    When the KCC builds a connection, it selects two end-point domain controllers and places a Connection object into the NTDS Settings container for those servers. Connection objects always represent inbound data flows. You cannot change the inbound target of a Connection object, but you can change its replication partner.

    When building manual connections, make absolutely sure that you don't inadvertently put the domain controller into a loop or place the end-point at a domain controller in the forest that does not communicate directly with other domain controllers holding replicas of the same naming contexts.

    Also, the KCC will not delete manual connections when new domain controllers are added to the replica ring or other domain controllers are taken out or fail. You'll need to change the topology by hand after you take manual control of the connections.

    You have two choices when manually controlling replication topology: you can select a new replication partner for a given connection or you can build a new Connection object.

    Selecting a New Replication Partner

    When you are ready to select a new replication partner, follow Procedure 7.11.

    Procedure 7.11 Selecting a New Replication Partner

    1. Open the AD Sites and Services console.

    2. Expand the tree to find the target server and highlight its NTDS Settings icon.

    3. Double-click the Connection object from the domain controller you want to change. This opens the Properties window for the connection (see Figure 7.20).

      Figure 7.20. Properties window for <automatically generated> connection showing its replication partner.


      The Replicate From field contains the name of the replication partner, the partner's site, and the domains that are replicated from that partner. In the example, the target server is in the Subsidiary.com domain and is not a Global Catalog server, so it does not replicate any other naming contexts.

    4. In the Replicate From field, click Change. The Find Domain Controllers window opens. If you have an extensive forest, this list might be fairly long.

    5. Double-click the domain controller that you want to be the server's new replication partner. This closes the window and returns you to the Properties window. The new replication partner is listed in the Server field.

    6. Click OK to save the changes and close the window. The DRA sees the change and begins replication from the new partner. If this is an inter-site connection, it may take a while for replication to occur.

    Building New Connections

    When you are ready to create a new connection between domain controllers, do as directed in Procedure 7.12.

    Procedure 7.12 Building a New Connection Object

    1. Open the AD Sites and Services console.

    2. Expand the tree to show the contents of the NTDS Settings container under the server for which you want to build a connection. There should already be at least one Connection object designated <automatically generated>. This was built by the KCC.

    3. Right-click the NTDS Settings object and select NEW NT DS CONNECTION from the flyout menu. The Find Domain Controllers window opens.

    4. Select the domain controller from which you want to build a connection. Remember that Connection objects always represent inbound data flows.

    5. Click OK. The New Object – (Connection) window opens. The name of the domain controller you selected is inserted in the Name field.

    6. Click OK to save the change and return to the console. The new Connection object appears on the list. You should keep an eye on the Event log to make sure the DRA sees the new connection and replicates across it. You may need to enable Active Directory diagnostics to do this. See the next section.

      Previous Section Next Section