Merge pull request #7533 from frankroj/fr-vamt-code-blocks-update

VAMT code blocks standardization

windows/deployment/volume-activation/activate-forest-by-proxy-vamt.md

@@ -33,18 +33,31 @@ Before performing proxy activation, ensure that the network and the VAMT install
 ### To perform an Active Directory forest proxy activation
 
 1. Open VAMT.
+
 2. In the left-side pane, select the **Active Directory-Based Activation** node.
+
 3. In the right-side **Actions** pane, select **Proxy activate forest** to open the **Install Product Key** dialog box.
+
 4. In the **Install Product Key** dialog box, select the KMS Host key (CSVLK) that you want to activate.
+
 5. If you want to rename the ADBA object, enter a new Active Directory-Based Activation Object name. If you want to rename the ADBA object, you must do it now. After you select **Install Key**, the name can't be changed.
+
 6. Enter the name of the file where you want to save the offline installation ID, or browse to the file location and then select **Open**. If you're activating an AD forest in an isolated workgroup, save the `.cilx` file to a removable media device.
+
 7. Select **Install Key**. VAMT displays the **Activating Active Directory** dialog box until it completes the requested action. The activated object and the date that it was created appear in the **Active Directory-Based Activation** node in the center pane.
+
 8. Insert the removable media into the VAMT host that has Internet access. Make sure that you are on the root node, and that the **Volume Activation Management Tool** view is displayed in the center pane.
+
 9. In the right-side **Actions** pane, select **Acquire confirmation IDs for CILX** to open the **Acquire confirmation IDs for file** dialog box.
+
 10. In the **Acquire confirmation IDs for file** dialog box, browse to where the `.cilx` file you exported from the isolated workgroup host computer is located. Select the file, and then select **Open**. VAMT displays an **Acquiring Confirmation IDs** message while it contacts Microsoft and acquires the CIDs.
+
 11. When the CID collection process is complete, VAMT displays a **Volume Activation Management Tool** message that shows how many confirmation IDs were successfully acquired, and the name of the file to which the IDs were saved. Select **OK** to close the message.
+
 12. Remove the storage device that contains the `.cilx` file from the Internet-connected VAMT host computer and insert it into the VAMT host computer in the isolated workgroup.
+
 13. Open VAMT and then select the **Active Directory-Based Activation** node in the left-side pane.
+
 14. In the right-side **Actions** pane, select **Apply confirmation ID to Active Directory domain**, browse to the `.cilx` file and then select **Open**.
 
 VAMT displays the **Activating Active Directory** dialog box until it completes the requested action. The activated object and the date that it was created appear in the **Active Directory-Based Activation** node in the center pane.

windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md

@@ -14,7 +14,11 @@ ms.collection: highpri
 
 # Activate using Active Directory-based activation
 
-(*Applies to: Windows, Windows Server, Office*)
+*Applies to:*
+
+- Windows
+- Windows Server
+- Office
 
 > [!TIP]
 > Are you looking for information on retail activation?

windows/deployment/volume-activation/activate-using-key-management-service-vamt.md

@@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
 
 # Activate using Key Management Service
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 > [!TIP]
 > Are you looking for information on retail activation?
@@ -39,14 +47,20 @@ To enable KMS functionality, a KMS key is installed on a KMS host; then, the hos
 
 ### Configure KMS in Windows 10
 
-To activate, use the slmgr.vbs command. Open an elevated command prompt and run one of the following commands:
+To activate, use the `slmgr.vbs` command. Open an elevated command prompt and run one of the following commands:
+
+- To install the KMS key, run the command `slmgr.vbs /ipk <KmsKey>`.
+
+- To activate online, run the command `slmgr.vbs /ato`.
 
-- To install the KMS key, type `slmgr.vbs /ipk <KmsKey>`.
-- To activate online, type `slmgr.vbs /ato`.
 - To activate by telephone, follow these steps:
+
   1. Run `slmgr.vbs /dti` and confirm the installation ID.
+
   2. Call [Microsoft Licensing Activation Centers worldwide telephone numbers](https://www.microsoft.com/licensing/existing-customer/activation-centers) and follow the voice prompts to enter the installation ID that you obtained in step 1 on your telephone.
+
   3. Follow the voice prompts and write down the responded 48-digit confirmation ID for OS activation.
+
   4. Run `slmgr.vbs /atp \<confirmation ID\>`.
 
 For more information, see the information for Windows 7 in [Deploy KMS Activation](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn502531(v=ws.11)).
@@ -58,42 +72,43 @@ Installing a KMS host key on a computer running Windows Server allows you to act
 > [!NOTE]
 > You cannot install a client KMS key into the KMS in Windows Server.
 
-This scenario is commonly used in larger organizations that do not find the overhead of using a server a burden.
+This scenario is commonly used in larger organizations that don't find the overhead of using a server a burden.
 
 > [!NOTE]
-> If you receive error 0xC004F015 when trying to activate Windows 10 Enterprise, see [KB 3086418](/troubleshoot/windows-server/deployment/error-0xc004f015-activate-windows-10).
+> If you receive error 0xC004F015 when trying to activate Windows 10 Enterprise, see [Error 0xC004F015 when you activate Windows 10 Enterprise on a Windows Server 2012 R2 KMS host](/troubleshoot/windows-server/deployment/error-0xc004f015-activate-windows-10).
 
 ### Configure KMS in Windows Server 2012 R2
 
 1. Sign in to a computer running Windows Server 2012 R2 with an account that has local administrative credentials.
+
 2. Launch Server Manager.
+
 3. Add the Volume Activation Services role, as shown in Figure 4.
 
    ![Adding the Volume Activation Services role in Server Manager.](../images/volumeactivationforwindows81-04.jpg)
 
    **Figure 4**. Adding the Volume Activation Services role in Server Manager
 
-4. When the role installation is complete, click the link to launch the Volume Activation Tools (Figure 5).
+4. When the role installation is complete, select the link to launch the Volume Activation Tools (Figure 5).
 
    ![Launching the Volume Activation Tools.](../images/volumeactivationforwindows81-05.jpg)
 
    **Figure 5**. Launching the Volume Activation Tools
 
-5. Select the **Key Management Service (KMS)** option, and specify the computer that will act as the KMS host (Figure 6).
-      This can be the same computer on which you installed the role or another computer. For example, it can be a client computer running Windows 10.
+5. Select the **Key Management Service (KMS)** option, and specify the computer that will act as the KMS host (Figure 6). This computer can be the same computer on which you installed the role or another computer. For example, it can be a client computer running Windows 10.
 
    ![Configuring the computer as a KMS host.](../images/volumeactivationforwindows81-06.jpg)
 
    **Figure 6**. Configuring the computer as a KMS host
 
-6. Install your KMS host key by typing it in the text box, and then click **Commit** (Figure 7).
+6. Install your KMS host key by typing it in the text box, and then select **Commit** (Figure 7).
 
    ![Installing your KMS host key.](../images/volumeactivationforwindows81-07.jpg)
 
    **Figure 7**. Installing your KMS host key
 
-7. If asked to confirm replacement of an existing key, click **Yes**.
-8. After the product key is installed, you must activate it. Click **Next** (Figure 8).
+7. If asked to confirm replacement of an existing key, select **Yes**.
+8. After the product key is installed, you must activate it. Select **Next** (Figure 8).
 
    ![Activating the software.](../images/volumeactivationforwindows81-08.jpg)
 
@@ -109,7 +124,7 @@ Now that the KMS host is configured, it will begin to listen for activation requ
 
 ## Verifying the configuration of Key Management Service
 
-You can verify KMS volume activation from the KMS host server or from the client computer. KMS volume activation requires a minimum threshold of 25 computers before activation requests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host, but unless the activation threshold is reached, the verification will take the form of an error message rather than a confirmation message.
+KMS volume activation can be verified from the KMS host server or from the client computer. KMS volume activation requires a minimum threshold of 25 computers before activation requests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host, but unless the activation threshold is reached, the verification will take the form of an error message rather than a confirmation message.
 
 > [!NOTE]
 > If you configured Active Directory-based activation before configuring KMS activation, you must use a client computer that will not first try to activate itself by using Active Directory-based activation. You could use a workgroup computer that is not joined to a domain or a computer running Windows 7 or Windows Server 2008 R2.
@@ -117,18 +132,20 @@ You can verify KMS volume activation from the KMS host server or from the client
 To verify that KMS volume activation works, complete the following steps:
 
 1. On the KMS host, open the event log and confirm that DNS publishing is successful.
-2. On a client computer, open a Command Prompt window, type `Slmgr.vbs /ato`, and then press ENTER.
+
+2. On a client computer, open a Command Prompt window and run the command `Slmgr.vbs /ato`.
 
    The `/ato` command causes the operating system to attempt activation by using whichever key has been installed in the operating system. The response should show the license state and detailed Windows version information.
-3. On a client computer or the KMS host, open an elevated Command Prompt window, type `Slmgr.vbs /dlv`, and then press ENTER.
 
-   The `/dlv` command displays the detailed licensing information. The response should return an error that states that the KMS activation count is too low. This confirms that KMS is functioning correctly, even though the client has not been activated.
+3. On a client computer or the KMS host, open an elevated Command Prompt window and run the command `Slmgr.vbs /dlv`.
+
+   The `/dlv` command displays the detailed licensing information. The response should return an error that states that the KMS activation count is too low. This test confirms that KMS is functioning correctly, even though the client hasn't been activated.
 
 For more information about the use and syntax of slmgr.vbs, see [Slmgr.vbs Options](/windows-server/get-started/activation-slmgr-vbs-options).
 
 ## Key Management Service in earlier versions of Windows
 
-If you have already established a KMS infrastructure in your organization for an earlier version of Windows, you may want to continue using that infrastructure to activate computers running Windows 10 or Windows Server 2012 R2. Your existing KMS host must be running Windows 7 or later. To upgrade your KMS host, complete the following steps:
+If you've already established a KMS infrastructure in your organization for an earlier version of Windows, you may want to continue using that infrastructure to activate computers running Windows 10 or Windows Server 2012 R2. Your existing KMS host must be running Windows 7 or later. To upgrade your KMS host, complete the following steps:
 
 1. Download and install the correct update for your current KMS host operating system. Restart the computer as directed.
 2. Request a new KMS host key from the Volume Licensing Service Center.

windows/deployment/volume-activation/activate-windows-10-clients-vamt.md

@@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
 
 # Activate clients running Windows 10
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 > [!TIP]
 > Are you looking for information on retail activation?

windows/deployment/volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md

@@ -14,7 +14,15 @@ ms.topic: article
 
 # Appendix: Information sent to Microsoft during activation
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 **Looking for retail activation?**
 

windows/deployment/volume-activation/configure-client-computers-vamt.md

@@ -99,7 +99,7 @@ There are several options for organizations to configure the WMI firewall except
 
 - **Image.** Add the configurations to the master Windows image deployed to all clients.
 
-- **Group Policy.** If the clients are part of a domain, then all clients can be configured using Group Policy. The Group Policy setting for the WMI firewall exception is found in GPMC.MSC at: **Computer Configuration\\Windows Settings\\Security Settings\\Windows Firewall with Advanced Security\\Windows Firewall with Advanced Security\\Inbound Rules**.
+- **Group Policy.** If the clients are part of a domain, then all clients can be configured using Group Policy. The Group Policy setting for the WMI firewall exception is found in GPMC.MSC at: **Computer Configuration** > **Windows Settings** > **Security Settings** > **Windows Firewall with Advanced Security** > **Windows Firewall with Advanced Security** > **Inbound Rules**.
 
 - **Script.** Execute a script using Microsoft Configuration Manager or a third-party remote script execution facility.
 

windows/deployment/volume-activation/monitor-activation-client.md

@@ -14,7 +14,15 @@ ms.date: 11/07/2022
 
 # Monitor activation
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 > [!TIP]
 > Are you looking for information on retail activation?

windows/deployment/volume-activation/plan-for-volume-activation-client.md

@@ -14,7 +14,15 @@ ms.date: 11/07/2022
 
 # Plan for volume activation
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 > [!TIP]
 > Are you looking for information on retail activation?

windows/deployment/volume-activation/use-the-volume-activation-management-tool-client.md

@@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
 
 # Use the Volume Activation Management Tool
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 > [!TIP]
 > Are you looking for information on retail activation?

windows/deployment/volume-activation/use-vamt-in-windows-powershell.md

@@ -43,7 +43,7 @@ To open PowerShell with administrative credentials, select **Start** and enter `
 
 For all supported operating systems, you can use the VAMT PowerShell module included with the Windows ADK. By default, the module is installed with the Windows ADK in the VAMT folder. Change directories to the directory where VAMT is located. For example, if the Windows ADK is installed in the default location of `C:\Program Files(x86)\Windows Kits\10`, enter:
 
-  ``` powershell
+  ```powershell
   cd "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT 3.0"
   ```
 
@@ -51,7 +51,7 @@ For all supported operating systems, you can use the VAMT PowerShell module incl
 
 To import the VAMT PowerShell module, enter the following command at a PowerShell command prompt:
 
-  ``` powershell
+  ```powershell
   Import-Module .\VAMT.psd1
   ```
 
@@ -61,13 +61,13 @@ To import the VAMT PowerShell module, enter the following command at a PowerShel
 
 You can view all of the help sections for a VAMT PowerShell cmdlet, or you can view only the section that you're interested in. To view all of the Help content for a VAMT cmdlet, enter:
 
-``` powershell
+```powershell
 get-help <cmdlet name> -all
 ```
 
 For example, enter:
 
-``` powershell
+```powershell
 get-help get-VamtProduct -all
 ```
 
@@ -78,24 +78,24 @@ get-help get-VamtProduct -all
 
 1. To get the syntax to use with a cmdlet, enter the following command at a PowerShell command prompt:
 
-   ``` powershell
+   ```powershell
    get-help <cmdlet name>
    ```
 
    For example, enter:
 
-   ``` powershell
+   ```powershell
    get-help get-VamtProduct 
    ```
 
 2. To see examples using a cmdlet, enter:
 
-   ``` powershell
+   ```powershell
    get-help <cmdlet name> -examples
    ```
 
    For example, enter:
 
-   ``` powershell
+   ```powershell
    get-help get-VamtProduct -examples
    ```

windows/deployment/volume-activation/vamt-known-issues.md

@@ -46,13 +46,13 @@ On the KMS host computer, perform the following steps:
 
 3. To extract the contents of the update, run the following command:
 
-   ``` syntax
+   ```cmd
    expand c:\KB3058168\Windows8.1-KB3058168-x64.msu -f:* C:\KB3058168\
    ```
 
 4. To extract the contents of Windows8.1-KB3058168-x64.cab, run the following command:
 
-   ``` syntax
+   ```cmd
    expand c:\KB3058168\Windows8.1-KB3058168-x64.cab -f:pkeyconfig-csvlk.xrm-ms c:\KB3058168
    ```
 

windows/deployment/volume-activation/volume-activation-windows-10.md

@@ -14,7 +14,15 @@ ms.technology: itpro-fundamentals
 
 # Volume Activation for Windows 10
 
-(*Applies to: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2*)
+*Applies to:*
+
+- Windows 10
+- Windows 8.1
+- Windows 8
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2012
+- Windows Server 2008 R2
 
 > [!TIP]
 > Are you looking for volume licensing information?