On This PageProcedure DetailsThis chapter gives step-by-step information for the procedures listed in Chapter 3 of this guide. Procedure: Back up System StateThe following procedure backs up system state only. It does not back up the system disk or any other data on the domain controller. Procedure Requirements | • | To back up system state, you can log on at the local computer, or you can enable Terminal Services in Remote Administration mode on the remote domain controller | | • | Credentials: Domain administrators, local administrator, or backup operator | | • | Tool: Backup |
Procedure Steps To back up the system state on a domain controller 1. | Log on to the domain controller by using the account that has domain administrator or backup operator credentials. | 2. | Start the Windows Backup Wizard. | • | From a command prompt or the Run text box, type ntbackup and press ENTER. -or- | | • | Go to Start > Programs > Accessories > System Tools > Backup. |
| 3. | By default, the Always Start in Wizard Mode check box is checked. You can leave this option selected, and click Next. | 4. | Select the Back up files and settings option, and then click Next. | 5. | Select the Let me choose what to back up option, and then click Next. | 6. | In the Items to Back Up window, expand My Computer by clicking the plus sign. | 7. | From the expanded list below My Computer, check the SystemState option, and then click Next. | 8. | Select a location to store the backup. | • | If you are backing up to a file, type the path and filename for the backup (.bkf) file (or click the Browser button to find a folder or file). | | • | If you are backing up to a tape unit, choose the tape that you wish to use. Note: You should not store the backup on the local hard drive. Instead, you should store it in an off-machine location, such as a tape drive. |
| 9. | Enter a name for this backup, and click Next. | 10. | On the last page of the wizard, select Advanced. | 11. | Do not change the default options for Type of Backup. Normal should be selected, and the check box should remain cleared for Backup migrated remote storage data. Click Next. | 12. | Check the Verify data after backup option, and then click Next. | 13. | In the Backup Options dialog box, select a backup option, and then click Next. | 14. | Allow only the owner and administrator access to the backup data and to any backups appended to this medium; click Next. | 15. | In the When to back up box, select the appropriate option for your needs, and click Next. | 16. | If you are satisfied with all of the options selected, click Finish to perform the back up operation according to your selected schedule. Note: The system state can also be backed up using backup from a command line with appropriate parameters. For more information, refer to the command-line reference accessible by typing ntbackup -? from a command prompt. |
Procedure: Back up System State and the System DiskThe following procedure backs up both system state and the system disk. Procedure Requirements | • | To back up system state, you must log on at the local computer, or you must enable Terminal Services in Remote Administration mode on the remote domain controller. | | • | Credentials: Domain administrator, local administrator, or backup operator | | • | Tool: Backup.exe. |
Procedure Steps To back up system state and the system disk on a domain controller 1. | Log on to the domain controller by using an account that has domain administrator, local administrator, or backup operator credentials. | 2. | Start the Windows Backup Wizard by choosing one of the following options: | • | Open a command prompt, type ntbackup and press ENTER. -or- | | • | Go to Start > Programs > Accessories > System Tools > Backup. |
| 3. | Click the Backup Wizard button, and then click Next. | 4. | Select Back up selected files, drives, or network data. | 5. | In Items to Back Up, click SystemState to select it. Then select the drive letter containing the system files, and click the system disk. Click Next. | 6. | In the Where to Store the Backup box, select the backup media type by choosing one of the following options: | • | Choose File if you want to back up to a file. If you do not have a tape backup unit installed, File is selected automatically. -or- | | • | Choose a tape device if you want to back up to tape. |
| 7. | In the Backup Media or File Name box, choose one of the following options: | • | If you are backing up to a file, type a path and file name for the backup (.bkf) file, or click the Browse button to find a folder or file. If the destination folder or file does not exist, the system creates it. -or- | | • | If you are backing up to a tape unit, choose the tape that you want to use. |
| 8. | After you click Next, the Completing the Backup Wizard screen appears. This screen summarizes the options selected for this backup job. Verify that Prompt to replace data is listed in the How category. If it is not, click the Advanced button, click Next until you reach the Media Options screen, and then select Replace the data on the media with this backup. | 9. | Complete the remaining wizard screens, and click Finish to begin the backup operation. When a Replace Data dialog box appears, click Yes to overwrite the existing backup on this tape or file path with this backup. A progress indicator shows the status of the backup operation. |
Procedure: Restart the Domain Controller in Directory Services Restore ModeTo take a domain controller offline, restart it in Directory Services Restore Mode and log on as the local administrator. If you have physical access to the domain controller, you can start in Directory Services Restore Mode locally. When you start Windows Server 2003 in Directory Services Restore Mode, the local Administrator account is authenticated by the local Security Accounts Manager (SAM) database. Therefore, logging on requires using the local administrator password, not an Active Directory domain password. Procedure Requirements | • | Credentials: Directory Services Restore Mode administrator | | • | Tool: None |
Procedure Steps To locally restart in Directory Services Restore Mode 1. | Restart the domain controller. | 2. | When the screen for selecting an operating system appears, press F8. | 3. | From the Windows Advanced Options menu, select Directory Services Restore Mode. | 4. | When prompted, log on as the local administrator. |
Procedure: Allow this Computer to Replicate with all its PartnersProcedure Steps To allow this computer to replicate with all its partners 1. | Open the command prompt. | 2. | Find the outbound partners for this domain controller by typing: repadmin /showrepl /repsto <local domain controller name> and press ENTER. This repadmin command will output a list that contains information about all of the outbound neighbors. For each neighbor, verify that the last synchronization attempt was successful and has a time stamp that indicates it has replicated since restore. | 3. | If replication has not been successful, you can force replication between this domain controller and its outbound partners rather than waiting for the next replication cycle. From a command prompt, run repadmin /syncall /ed /A /P /q. | 4. | Check for replication errors in the output of the command in the previous step. If there are no errors, then replication has been successful. Any replication errors that exist must be rectified in order for replication to be completed. |
Procedure: Restore from Backup MediaUse a good backup containing at least the system state and system disk to restore the server. By performing a non-authoritative restore on Active Directory, you automatically perform a non-authoritative restore of SYSVOL. No additional steps are required. Procedure Requirements | • | To restore system state, you must log on at the local computer, or you must enable Terminal Services in Remote Administration mode on the remote domain controller. | | • | Credentials: local Administrator account | | • | Tool: Backup.exe |
Procedure Steps To restore from backup media 1. | In Directory Services Restore Mode, start the Windows Server 2003 backup utility. Go to Start > Programs > Accessories > System Tools > Backup. | 2. | Click the Restore Wizard button, and then click Next. | 3. | Select the appropriate backup location and ensure that at least the System disk and SystemState containers are selected. | 4. | Click the Advanced button. | 5. | In Restore Files to list, select Original Location, and then click Next. | 6. | In the Advanced Restore Options window, check the boxes for: | • | Restore security. | | • | Restore junction points, and restore the file and folder data under the junction points to the original location. | | • | Preserve existing volume mount points. | | • | For a primary restore of SYSVOL, also check the following box: When restoring replicated data sets, mark the restored data as the primary data for all replicas. A primary restore is only required if the domain controller you are restoring is the only domain controller in the domain. A primary restore is required on the first domain controller being restored in a domain if you are restoring the entire domain or forest. |
| 7. | Click Finish. | 8. | When the restore is complete, click Close, and then click Yes to restart the computer. |
The system will now restart and will replicate any new information received since the last backup with its replication partners. Procedure: Turn off Inbound Replication Using RepadminThis step is required only if the domain, or forest functional level, is Windows 2000 native mode or earlier. By turning off inbound replication, you ensure that changes to group membership originate from the restored domain controller, rather than having the changes overwritten. Procedure Steps To turn off inbound replication using repadmin 1. | From a command prompt or the Run text box, type repadmin /options +DISABLE_INBOUND_REPL and then press ENTER. | 2. | Verify that the option is set. You should get this message: repadmin running command /options against server localhost. |
Procedure: Turn on Inbound ReplicationProcedure Steps To turn on inbound replication using repadmin 1. | From a command prompt or the Run text box, type repadmin /options . -DISABLE_INBOUND_REPL and then press ENTER. | 2. | Verify that the option is set. You should get this message: repadmin running command /options against server localhost. |
Procedure: Mark the Application Partition as AuthoritativeOnce the data has been restored from backup, you must select which objects are to be marked authoritative in order to have them replicated to other domain controllers. Procedure Steps To mark the application partition as authoritative 1. | From a command prompt or the Run text box, type ntdsutil to start the tool. | 2. | At the ntdsutil: prompt, type authoritative restore and press ENTER. For assistance with the Ntdsutil command line-tool, type help at any time. | 3. | Type List NC CRs and press ENTER. NTDSUTIL will output a list of the application partitions that are available after the restore, and the associated cross references. Note the cross-reference distinguished name and application-partition distinguished name that corresponds to the application partition you wish to restore. | 4. | Type restore subtree <App Partition DN>, where App Partition DN is the distinguished name of the application partition noted above. | 5. | Ntdsutil will provide a confirmation dialog. Click Yes to proceed. The output message will indicate the status of the operation. There should be no failures. | 6. | Type restore object <Cross Ref DN> (where Cross Ref DN is the distinguished name of the application partition cross reference noted above) and press ENTER. | 7. | Ntdsutil will provide a confirmation dialog. Click Yes to proceed. The output message will indicate the status of the operation. There should be no failures. | 8. | Quit the Ntdsutil tool. |
Procedure: Mark the Object(s) AuthoritativeOnce the data has been restored from backup, you must select which objects are to be marked authoritative in order to have them replicated to other domain controllers. In order to complete this operation, you must know the full distinguished name of the object you wish to restore. Procedure Steps To mark the object(s) authoritative 1. | From a command prompt or the Run text box, type ntdsutil to start the tool. | 2. | At the ntdsutil: prompt, type authoritative restore and press ENTER. For assistance with the Ntdsutil command line-tool, type help at any time. | 3. | To restore an object, type restore object <object DN> (where object DN is the distinguished name of the object that is to be marked authoritative). If you were to restore a deleted user named John Smith in a corp.contoso.com domain, the command would be similar to: restore object CN=John Smith,CN=Users,DC=corp,DC=contoso,DC=com. Always enclose the distinguished name in quotes when there is a space or other special characters within the distinguished name. | 4. | Press ENTER. Ntdsutil will start the attempt to mark the object as authoritative. The output message will indicate the status of the operation. The most common cause of failure is an incorrectly specified distinguished name, or a backup for which the DN does not exist (which would occur if you tried to restore a deleted user that was created after the backup). | 5. | Quit the Ntdsutil tool. |
Procedure: Verify Active Directory RestoreAfter the restore is completed, you should restart the server and perform basic verification. Procedure Requirements | • | You must log on at the local computer, or you must enable Terminal Services in Remote Administration mode on the remote domain controller. | | • | Credentials: | • | Basic: domain administrator or local administrator | | • | Advanced: local administrator | | • | Tool: Backup.exe |
|
Procedure Steps To perform basic Active Directory verification 1. | After the restore operation completes, restart the computer in Start Windows Normally mode. Active Directory and Certificate Services automatically detect that they have been recovered from a backup. They perform an integrity check and re-index the database. | 2. | After you are able to log on to the system, browse Active Directory. Verify that all of the User objects and Group objects that were present in the directory prior to backup are restored. Similarly, verify that files that were members of a File Replication service (FRS) replica set and certificates that were issued by the Certificate Services are present. |
Procedure: Restore System State to an Alternate LocationPerform this procedure to allow an authoritative restore of SYSVOL. After the objects are restored, you can delete the files in the alternate location. Procedure Requirements | • | Credentials: local administrator | | • | Tool: Backup.exe |
Procedure Steps To restore system state to an alternate location 1. | Click the Restore tab. | 2. | Select SystemState. (You need not restore the system disk to an alternate location.) | 3. | In the Restore Files to drop-down list, ensure that Alternate Location is selected, and designate an alternate location. | 4. | When the restore process is finished, close the backup utility. |
Procedure: Clean up MetadataIf you give the new domain controller the same name as the failed computer, then you need perform only the first procedure to clean up metadata, which removes the NTDS Settings object of the failed domain controller. If you give the new domain controller a different name, then you need to perform all three procedures: clean up metadata, remove the failed Server object from the site, and remove the Computer object from the domain controllers container. Procedure Requirements | • | Credentials: Enterprise administrator (Metadata cleanup requires modifying the configuration naming context.) | | • | Tools: Ntdsutil.exe, Active Directory Sites and Services, Active Directory Users and Computers |
Procedure Steps To clean up metadata 1. | At the command line, type ntdsutil and press ENTER. | 2. | At the ntdsutil: prompt, type metadata cleanup and press ENTER. | 3. | At the metadata cleanup: prompt, type connections and press ENTER. | 4. | At the server connections: prompt, type connect to server servername, where servername is the domain controller (any functional domain controller in the same domain) from which you plan to clean up the metadata of the failed domain controller. Press ENTER. | 5. | Type quit and press ENTER to return to the metadata cleanup: prompt. | 6. | Type select operation target and press ENTER. | 7. | Type list domains and press ENTER. This lists all domains in the forest with a number associated with each. | 8. | Type select domain number, where number is the number corresponding to the domain in which the failed server was located. Press ENTER. | 9. | Type list sites and press ENTER. | 10. | Type select site number, where number refers to the number of the site in which the domain controller was a member. Press ENTER. | 11. | Type list servers in site and press ENTER. This will list all servers in that site with a corresponding number. | 12. | Type select server number, where number refers to the domain controller to be removed, and press ENTER. | 13. | Type quit and press ENTER. The Metadata cleanup menu is displayed. | 14. | Type remove selected server and press ENTER. At this point, Active Directory confirms that the domain controller was removed successfully. If you receive an error that the object could not be found, Active Directory might have already removed the domain controller. | 15. | Type quit and press ENTER until you return to the command prompt. |
If the new domain controller receives a different name than the failed domain controller, perform the following additional steps: Note: Do not perform the additional steps if the new computer will have the same name as the failed computer. Ensure that hardware failure was not the cause of the problem. If the faulty hardware is not changed, then restoring through reinstallation might not help. To remove the failed Server object from the sites 1. | In Active Directory Sites and Services, expand the appropriate site. | 2. | Delete the Server object associated with the failed domain controller. |
To remove the failed Server object from the domain controller's container 1. | In Active Directory Users and Computers, expand the domain controller's container. | 2. | Delete the Computer object associated with the failed domain controller. |
Procedure: Install Active DirectoryDuring the installation process, replication occurs, ensuring that the domain controller has an accurate and up to date copy of Active Directory. For more information about seizing operations master roles, see Installing Active Directory in this guide. After you gather information as described in Gathering Installation Information earlier in this guide, you can use the Active Directory Installation Wizard to install Active Directory. Procedure Requirements | • | Credentials: local Administrator account | | • | Tools: Dcpromo.exe |
Procedure Steps To install Active Directory 1. | In the Run text box, type dcpromo and click OK. | 2. | The Active Directory Installation Wizard appears. At the Welcome screen, click Next. | 3. | For Domain Controller Type, select Additional domain controller for an existing domain. Click Next. | 4. | For Network Credentials, enter the user name, password, and domain for the user account that has permission to add this new domain controller to the domain. Click Next. | 5. | Enter the name of the domain that you want the new domain controller to host. Click Next. | 6. | For Database and Log Locations, enter the paths for the locations of the directory database (Ntds.dit) and the log files. For better performance, store the database and log files on separate physical disk drives. Click Next. | 7. | For Shared System Volume, enter the path where you want to locate the system volume (SYSVOL). Click Next. | 8. | Under Directory Services Restore Mode Administrator Password, enter the password that you want to use when you need to start Directory Services Restore Mode. Click Next. | 9. | The Summary screen displays a list of the items you chose. Verify that the information is correct, and then click Next to proceed with the installation. | 10. | The wizard proceeds to install Active Directory. When it finishes, the wizard displays a summary screen listing the domain and site in which the new domain controller is a member. Verify that this information is correct. Click Finish to close the wizard. | 11. | Click Restart to restart the domain controller. | 12. | Let the domain controller restart. If any message indicates that one or more services has failed to start, restart the domain controller one more time. If the initial replication cycles have not had enough time to complete during the first restart on a new domain controller, some services may be unable to start successfully. If the message appears during additional restarts, examine the event logs in Event Viewer to determine the cause of the problem. |
Procedure: Promote Server to Domain ControllerProcedure Steps To promote a server to domain controller 1. | In the Run text box, type dcpromo /adv and click Next. | 2. | Select Additional domain controller for exiting domain. | 3. | Select From these restored backup files and point to the same location where you had restored the system state data. | 4. | Since the domain controller you are promoting was a global catalog server, the Active Directory Installation Wizard will ask you whether you want this server to also be a global catalog. | 5. | Give appropriate credentials for the operation. | 6. | Enter the domain in which you want to place the new domain controller in. It has to be the same domain of the domain controller whose system state data you are using. | 7. | Continue with the remaining steps of dcpromo. |
Dcpromo will now promote the server to a domain controller using the data present in the restored files. This saves dcpromo from having to replicate every object from the partner domain controller. However, it may have to replicate those objects that were modified (added or deleted) since the backup was taken. If the backup was recent, the amount of replication required will be considerably less than that required for a regular dcpromo. Once the dcpromo operation is completed successfully and the machine rebooted, the restored folder (in the above example: E:\restore) and sub-folders can be removed from the local disk. Procedure: Install and Run Setup Manager to Create an Answer File (Unattend.txt)Procedure Steps 1. | Insert the Windows Server 2003 CD-ROM into the computers CD-ROM drive or DVD-ROM drive. Press and hold down the SHIFT key as you insert the CD to prevent it from starting automatically. | 2. | Start Windows Explorer, and then open the Support\Tools folder on the Windows Server 2003 CD-ROM. | 3. | In the details pane, double-click the Deploy.cab file to open it. | 4. | On the Edit menu, click Select All. | 5. | On the Edit menu, click Copy. | 6. | Create a new folder on your local hard disk. To do this: 1. | Click Local Disk (C:), or click the drive in which you want to create the new folder. | 2. | On the File menu, point to New, and then click Folder. | 3. | In the New Folder name box, type the name that you want, and then press ENTER. |
| 7. | Right-click the new folder that you created, and then click Paste. | 8. | Double-click the new folder to open it, and then double-click the Setupmgr.exe file. The Setup Manager wizard starts. Follow the instructions in the wizard to create an answer file. |
Procedure: Install the DNS Server ServiceAssign a static IP address, rather than a dynamically-assigned IP address, to any computer that acts as a DNS server. To use this procedure, your DNS infrastructure must already exist, function properly, and be configured to use Active Directory-integrated zones. This procedure describes the steps to add an additional DNS server into the DNS infrastructure. Procedure Requirements | • | Credentials: Domain Admin or Enterprise Admin | | • | Tools: My Network Places, Control Panel |
Procedure Steps To install the DNS Server service 1. | Ensure that the computer is using a static IP address. Right-click My Network Places and click Properties. | 2. | In the Network and Dial-up Connections dialog box, right-click the connection that represents the connection this computer uses to attach to your network. The default label is Local Area Connection, but this can be changed, so it might not be labeled the same on your computer. Click Properties. | 3. | In the Local Area Connection Properties dialog box, click once on Internet Protocol (TCP/IP) to highlight it (be sure that you do not clear the check box in front of it), and then click Properties. | 4. | In the Internet Protocol (TCP/IP) Properties dialog box, ensure that Use the following IP address: is selected and that a valid IP address, subnet mask, and default gateway appear. Click OK to close the dialog box. Click OK again to return to your desktop. | 5. | In Control Panel, click Add/Remove Programs. Click Add/Remove Windows Components. | 6. | Scroll down to Networking Services. Highlight it and click Details. | 7. | In the Networking Services dialog box, select the check box in front of Domain Name System (DNS). Click OK. | 8. | Click Next. Provide the location of the installation files, if necessary. After the installation is complete, click Finish to end the wizard, and then click Close to exit Add/Remove Programs. |
Procedure: Gather the SYSVOL Path InformationThis procedure gathers installation information that includes: | • | The user name, password, and the domain that contains the user account that you intend to use to run the Active Directory Installation Wizard. | | • | The name of the domain that you want the new domain controller to host. | | • | Location for the Active Directory database (Ntds.dit). | | • | Location for the log files. | | • | Location for the shared system volume (SYSVOL). | | • | The server Administrator account name and password to use in Directory Services Restore Mode. |
Before you attempt to relocate all or portions of the system volume, you must clearly understand the folder structure and the relationships between the folders and the path information that is stored in the registry and the directory itself. When folders are relocated, any associated parameters that are stored in the registry and the directory must be updated to match the new location. The folder structure contains junctions that might also require updating when folders get moved to a new location. Maintaining the relationship between the folders, junctions, and stored parameters is important when you must relocate all or portions of SYSVOL. Failure to do so can result in files being replicated to or from the wrong location. It can also result in files failing to replicate, yet FRS will not report any errors. Due to the configuration error, FRS looks in the wrong location for the files that you want to replicate. The folder structure used by the system volume uses a feature called a junction point. Junction points look like folders and behave like folders (in Windows Explorer you cannot distinguish them from regular folders), but they are not folders. A junction point contains a link to another folder. When a program opens it, the junction point automatically redirects the program to the folder to which the junction point is linked. The redirection is completely transparent to the user and the application. For example if you create two folders, C:\Folder1 and C:\Folder2, and create a junction called C:\Folder3, and then link the junction back to Folder1, Windows Explorer displays three folders: \Folder1 \Folder2 \Folder3 If you open Folder3, Windows Explorer is redirected to Folder1 and displays the contents of Folder1. You receive no indication of the redirection because it is transparent to the user and to Windows Explorer. If you look at the contents of Folder1, you see that it is exactly the same as the contents displayed when you open Folder3. If you open a command prompt and list a directory, all three folders appear in the output. The first two are type <DIR> and Folder3 is type <JUNCTION>. If you list a directory of Folder3, you see the contents of Folder1. Note: To create or update junctions, you need the Linkd.exe tool supplied with the Windows 2000 Server Resource Kit. Linkd allows you to create, delete, update, and view the links that are stored in junction points. By default, the system volume is contained in the %systemroot%\SYSVOL folder. The tree of folders contained within this folder can be extensive, depending on how your network uses FRS. When relocating folders in the system volume, ensure that you move all folders (including any hidden folders) and ensure that the relationships of the folders do not change unintentionally. When you relocate folders, you need to be concerned with the first three levels of subdirectories in order to properly update the parameters used by FRS. These levels are affected by junction points and parameter settings. These folders include: | • | %systemroot%\SYSVOL | | • | %systemroot%\SYSVOL\Domain | | • | %systemroot%\SYSVOL\Domain\DO_NOT_REMOVE_Ntfrs_ Preinstalled_Directory | | • | %systemroot%\SYSVOL\Domain\Policies | | • | %systemroot%\SYSVOL\Domain\Scripts | | • | %systemroot%\SYSVOL\Staging | | • | %systemroot%\SYSVOL\Staging\Domain | | • | %systemroot%\SYSVOL\Staging Areas | | • | %systemroot%\SYSVOL\Staging Areas FQDN | | • | %systemroot%\SYSVOL\Sysvol | | • | %systemroot%\SYSVOL\Sysvol FQDN |
where FQDN is the fully qualified domain name of the domain that this domain controller hosts. Note: If any of the folders do not appear in Windows Explorer, click Tools and then click Folder Options. On the View tab, select Show hidden files and folders. If you use Windows Explorer to view these folders, they appear to be typical folders. If you open a command prompt and type dir to list these folders, you will notice two special folders are listed as <JUNCTION>. Both folders labeled FQDN are junction points. The junction in %systemroot%\SYSVOL\Sysvol links to %systemroot%\SYSVOL\Domain. The junction in %systemroot%\SYSVOL\Staging Areas is linked to %systemroot%\SYSVOL\Staging\Domain. If you change the path to the folders to which the junctions are linked, you must also update the junctions, including drive letter changes and folder changes. Besides junction points linking to folders within the system volume tree, the registry and the directory also store references to folders. These references contain paths that you must update if you change the location of the folder. FRS uses two values that are stored in the directory. The first value, fRSRootPath, points to the location of the policies and scripts that are stored in SYSVOL. By default, this location is the %systemroot%\SYSVOL\Domain folder. The second value, fRSStagingPath, points to the location of the folders used as the staging area. By default, this location is the %systemroot%\SYSVOL\Staging\Domain folder. The Net Logon service uses a parameter stored in the registry to identify the location of the folder that it uses to create the SYSVOL and NETLOGON share points. By default, this path is %systemroot%\SYSVOL\Sysvol. If you change the paths to these folders, you must update these values. When relocating SYSVOL, you first move the entire folder structure to a new location; then you update all the junction points and the parameters that are stored in the registry and the directory in order to maintain the relationships between the parameters, the folders, and the junctions. Optionally, you can relocate the staging area and leave the rest of the system volume at its original location. In this case, you must update the fRSStagingPath parameter in the directory and the junction point stored at %systemroot%\SYSVOL\staging areas. Procedure Requirements | • | Credentials: Domain Admins | | • | Tools: Regedit.exe, ADSI Edit, Linkd.exe |
Procedure Steps To gather the system volume path information Use the steps below to locate the information and record the current values in Table 1. If you are relocating the staging area, you only need to record information for rows 2 and 5 in Table 1. All other operations require that you record information in all five rows. To restore and rebuild SYSVOL, you must record the information from the domain controller that you are repairing in rows 1, 2, and 3. Use the junctions located on the domain controller that you are copying from the SYSVOL folder structure to record the current value for rows 4 and 5. The new values for rows 4 and 5 are based on the domain controller that you are repairing. Table 1 System Volume Path Information 1. fRSRootPath | | | 2.fRSStagingPath | | | 3. Sysvol parameter in registry | | | 4. Sysvol junction | | | 5. Staging junction | | |
fRSRootPath 1. | In the Run text box, type adsiedit.msc and press ENTER. | 2. | Double-click DomainNC [machinename] (where machinename is the name of this domain controller). Verify that the Domain NC expands to display the domain component (DC=) folder. | 3. | Click the domain component to display the containers and OUs in the details pane. Double-click the Domain Controllers OU to display the containers that represent the domain controllers. | 4. | Double-click the container that represents this domain controller (CN=computername) to display more containers. | 5. | Double-click the CN=NTFRS Subscriptions container. | 6. | Right-click the CN=Domain System Volume container, and click Properties. | 7. | In the Select which properties to view list, select Mandatory. | 8. | In the Select a property to view list, select fRSRootPath. The current value appears in the Value(s) box. | 9. | Record the current value in the table above. Based on the folder structure discussed earlier and the new location, record the new path value for this parameter in the table. | 10. | Click Cancel to close the dialog box. |
fRSStagingPath 1. | In the Run text box, type adsiedit.msc and press ENTER. | 2. | Double-click DomainNC [machinename] (where machinename is the name of this domain controller). Verify that the Domain NC expands to display the domain component (DC=) folder. | 3. | Click the domain component to display the containers and OUs in the details pane. Double-click the Domain Controllers OU to display the containers that represent the domain controllers. | 4. | Double-click the container that represents this domain controller (CN=computername) to reveal more containers. | 5. | Double-click the CN=NTFRS Subscriptions container. | 6. | Right-click the CN=Domain System Volume container, and click Properties. | 7. | In the Select which properties to view list, select Mandatory. | 8. | In the Select a property to view list, select fRSStagingPath. The current value appears in the Value(s) box. | 9. | Record the current value in Table 1. Based on the folder structure discussed earlier and the new location, record the new path value for this parameter in Table 1. |
SYSVOL Parameter in the Registry 1. | In the Run text box, type regedit and press ENTER. | 2. | In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters. | 3. | Sysvol appears in the details pane. The current value is listed in the Data column. | 4. | Record the current value in Table 1. Based on the folder structure discussed earlier and the new location, record the new path value for this parameter in Table 1. |
SYSVOL Junction 1. | At a command prompt, change the directory to %systemroot%\SYSVOL\Sysvol. Note: This assumes that the system volume is still in the default location. If it has been relocated, substitute the appropriate paths into these instructions. | 2. | At the command prompt, type dir. Verify that the fully qualified domain name (FQDN) is listed as type <JUNCTION>. | 3. | At the command prompt, type linkd fqdn (where fqdn is the domain name listed in the Dir output). This displays the value stored in the junction point. Press ENTER. | 4. | Record the current value in Table 1. Based on the folder structure discussed earlier and the new location, record the new path value for this parameter in Table 1. |
Staging Junction 1. | At a command prompt, change the directory to <%systemroot%>\SYSVOL\Staging Areas. Note: This assumes that the staging area is still in the default location. If it has been relocated, substitute the appropriate paths into these instructions. | 2. | At the command prompt, type dir. Verify that the fully qualified domain name is listed as type <JUNCTION>. | 3. | At the command prompt, type linkd fqdn (where fqdn is the domain name listed in the Dir output). This displays the value stored in the junction point. Press ENTER. | 4. | Record the current value in Table 1. Based on the folder structure discussed earlier and the new location, record the new path value for this parameter in Table 1. |
Procedure: Verify DNS Registration and FunctionalityThis test verifies that DNS is functioning so that other domain controllers can be located. Procedure Requirements | • | Credentials: Domain administrator | | • | Tool: Netdiag.exe |
Procedure Steps To verify DNS registration and functionality Note: For a more detailed response from this command, you can use the verbose option. Add /v to the end of the command to see the detailed response. | • | At a command prompt, type netdiag /test:dns and press ENTER. |
If DNS is functioning, the last line of the response is DNS Test..: Passed. The verbose option lists specific information about what was tested. This information can help with troubleshooting if the test fails. If the test fails, do not attempt any additional steps until you determine and fix the problem that prevents proper DNS functionality. Procedure: Verify that an IP Address Maps to a Subnet and Determine the Site AssociationUse this procedure to determine the site to which you want to add a Server object prior to installing Active Directory, or to verify the appropriate site prior to moving a Server object to it. To be associated with a site, the IP address of a domain controller must map to a Subnet object that is defined in Active Directory. The site to which the subnet is associated is the site of the domain controller. The subnet address, which is computed from the IP network address and the subnet mask, is the name of a Subnet object in Active Directory. When you know the subnet address, you can locate the Subnet object and determine the site to which the subnet is associated. Procedure Requirements | • | Credentials: Domain users | | • | Tools: | • | My Network Places | | • | Active Directory Sites and Services (Administrative Tools) |
|
Procedure Steps To verify that an IP address maps to a subnet and determine the site association 1. | Log on locally or open a Terminal Services connection to the server for which you want to check the IP address. | 2. | On the desktop, right-click My Network Places, and then click Properties. | 3. | In the Network and Dial-up Connections dialog box, right-click Local Area Connection, and then click Properties. | 4. | Double-click Internet Protocol (TCP/IP). | 5. | Use the values in IP address and Subnet mask to calculate the subnet address. | 6. | In Active Directory Sites and Services, expand the Sites container, and then click the Subnets container. | 7. | In the Name column in the details pane, find the Subnet object that matches the subnet address. | 8. | In the Site column, note the site to which the IP subnet address is associated. |
If the site that appears in the Site box is not the appropriate site, contact a supervisor and find out whether the IP address is incorrect or whether to move the Server object to the site indicated by the subnet. Procedure: Verify Communication with Other Domain ControllersThis test verifies that domain controllers can be located. Procedure Requirements | • | Credentials: Domain users | | • | Tool: Netdiag.exe |
Procedure Steps To verify communication with other domain controllers Note: For a more detailed response from this command, you can use the verbose option. Add /v to the end of the command to see the detailed response. | • | At a command prompt, type netdiag /test:dsgetdc and press ENTER. |
If domain controllers are successfully located, the last line of the response is DC discovery test..: Passed. The verbose option lists the specific domain controllers that are located. If the test fails, do not attempt any additional steps until you determine and fix the problem that prevents communication with other domain controllers. Procedure: Verify the Availability of the Operations MastersThis test verifies that the operations masters can be located and that they are online and responding. Procedure Requirements | • | Credentials: Domain users | | • | Tool: Dcdiag.exe |
Procedure Steps To verify the existence of the operations masters Note: You can use these tests prior to installing Active Directory as well as afterward. To perform the test prior to installing Active Directory, you must use the /s option to indicate the name of a domain controller to use for the test. You do not need the /s option to perform the test after installing Active Directory. The test automatically runs on the local domain controller where you are performing the tests. The commands listed in this procedure show the /s option. If you are performing this test after installing Active Directory, omit the /s option. For a more detailed response from this command, you can use the verbose option by adding /v to the end of the command to see the detailed response. 1. | To ensure that the operations masters can be located, at a command prompt, type: dcdiag /s: domaincontroller /test:knowsofroleholders /verbose where domaincontroller is the name of a domain controller in the domain in which you want to add the new domain controller. The verbose option provides a detailed list of the operations masters that were tested. Near the bottom of the screen, a message confirms that the test succeeded. If you use the verbose option, look carefully at the bottom part of the displayed output. The test confirmation message appears immediately after the list of operations masters. Press ENTER. | 2. | To test to ensure the operations masters are functioning properly and are available on the network, at a command prompt, type: dcdiag /s: domaincontroller /test:fsmocheck where domaincontroller is the name of a domain controller in the domain in which you want to add the new domain controller. The verbose option provides a detailed list of the operations masters that were tested. Near the bottom of your screen, a message confirms that the test succeeded. Press ENTER. |
If these tests fail, do not attempt any additional steps until you determine and fix the problem that prevents locating operations masters and verifying that they are functioning properly. Note: If any of the verification tests fail, do not continue until you determine and fix the problems. If these tests fail, the installation is also likely to fail. Procedure: Determine Whether a Server Object has Child ObjectsWhen a domain controller is properly installed, its Server object has a Child NTDS-Settings object. Other applications that are running on domain controllers can also publish Child objects. After installing Active Directory on a domain controller, verify that the Server object has a Child NTDS Settings object. Prior to deleting a Server object from the Servers container for a site, verify that the Server object has no Child objects. Procedure Requirements | • | Credentials: Domain users | | • | Tool: Active Directory Sites and Services (Administrative Tools) |
Procedure Steps To determine whether a Server object has Child objects |