changed files by pdets auto publish service, publishid[89f9c703-b4b9-4918-b59d-6d131898f9aa] and do [publish].

Author: wwlpublish

learn-pr/wwl-azure/troubleshoot-active-directory/includes/3-recover-active-directory-domain-services-database.md

@@ -9,7 +9,7 @@ The AD DS database is stored as a file named Ntds.dit. When you install and conf
 
 Within the Ntds.dit file are all the partitions that the domain controller hosts. In the NTDS folder are other files that support the AD DS database. The Edb*.log files are the transaction logs for AD DS. When a change occurs in the directory:
 
-1. It is first written to the log file.
+1. It's first written to the log file.
 
 1. The change is committed to the directory as a transaction.
 
@@ -22,7 +22,7 @@ The following table describes the different file-level components of the AD DS d
 | Ntds.dit| Main AD DS database file. Contains Active Directory partitions and objects.|
 | Edb*.log| Transaction logs. Under normal operations, new transactions in the transaction log overwrite old transactions. However, if many transactions occur within a short period, AD DS creates additional transaction log files. Therefore, if you look in the NTDS folder of a particularly busy domain controller, you might see several Edb*.log files.|
 | Edb.chk| Database checkpoint file. The Edb.chk file acts like a bookmark in the log files. Edb.chk marks the location before which transactions have been successfully committed to the database, and after which transactions remain to be committed.|
-| Edbres00001.jrs, Edbres00002.jrs| Reserve transaction log files. If a disk drive runs out of space, AD DS cannot write to the logs. So, AD DS maintains two extra log files, Edbres00001.jrs and Edbres00002.jrs. When a disk runs out of space for normal transaction logs, AD DS recruits the space used by these two files to write the transactions that are in a queue currently. After that, it safely shuts down Active Directory services, and dismounts the database.|
+| Edbres00001.jrs, Edbres00002.jrs| Reserve transaction log files. If a disk drive runs out of space, AD DS can't write to the logs. So, AD DS maintains two extra log files, Edbres00001.jrs and Edbres00002.jrs. When a disk runs out of space for normal transaction logs, AD DS recruits the space used by these two files to write the transactions that are in a queue currently. After that, it safely shuts down Active Directory services, and dismounts the database.|
 
 ## Manage the AD DS database with NtdsUtil
 
@@ -57,25 +57,25 @@ You can use the following methods to restart AD DS:
 - Windows PowerShell
 
 > [!TIP]
-> Other services running on the server that do not depend on AD DS to function, such as Dynamic Host Configuration Protocol (DHCP), remain available to respond to client requests while AD DS is stopped. 
+> Other services running on the server that don't depend on AD DS to function, such as Dynamic Host Configuration Protocol (DHCP), remain available to respond to client requests while AD DS is stopped. 
 
-Restartable AD DS requires minor changes to the existing Microsoft Management Console (MMC) snap-ins. By using the snap-in, an administrator can stop and restart AD DS more easily, as they would any other service that is running locally on the server. Although stopping AD DS is similar to signing in in DSRM, restartable AD DS provides a unique state, known as AD DS Stopped.
+Restartable AD DS requires minor changes to the existing Microsoft Management Console (MMC) snap-ins. By using the snap-in, an administrator can stop and restart AD DS more easily, as they would any other service that is running locally on the server. Although stopping AD DS is similar to signing in DSRM, restartable AD DS provides a unique state, known as AD DS Stopped.
 
 ### What are the domain controller states?
 
 The three possible states for a domain controller that is running Windows Server are as follows:
 
-- AD DS Started. In this state, AD DS is started. The domain controller can perform AD DS–related tasks normally.****
+- AD DS Started. In this state, AD DS is started. The domain controller can perform AD DS–related tasks normally.
 
-- AD DS Stopped. In this state, AD DS is stopped. The domain controller has some characteristics of both a domain controller in DSRM and a domain-joined member server. ****
+- AD DS Stopped. In this state, AD DS is stopped. The domain controller has some characteristics of both a domain controller in DSRM and a domain-joined member server.
 
 - DSRM. In this state, the AD DS database (Ntds.dit) on the local domain controller is offline. Another domain controller can be contacted for sign-in, if one is available. If no other domain controller can be contacted, you can do one of the following, by default:
 
   - Sign in to the domain controller locally in DSRM by using the DSRM password.
 
   - Restart the domain controller to sign in with a domain account.
 
-As with a member server, the domain controller in the Stopped state is still joined to the domain. Because the domain controller is still joined to the domain, Group Policy and other settings still apply to the computer. However, a domain controller should not remain in the AD DS Stopped state for an extended period because in this state, it cannot service sign-in requests or replicate with other domain controllers.
+As with a member server, the domain controller in the Stopped state is still joined to the domain. Because the domain controller is still joined to the domain, Group Policy and other settings still apply to the computer. However, a domain controller shouldn't remain in the AD DS Stopped state for an extended period because in this state, it can't service sign-in requests or replicate with other domain controllers.
 
 ## Manage AD DS snapshots
 
@@ -97,11 +97,11 @@ After completing the restoration, you must restart the server. The domain contro
 
 In a normal restoration, you restore a backup of AD DS as of a known good date. Essentially, you roll the domain controller back in time. When AD DS restarts on the domain controller, the domain controller contacts its replication partners and requests all subsequent updates. In other words, the domain controller catches up with the rest of the domain by using standard replication mechanisms.
 
-Normal restoration is useful when the directory on a domain controller has been damaged or corrupted, but the problem has not spread to other domain controllers. However, for certain situations a normal restoration is not sufficient. For example, normal restoration will not work where damage has replicated, such as when you delete one or more objects, and that deletion has replicated. If you restore a known good version of AD DS and restart the domain controller, the deletion—which happened after the backup—simply replicates back to the domain controller.
+Normal restoration is useful when the directory on a domain controller has been damaged or corrupted, but the problem has not spread to other domain controllers. However, for certain situations a normal restoration isn't sufficient. For example, normal restoration won't work where damage has replicated, such as when you delete one or more objects, and that deletion has replicated. If you restore a known good version of AD DS and restart the domain controller, the deletion—which happened after the backup—simply replicates back to the domain controller.
 
 ### Perform authoritative restore
 
-An authoritative restore is necessary when you have restored a known good copy of AD DS and it contains objects that must override existing objects in the AD DS database. In an authoritative restore, you restore the known good version of AD DS just as you do in a normal restore. However, before you restart the domain controller, you mark the accidentally deleted or previously corrupted objects that you wish to retain as authoritative, so that they will replicate from the restored domain controller to its replication partners. When you mark objects as authoritative, Windows increments the version number of all object attributes to be so high that the version is virtually guaranteed to be higher than the version number on all other domain controllers.
+An authoritative restore is necessary when you have restored a known good copy of AD DS and it contains objects that must override existing objects in the AD DS database. In an authoritative restore, you restore the known good version of AD DS just as you do in a normal restore. However, before you restart the domain controller, you mark the accidentally deleted or previously corrupted objects that you wish to retain as authoritative, so that they'll replicate from the restored domain controller to its replication partners. When you mark objects as authoritative, Windows increments the version number of all object attributes to be so high that the version is virtually guaranteed to be higher than the version number on all other domain controllers.
 
 When the restored domain controller restarts, it replicates from its replication partners all the changes made to the directory. It also notifies its partners that it has changes, and the version numbers of the changes ensure that partners take the changes and replicate them throughout the directory service.
 
@@ -114,7 +114,7 @@ To perform an authoritative restore, complete the following procedure:
 
 1. Sign in with the Administrator account and the DSRM password.
 
-1. Restore the directory with Windows Server Backup. Before restarting the domain controller, you must first mark as authoritative the objects that you wish to persist after restart—that is, the deleted objects that you are trying to restore. To mark an object as authoritative, at the command prompt, run the following commands:
+1. Restore the directory with Windows Server Backup. Before restarting the domain controller, you must first mark as authoritative the objects that you wish to persist after restart—that is, the deleted objects that you're trying to restore. To mark an object as authoritative, at the command prompt, run the following commands:
 
     - NtdsUtil.exe
 

learn-pr/wwl-azure/troubleshoot-active-directory/includes/4-recover-sysvol.md

@@ -6,7 +6,8 @@ Group Policy settings are presented as Group Policy Objects (GPOs) in AD DS user
 | Group Policy Template| The Group Policy template stores the settings, and is a collection of files stored in the SYSVOL of each domain controller in the `%SystemRoot%\SYSVOL\Domain\Policies\GPOGUID` path, where GPOGUID is the GUID of the Group Policy container. When you make changes to the settings of a GPO, the changes are saved to the Group Policy template of the domain controller from which the GPO was opened.|
 
 > [!NOTE]
-> By default, this is the domain controller that holds the primary domain controller (PDC) emulator operations master role. 
+> By default, this is the domain controller that holds the primary domain controller (PDC) emulator operations master role. 
+
 ## What is Group Policy replication?
 
 Group Policy containers and Group Policy templates are both replicated between all domain controllers in a single domain in AD DS. But these two elements use different replication mechanisms:
@@ -30,7 +31,8 @@ There are a number of ways to perform an authoritative restore of SYSVOL. After
 - Perform a system state restore using `wbadmin –authsysvol`
 
 > [!TIP]
-> If you have the option to restore a system state backup (that is, you are restoring AD DS to the same hardware and operating system instance) then using `wbadmin –authsysvol` is simpler. 
+> If you have the option to restore a system state backup (that is, you are restoring AD DS to the same hardware and operating system instance) then using `wbadmin –authsysvol` is simpler. 
+
 But if you need to perform a bare metal restore, then you need to edit the `msDFSR-Options` attribute.
 
 ### Perform an authoritative synchronization of DFSR-replicated SYSVOL
@@ -43,9 +45,9 @@ Use the following procedure to perform an authoritative synchronization of SYSVO
 
 1. Enable both of the following from the **View** menu:
 
-  - Advanced Features
+    - Advanced Features
 
-  - User, Contacts, Groups, and Computers as containers
+    - User, Contacts, Groups, and Computers as containers
 
 1. In your domain, expand **Domain Controllers**, expand the specific domain controller you restored, expand **DFSR-LocalSettings**, and then select **Domain System Volume**.
 

learn-pr/wwl-azure/troubleshoot-active-directory/includes/5-troubleshoot-active-directory-domain-services-replication.md

@@ -116,7 +116,7 @@ The five operations master roles have the following distribution:
 
 - Each AD DS domain has one relative ID (RID) master, one infrastructure master, and one primary domain controller (PDC) emulator.
 
-The operations master perform the following functions:
+The operations master performs the following functions:
 
 - Domain naming master. This is the domain controller that you must contact when you add or remove a domain or make domain name changes. If the domain naming master is unavailable, you won't be able to add domains to the forest.