From 802b23f9809d97387553178d2c2e7c5f724f1405 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Thu, 17 Nov 2022 18:49:19 -0500 Subject: [PATCH] VAMT code blocks standardization --- ...g-active-directory-based-activation-client.md | 6 +++++- ...activate-using-key-management-service-vamt.md | 12 ++++++++++-- .../activate-windows-10-clients-vamt.md | 10 +++++++++- ...sent-to-microsoft-during-activation-client.md | 10 +++++++++- .../configure-client-computers-vamt.md | 2 +- .../monitor-activation-client.md | 10 +++++++++- .../plan-for-volume-activation-client.md | 10 +++++++++- ...e-volume-activation-management-tool-client.md | 10 +++++++++- .../use-vamt-in-windows-powershell.md | 16 ++++++++-------- .../volume-activation/vamt-known-issues.md | 4 ++-- .../volume-activation-windows-10.md | 10 +++++++++- 11 files changed, 80 insertions(+), 20 deletions(-) diff --git a/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md b/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md index c19e08bdbc..3892da1105 100644 --- a/windows/deployment/volume-activation/activate-using-active-directory-based-activation-client.md +++ b/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? diff --git a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md b/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md index 0d3d2d93aa..2475495915 100644 --- a/windows/deployment/volume-activation/activate-using-key-management-service-vamt.md +++ b/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? @@ -61,7 +69,7 @@ Installing a KMS host key on a computer running Windows Server allows you to act This scenario is commonly used in larger organizations that do not 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 diff --git a/windows/deployment/volume-activation/activate-windows-10-clients-vamt.md b/windows/deployment/volume-activation/activate-windows-10-clients-vamt.md index 3becdf4dae..9be66de526 100644 --- a/windows/deployment/volume-activation/activate-windows-10-clients-vamt.md +++ b/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? diff --git a/windows/deployment/volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md b/windows/deployment/volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md index 07a8a62eaf..bb61a1db81 100644 --- a/windows/deployment/volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md +++ b/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?** diff --git a/windows/deployment/volume-activation/configure-client-computers-vamt.md b/windows/deployment/volume-activation/configure-client-computers-vamt.md index 392c89d4bf..382a9b53d3 100644 --- a/windows/deployment/volume-activation/configure-client-computers-vamt.md +++ b/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. diff --git a/windows/deployment/volume-activation/monitor-activation-client.md b/windows/deployment/volume-activation/monitor-activation-client.md index 0f48de80b8..d811b9bb87 100644 --- a/windows/deployment/volume-activation/monitor-activation-client.md +++ b/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? diff --git a/windows/deployment/volume-activation/plan-for-volume-activation-client.md b/windows/deployment/volume-activation/plan-for-volume-activation-client.md index e9969efbf8..43a1c717d5 100644 --- a/windows/deployment/volume-activation/plan-for-volume-activation-client.md +++ b/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? diff --git a/windows/deployment/volume-activation/use-the-volume-activation-management-tool-client.md b/windows/deployment/volume-activation/use-the-volume-activation-management-tool-client.md index e742b9f498..b733a5046e 100644 --- a/windows/deployment/volume-activation/use-the-volume-activation-management-tool-client.md +++ b/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? diff --git a/windows/deployment/volume-activation/use-vamt-in-windows-powershell.md b/windows/deployment/volume-activation/use-vamt-in-windows-powershell.md index 35886bbb64..71e97c1a03 100644 --- a/windows/deployment/volume-activation/use-vamt-in-windows-powershell.md +++ b/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 -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 ``` For example, enter: - ``` powershell + ```powershell get-help get-VamtProduct ``` 2. To see examples using a cmdlet, enter: - ``` powershell + ```powershell get-help -examples ``` For example, enter: - ``` powershell + ```powershell get-help get-VamtProduct -examples ``` diff --git a/windows/deployment/volume-activation/vamt-known-issues.md b/windows/deployment/volume-activation/vamt-known-issues.md index 948e4f2def..0507f060c7 100644 --- a/windows/deployment/volume-activation/vamt-known-issues.md +++ b/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 ``` diff --git a/windows/deployment/volume-activation/volume-activation-windows-10.md b/windows/deployment/volume-activation/volume-activation-windows-10.md index a56f8ed301..3cc524e10f 100644 --- a/windows/deployment/volume-activation/volume-activation-windows-10.md +++ b/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?