From 5b74488e59654d50bcba7abf8f7cf6357bf7a4d9 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Fri, 28 Oct 2016 10:34:09 -0700 Subject: [PATCH] typo slmgr --- .../activate-using-active-directory-based-activation-client.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deploy/activate-using-active-directory-based-activation-client.md b/windows/deploy/activate-using-active-directory-based-activation-client.md index a3dce6ef96..82c95ff35b 100644 --- a/windows/deploy/activate-using-active-directory-based-activation-client.md +++ b/windows/deploy/activate-using-active-directory-based-activation-client.md @@ -91,7 +91,7 @@ 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. + 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 **slmgr.vbs /dlv** command also indicates whether KMS has been used. ## See also - [Volume Activation for Windows 10](volume-activation-windows-10.md)