• 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

    Additional Domain Operations

    This section discusses a few miscellaneous domain controller manipulations:

    • Demoting a domain controller, including demoting the last domain controller in a domain

    • Renaming a domain controller

    • Renaming a domain

    Demoting Domain Controller

    Unlike NT PDCs and BDCs, Windows Server 2003 and Windows 2000 domain controllers can be demoted to become member servers. This demotion strips away the services involved with authenticating users and passing out group policies but does not affect the server's name or capability to support applications.

    The domain controller must be able to communicate with its replication partners or it will refuse to accept demotion. If you pull the server off the wire then attempt to demote it, it will stubbornly refuse. In this situation, you are forced to reinstall Windows Server 2003 completely. Also, if the domain itself remains available, you must run metadata cleanup from the Ntdsutil utility to clean out the server name from Active Directory. See Chapter 10, "Active Directory Maintenance," for details.

    Here is a checklist of domain-related services that the domain controller might be hosting:

    • Replication bridgehead. Before demoting the bridgehead server for a site, you should assure yourself that another server is available for inter-site replication. The Inter-Site Topology Generator (ISTG) is responsible for determining the bridgehead server. If you down the ISTG, the remaining servers will realize after an hour that it is not available and they will determine which domain controller will become the new ISTG. See Chapter 7, "Managing Active Directory Replication," for details of the selection process. Determine the identity of the servers using the Replication Monitor, Replmon.

    • FSMOs. Before demoting a domain controller that is also an operations master, you should first transfer the roles to another server. Use Replmon to determine the identity of the FSMOs.

    • Global Catalog. Before demoting a Global Catalog server, be sure that another GC server is available in the site. If you leave a site without a GC, the clients will be forced to go across the WAN and that will hurt performance. Use Replmon to determine the GCs in a forest.

    • Application naming contexts. If you delete the last domain controller in a domain, you must decide what to do with the Application naming contexts that contain DNS resource records. If you have no further need for the DNS zones that have been integrated into Active Directory, you can elect to remove the naming contexts along with the domain. If you want retain the DNS zones, though, you must take steps to configure another DNS server and make it the primary master for the zones.

    • DHCP. Windows 2000 and Windows Server 2003 DHCP servers that are members of a domain rely on Active Directory to determine their authorization status. If you demote all domain controllers, the server will continue to show an Authorized status and continue to pass out addresses. If you want the server to behave otherwise, you must either manually de-authorize it or stop the service completely.

    To demote the domain controller, launch Dcpromo. It will sense that Active Directory is loaded and offer you the option of demoting the server. If this is the last server in the domain, be sure to check that option so that the server will take additional steps to clean out the last vestiges of the domain from the Registry and make the server a standalone server in a workgroup.

    Renaming Domains

    You can now restructure forests by renaming domains and changing the domain hierarchy. The forest functional level must be at Windows Server 2003. The utility that does this trick is called RENDOM. It is not installed by default. You can find it on the Windows Server 2003 CD under \Valueadd\Msft\Mgmt\Rendom.

    You cannot use RENDOM to separate a domain into a separate forest, nor can you merge a domain with an existing forest, so it is not the true prune-and-graft that Microsoft promised for this release, but it goes a long way towards simplifying internal restructurings.

    Renaming Domain Controllers

    If the domain functional level is set to Windows Server 2003, you can rename a domain controller using a new switch on the NETDOM command in the Support Tools. There are two options.

    Rename Using Alternate Name

    This option uses NETDOM COMPUTERNAME to add an alternate name, make that name the primary name, and then remove the original name. The sequence of events is described in Procedure 9.6.

    Procedure 9.6 Renaming a Domain Controller Using NETDOM COMPUTERNAME

    1. From a command prompt at the console of the domain controller you want to rename, issue the following command to assign an alternate name to the server (be sure to enter the fully qualified DNS name, not just the flat name):

      netdom computername <old-name> /add:<new-name>
      
    2. Verify in DNS that the new name is registered.

    3. Issue the following command to make the new name the primary name for the server:

      netdom computername <old-name> /makeprimary:<new-name>
      
    4. Restart the server so that the new name will take effect.

    5. Following the restart, open a command prompt once again and issue the following command to remove the old name:

      netdom computername <new-name> /remove<old-name>
      
    6. Verify that the server now has only one name using the following command:

      netdom computername <new-name> /enumerate
      

    At this point, if you look in DNS or in the Properties window for the server, you'll see only the new name.

    Rename by Replacing Primary Name

    This option uses NETDOM RENAMECOMPUTER to replace the primary name of the domain controller in one swoop. You can also use the command to reboot the server with a few seconds delay (configured at the command line) so that the new primary name takes effect. The syntax is as follows:

    netdom renamecomputer <old-name> /newname:<new-name> /reb: 1
    

    Following restart, the server registers its new name with DNS, which will be its primary name in Active Directory.

      Previous Section Next Section