mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Cleaning up after conversion
This commit is contained in:
@ -10,8 +10,6 @@ author: CFaw
|
||||
---
|
||||
|
||||
# Activate using Active Directory-based activation
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -44,9 +42,9 @@ The process proceeds as follows:
|
||||
|
||||
3. Client computers are activated by receiving the activation object from a domain controller during startup.
|
||||
|
||||

|
||||

|
||||
|
||||
**Figure 10**. The Active Directory-based activation flow
|
||||
**Figure 10**. The Active Directory-based activation flow
|
||||
|
||||
For environments in which all computers are running Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, or Windows Server 2012 R2, and they are joined to a domain, Active Directory-based activation is the best option for activating all client computers and servers, and you may be able to remove any KMS hosts from your environment.
|
||||
|
||||
@ -57,14 +55,10 @@ Clients that are activated with Active Directory-based activation will maintain
|
||||
When a reactivation event occurs, the client queries AD DS for the activation object. Client computers examine the activation object and compare it to the local edition as defined by the GVLK. If the object and GVLK match, reactivation occurs. If the AD DS object cannot be retrieved, client computers use KMS activation. If the computer is removed from the domain, when the computer or the Software Protection service is restarted, the operating system will change the status from activated to not activated, and the computer will try to activate with KMS.
|
||||
|
||||
## Step-by-step configuration: Active Directory-based activation
|
||||
|
||||
|
||||
**Note**
|
||||
You must be a member of the local Administrators group on all computers mentioned in these steps. You also need to be a member of the Enterprise Administrators group, because setting up Active Directory-based activation changes forest-wide settings.
|
||||
|
||||
|
||||
|
||||
To configure Active Directory-based activation on Windows Server 2012 R2, complete the following steps:
|
||||
**To configure Active Directory-based activation on Windows Server 2012 R2, complete the following steps:**
|
||||
|
||||
1. Use an account with Domain Administrator and Enterprise Administrator credentials to sign in to a domain controller.
|
||||
|
||||
@ -72,39 +66,37 @@ To configure Active Directory-based activation on Windows Server 2012 R2, comp
|
||||
|
||||
3. Add the Volume Activation Services role, as shown in Figure 11.
|
||||
|
||||

|
||||

|
||||
|
||||
**Figure 11**. Adding the Volume Activation Services role
|
||||
|
||||
4. Click the link to launch the Volume Activation Tools (Figure 12).
|
||||
|
||||

|
||||

|
||||
|
||||
**Figure 12**. Launching the Volume Activation Tools
|
||||
|
||||
5. Select the **Active Directory-Based Activation** option (Figure 13).
|
||||
|
||||

|
||||

|
||||
|
||||
**Figure 13**. Selecting Active Directory-Based Activation
|
||||
|
||||
6. Enter your KMS host key and (optionally) a display name (Figure 14).
|
||||
|
||||

|
||||

|
||||
|
||||
**Figure 14**. Entering your KMS host key
|
||||
|
||||
7. Activate your KMS host key by phone or online (Figure 15).
|
||||
|
||||

|
||||

|
||||
|
||||
**Figure 15**. Choosing how to activate your product
|
||||
|
||||
8. After activating the key, click **Commit**, and then click **Close**.
|
||||
|
||||
## Verifying the configuration of Active Directory-based activation
|
||||
|
||||
|
||||
To verify your Active Directory-based activation configuration, complete the following steps:
|
||||
|
||||
1. After you configure Active Directory-based activation, start a computer that is running an edition of Windows that is configured by volume licensing.
|
||||
@ -119,21 +111,8 @@ To verify your Active Directory-based activation configuration, complete the fol
|
||||
|
||||
6. Scroll down to the **Windows activation** section, and verify that this client has been activated.
|
||||
|
||||
**Note**
|
||||
If you are using both KMS and Active Directory-based activation, it may be difficult to see whether a client has been activated by KMS or by Active Directory-based activation. Consider disabling KMS during the test, or make sure that you are using a client computer that has not already been activated by KMS. The **slmrg.vbs /dlv** command also indicates whether KMS has been used.
|
||||
|
||||
|
||||
|
||||
**Note**<br>
|
||||
If you are using both KMS and Active Directory-based activation, it may be difficult to see whether a client has been activated by KMS or by Active Directory-based activation. Consider disabling KMS during the test, or make sure that you are using a client computer that has not already been activated by KMS. The **slmrg.vbs /dlv** command also indicates whether KMS has been used.
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
Reference in New Issue
Block a user