mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-16 15:27:22 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into copilot-xplat-8348943
This commit is contained in:
Meghan Stewart
commit
9b94db7789
@ -106,7 +106,7 @@ Also, if your organization plans to use a management tool, you'll need to config
|
||||
|
||||
## Get apps and content
|
||||
|
||||
Once signed in to the Microsoft Store, you can browse and search for all products in the Store for Business and Education catalog. Some apps are free,and some apps charge a price. We're continuing to add more paid apps to the Store for Business and Education. Check back if you don't see the app that you're looking for. Currently, you can pay for apps with a credit card, and some items can be paid for with an invoice. We'll be adding more payment options over time.
|
||||
Once signed in to the Microsoft Store, you can browse and search for all products in the Store for Business and Education catalog. Some apps are free, and some apps charge a price. We're continuing to add more paid apps to the Store for Business and Education. Check back if you don't see the app that you're looking for. Currently, you can pay for apps with a credit card, and some items can be paid for with an invoice. We'll be adding more payment options over time.
|
||||
|
||||
**App types** - These app types are supported in the Store for Business and Education:
|
||||
|
||||
@ -244,7 +244,6 @@ Store for Business and Education is currently available in these markets.
|
||||
- Liechtenstein
|
||||
- Lithuania
|
||||
- Luxembourg
|
||||
- Macedonia
|
||||
- Madagascar
|
||||
- Malawi
|
||||
- Malaysia
|
||||
@ -268,6 +267,7 @@ Store for Business and Education is currently available in these markets.
|
||||
- New Zealand
|
||||
- Nicaragua
|
||||
- Nigeria
|
||||
- North Macedonia
|
||||
- Norway
|
||||
- Oman
|
||||
- Pakistan
|
||||
@ -310,7 +310,7 @@ Store for Business and Education is currently available in these markets.
|
||||
- Tonga
|
||||
- Trinidad and Tobago
|
||||
- Tunisia
|
||||
- Turkey
|
||||
- Türkiye
|
||||
- Turks and Caicos Islands
|
||||
- Uganda
|
||||
- United Arab Emirates
|
||||
@ -386,4 +386,4 @@ Developers in your organization, or ISVs can create content specific to your org
|
||||
|
||||
Once the app is in inventory, admins can choose how to distribute the app. ISVs creating apps through the dev center can make their apps available in Store for Business and Education. ISVs can opt-in their apps to make them available for offline licensing. Apps purchased in Store for Business and Education will work only on Windows 10.
|
||||
|
||||
For more information on line-of-business apps, see [Working with Line-of-Business apps](working-with-line-of-business-apps.md).
|
||||
For more information on line-of-business apps, see [Working with Line-of-Business apps](working-with-line-of-business-apps.md).
|
||||
|
||||
@ -31,7 +31,7 @@ Microsoft provides MDM security baselines that function like the Microsoft group
|
||||
|
||||
The MDM security baseline includes policies that cover the following areas:
|
||||
|
||||
- Microsoft inbox security technologies (not deprecated) such as BitLocker, Windows Defender SmartScreen, Exploit Guard, Microsoft Defender Antivirus, and Firewall
|
||||
- Microsoft inbox security technologies (not deprecated) such as **BitLocker, Windows Defender SmartScreen, Exploit Guard, Microsoft Defender Antivirus,** and **Firewall**
|
||||
- Restricting remote access to devices
|
||||
- Setting credential requirements for passwords and PINs
|
||||
- Restricting use of legacy technology
|
||||
@ -66,6 +66,6 @@ No. Only one MDM is allowed.
|
||||
|
||||
| Entry | Description |
|
||||
| --------------- | -------------------- |
|
||||
| What is dmwappushsvc? | It's a Windows service that ships in Windows operating system as a part of the windows management platform. It's used internally by the operating system as a queue for categorizing and processing all Wireless Application Protocol (WAP) messages, which include Windows management messages, and Service Indication/Service Loading (SI/SL). The service also initiates and orchestrates management sync sessions with the MDM server. |
|
||||
| What data is handled by dmwappushsvc? | It's a component handling the internal workings of the management platform and involved in processing messages that have been received by the device remotely for management. The messages in the queue are serviced by another component that is also part of the Windows management stack to process messages. The service also routes and authenticates WAP messages received by the device to internal OS components that process them further. This service doesn't send telemetry. |
|
||||
| How do I turn if off? | The service can be stopped from the "Services" console on the device (Start > Run > services.msc) and locating *Device Management Wireless Application Protocol (WAP) Push message Routing Service*. However, since this service is a component part of the OS and required for the proper functioning of the device, we strongly recommend not to disable the service. Disabling this service causes your management to fail. |
|
||||
| What is dmwappushsvc? | It's a Windows service that ships in the Windows operating system as a part of the Windows management platform. It's used internally by the operating system as a queue for categorizing and processing all Wireless Application Protocol (WAP) messages, which include Windows management messages, and Service Indication/Service Loading (SI/SL). The service also initiates and orchestrates management sync sessions with the MDM server. |
|
||||
| What data is handled by dmwappushsvc? | It's a component handling the internal workings of the management platform and is involved in processing messages that have been received by the device remotely for management. The messages in the queue are serviced by another component that is also part of the Windows management stack to process messages. The service also routes and authenticates WAP messages received by the device to internal OS components that process them further. This service doesn't send telemetry. |
|
||||
| How do I turn if off? | The service can be stopped from the "Services" console on the device (Start > Run > services.msc) and locating *Device Management Wireless Application Protocol (WAP) Push message Routing Service*. However, since this service is a component part of the OS and is required for the proper functioning of the device, we strongly recommend not to disable the service. Disabling this service causes your management to fail. |
|
||||
|
||||
@ -85,7 +85,7 @@ Use *Default* to specify a name that matches one of the search providers you ent
|
||||
Some countries/regions require specific, default search providers. The following table lists the applicable countries/regions and information for configuring the necessary search provider.
|
||||
|
||||
>[!NOTE]
|
||||
>For Russia + Commonwealth of Independent States (CIS), the independent states consist of Russia, Ukraine, Georgia, The Republic of Azerbaijan, Republic Of Belarus, The Republic of Kazakhstan, The Kyrgyz Republic, The Republic of Moldova, The Republic of Tajikistan, The Republic of Armenia, Turkmenistan, The Republic of Uzbekistan, and Turkey.
|
||||
>For Russia + Commonwealth of Independent States (CIS), the independent states consist of Russia, Ukraine, Georgia, The Republic of Azerbaijan, Republic Of Belarus, The Republic of Kazakhstan, The Kyrgyz Republic, The Republic of Moldova, The Republic of Tajikistan, The Republic of Armenia, Turkmenistan, The Republic of Uzbekistan, and Türkiye.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.technology: itpro-deploy
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier3
|
||||
ms.date: 11/28/2022
|
||||
ms.date: 10/13/2023
|
||||
---
|
||||
|
||||
# Prepare for deployment with MDT
|
||||
@ -135,7 +135,8 @@ To install WSUS on MDT01, enter the following at an elevated Windows PowerShell
|
||||
|
||||
```powershell
|
||||
Install-WindowsFeature -Name UpdateServices, UpdateServices-WidDB, UpdateServices-Services, UpdateServices-RSAT, UpdateServices-API, UpdateServices-UI
|
||||
"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall CONTENT_DIR=C:\WSUS
|
||||
cd "C:\Program Files\Update Services\Tools"
|
||||
.\wsusutil.exe postinstall CONTENT_DIR=C:\WSUS
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
@ -264,19 +265,19 @@ See the following example:
|
||||
|
||||
|
||||
|
||||
## Use CMTrace to read log files (optional)
|
||||
## Use Support Center OneTrace or CMTrace to read log files (optional)
|
||||
|
||||
The log files in MDT Lite Touch are formatted to be read by Configuration Manager Trace ([CMTrace](/mem/configmgr/core/support/cmtrace)).
|
||||
The log files in MDT Lite Touch are formatted to be read by [Support Center OneTrace](/mem/configmgr/core/support/support-center-onetrace) or [CMTrace](/mem/configmgr/core/support/cmtrace).
|
||||
|
||||
You can use Notepad (example below):
|
||||
Notepad can be used to read the log files (example below):
|
||||
|
||||
|
||||
|
||||
Alternatively, CMTrace formatting makes the logs much easier to read. See the same log file below, opened in CMTrace:
|
||||
However, Support Center OneTrace or CMTrace makes the logs much easier to read. See the same log file below, opened in CMTrace:
|
||||
|
||||
|
||||
|
||||
After installing the ConfigMgrTools.msi file, you can search for **cmtrace** and pin the tool to your taskbar for easy access.
|
||||
Both Support Center OneTrace and CMTrace are available as part of Microsoft Configuration Manager.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 90 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 67 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 60 KiB |
@ -8,155 +8,191 @@ author: frankroj
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/07/2022
|
||||
ms.date: 10/13/2023
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2022</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2019</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2016</a>
|
||||
---
|
||||
|
||||
# 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
|
||||
|
||||
> [!TIP]
|
||||
> Are you looking for information on retail activation?
|
||||
>
|
||||
> For information on retail activation, see the following articles:
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/)
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
|
||||
There are three possible scenarios for volume activation of Windows 10 or Windows Server 2012 R2 by using a Key Management Service (KMS) host:
|
||||
Volume activation can be performed via Key Management Service (KMS). KMS can be hosted either on a client version of Windows or on Windows Server.
|
||||
|
||||
- Host KMS on a computer running Windows 10
|
||||
- Host KMS on a computer running Windows Server 2012 R2
|
||||
- Host KMS on a computer running an earlier version of Windows
|
||||
## Key Management Service in a client version of Windows
|
||||
|
||||
Check out [Windows 10 Volume Activation Tips](/archive/blogs/askcore/windows-10-volume-activation-tips).
|
||||
Installing a KMS host key on a computer running a client version of Windows allows the following scenarios against this KMS host:
|
||||
|
||||
## Key Management Service in Windows 10
|
||||
- Activation of other computers running the same client version of Windows.
|
||||
- Activation of other computers running earlier client versions of Windows.
|
||||
|
||||
Installing a KMS host key on a computer running Windows 10 allows you to activate other computers running Windows 10 against this KMS host and earlier versions of the client operating system, such as Windows 8.1 or Windows 7.
|
||||
Clients locate the KMS server by using resource records in DNS, so some configuration of DNS is required. This scenario can be beneficial if the organization uses volume activation for clients and MAK-based activation for a smaller number of servers.
|
||||
|
||||
Clients locate the KMS server by using resource records in DNS, so some configuration of DNS may be required. This scenario can be beneficial if your organization uses volume activation for clients and MAK-based activation for a smaller number of servers.
|
||||
To enable KMS functionality, a KMS key is installed on a KMS host; then, the host is activated over the Internet or by phone using Microsoft activation services.
|
||||
To enable KMS functionality, a KMS key is installed on a KMS host. The host is then activated over the Internet or by phone using Microsoft activation services.
|
||||
|
||||
### Configure KMS in Windows 10
|
||||
### Configure KMS in a client version of Windows
|
||||
|
||||
To activate, use the `slmgr.vbs` command. Open an elevated command prompt and run one of the following commands:
|
||||
KMS can be activated on client versions of Windows by using the `slmgr.vbs`. To activate KMS on a client version of Windows, follow these steps:
|
||||
|
||||
- To install the KMS key, run the command `slmgr.vbs /ipk <KmsKey>`.
|
||||
1. Open an elevated Command Prompt window.
|
||||
|
||||
- To activate online, run the command `slmgr.vbs /ato`.
|
||||
1. In the elevated Command Prompt window, run the following command to install the KMS key:
|
||||
|
||||
- To activate by telephone, follow these steps:
|
||||
```cmd
|
||||
cscript.exe slmgr.vbs /ipk <KMS_Key>
|
||||
```
|
||||
|
||||
1. Run `slmgr.vbs /dti` and confirm the installation ID.
|
||||
1. Once the KMS key has been installed, it needs to be activated using one of the following methods:
|
||||
|
||||
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.
|
||||
- To activate online, in the elevated Command Prompt window, run the following command:
|
||||
|
||||
3. Follow the voice prompts and write down the responded 48-digit confirmation ID for OS activation.
|
||||
```cmd
|
||||
cscript.exe slmgr.vbs /ato
|
||||
```
|
||||
|
||||
4. Run `slmgr.vbs /atp \<confirmation ID\>`.
|
||||
- To activate by telephone, follow these steps:
|
||||
|
||||
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)).
|
||||
1. In the elevated Command Prompt window, run the following command:
|
||||
|
||||
## Key Management Service in Windows Server 2012 R2
|
||||
```cmd
|
||||
cscript.exe slmgr.vbs /dti
|
||||
```
|
||||
|
||||
Installing a KMS host key on a computer running Windows Server allows you to activate computers running Windows Server 2012 R2, Windows Server 2008 R2, Windows Server 2008, Windows 10, Windows 8.1, Windows 7, and Windows Vista.
|
||||
This command should display the installation ID.
|
||||
|
||||
> [!NOTE]
|
||||
> You cannot install a client KMS key into the KMS in Windows Server.
|
||||
1. Call the [Microsoft Volume License Key assisted support telephone numbers](https://www.microsoft.com/licensing/existing-customer/activation-centers). Follow the voice prompts and when prompted, enter the installation ID obtained in the previous step.
|
||||
|
||||
This scenario is commonly used in larger organizations that don't find the overhead of using a server a burden.
|
||||
1. Continue following the voice prompts. When prompted, write down the 48-digit confirmation ID for OS activation given by the prompts.
|
||||
|
||||
> [!NOTE]
|
||||
> 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).
|
||||
1. In the elevated Command Prompt window, run the following command:
|
||||
|
||||
### Configure KMS in Windows Server 2012 R2
|
||||
```cmd
|
||||
cscript.exe slmgr.vbs /atp <confirmation_ID_from_previous_step>
|
||||
```
|
||||
|
||||
1. Sign in to a computer running Windows Server 2012 R2 with an account that has local administrative credentials.
|
||||
## Key Management Service in Windows Server
|
||||
|
||||
2. Launch Server Manager.
|
||||
Installing a KMS host key on a computer running Windows Server allows you to activate computers running the same or earlier versions of Windows Server. Additionally, it also allows activation of client versions of Windows.
|
||||
|
||||
3. Add the Volume Activation Services role, as shown in Figure 4.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> You can't install a client KMS key into the KMS in Windows Server.
|
||||
|
||||
|
||||
### Configure KMS in Windows Server
|
||||
|
||||
**Figure 4**. Adding the Volume Activation Services role in Server Manager
|
||||
1. Sign in to a Windows Server server with an account that has local administrative credentials.
|
||||
|
||||
4. When the role installation is complete, select the link to launch the Volume Activation Tools (Figure 5).
|
||||
1. Open **Server Manager**.
|
||||
|
||||
|
||||
1. Under the **Manage** menu in **Server Manager**, select **Add Roles and Features**. The **Add Roles and Features Wizard** window opens.
|
||||
|
||||
**Figure 5**. Launching the Volume Activation Tools
|
||||
1. In the **Add Roles and Features Wizard**:
|
||||
|
||||
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.
|
||||
1. In the **Before you begin** page, select the **Next >** button.
|
||||
|
||||
|
||||
1. In the **Select installation type**/**Installation Type** page, select **Role-based or feature-based installation**, and then select the **Next >** button.
|
||||
|
||||
**Figure 6**. Configuring the computer as a KMS host
|
||||
1. In the **Select destination server**/**Server Selection** page, make sure **Select a server from the server pool** is selected. Under **Server Pool**, select the server on which to install KMS, and then select the **Next >** button.
|
||||
|
||||
6. Install your KMS host key by typing it in the text box, and then select **Commit** (Figure 7).
|
||||
1. In the **Select server roles**/**Server Roles** page, under **Roles**, select **Volume Activation Services**, and then select the **Next >** button.
|
||||
|
||||
|
||||
1. In the **Add features that are required for Volume Activation Services?** window that appears, select the **Add Features** button, and then select the **Next >** button.
|
||||
|
||||
**Figure 7**. Installing your KMS host key
|
||||
1. In the **Select features**/**Features** page, select the **Next >** button.
|
||||
|
||||
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).
|
||||
1. In the **Volume Activation Services** page, select the **Next >** button.
|
||||
|
||||
|
||||
1. In the **Confirm installation selections**/**Confirmation** page, select the **Install** button.
|
||||
|
||||
**Figure 8**. Activating the software
|
||||
1. Installation can take a few minutes to complete. Once the role installation completes, select the **Close** button.
|
||||
|
||||
The KMS key can be activated online or by phone. See Figure 9.
|
||||
1. Go to the **Start Menu** > **Windows Administrative Tools** and select **Volume Activation Tools**. The **Volume Activation Tools** window appears.
|
||||
|
||||
|
||||
1. In the **Volume Activation Tools** window:
|
||||
|
||||
**Figure 9**. Choosing to activate online
|
||||
1. In the **Introduction to Volume Activation Tools**/**Introduction** page, select the **Next >** button.
|
||||
|
||||
Now that the KMS host is configured, it will begin to listen for activation requests. However, it will not activate clients successfully until the activation threshold is met.
|
||||
1. In the **Select Volume Activation Method**/**Activation Type** page, select the **Key Management Service (KMS)** option, and specify the computer that acts as the KMS host. This computer can be the server on which the KMS role was installed, or another server/client computer. After the server/computer has been specified, select the **Next >** button.
|
||||
|
||||
1. In the **Manage KMS Host**/**Product Key Management** page, enter in the KMS host key in the text box under **Install your KMS host key**, and then select the **Commit** button.
|
||||
|
||||
1. If asked to confirm replacement of an existing key, select **Yes**.
|
||||
|
||||
1. After the product key is installed, in the **Product Key Installation Succeeded**/**Product Key Management** page, make sure **Activate Product** is selected, and then select **Next >** button to begin the activation process.
|
||||
|
||||
1. In the **Activate Product**/**Product Key Management** page, make sure the current product is shown under the **Select product** menu, and then select the desired activation method. The available methods are:
|
||||
|
||||
- **Active online** - If selecting this option, select the **Commit** button to finish activating the product online.
|
||||
|
||||
- **Active by phone** - If selecting this option:
|
||||
|
||||
1. Select the desired location from the **Select your location** drop-down menu, and then select the **Next >** button.
|
||||
|
||||
1. In the **Activate by Phone**/**Product Key Management** page, follow the instructions to activate the product by phone.
|
||||
|
||||
1. Once finished, select the **Commit** button.
|
||||
|
||||
1. In the **Activation Succeeded**/**Product Key Management** page, review the configuration options:
|
||||
|
||||
- If the configuration options are as expected, select the **Close** button.
|
||||
|
||||
- If configuration changes are desired:
|
||||
|
||||
1. Select the **Next >** button.
|
||||
|
||||
1. In the **Configure Key Management Service Options/Product Key Management** page, make the desired configuration changes, and then select the **Commit** button.
|
||||
|
||||
1. In the **Configuration Succeeded**/**Configuration** page, select the **Close** button.
|
||||
|
||||
Once the KMS host is configured, it begins to listen for activation requests. However, it doesn't activate clients successfully until the activation threshold is met.
|
||||
|
||||
## Verifying the configuration of Key Management Service
|
||||
|
||||
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.
|
||||
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 are processed. The verification process described here increments the activation count each time a client computer contacts the KMS host. If the activation threshold hasn't been reached, the verification generates an error message instead of 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.
|
||||
>
|
||||
> If you configured Active Directory-based activation before configuring KMS activation, you must use a client computer that doesn't first try to activate itself by using Active Directory-based activation. For example, a client computer that is a workgroup computer that isn't joined to a domain.
|
||||
|
||||
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 and run the command `Slmgr.vbs /ato`.
|
||||
2. On a client computer, open an elevated Command Prompt window and run the command:
|
||||
|
||||
```cmd
|
||||
cscript.exe 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 and run the command `Slmgr.vbs /dlv`.
|
||||
3. On a client computer or the KMS host, open an elevated Command Prompt window and run the command
|
||||
|
||||
```cmd
|
||||
cscript.exe 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).
|
||||
For more information about the use and syntax of the script `slmgr.vbs`, see [Slmgr.vbs Options](/windows-server/get-started/activation-slmgr-vbs-options).
|
||||
|
||||
## Key Management Service in earlier versions of Windows
|
||||
|
||||
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.
|
||||
3. Install the new KMS host key on your KMS host.
|
||||
4. Activate the new KMS host key by running the slmgr.vbs script.
|
||||
|
||||
For detailed instructions, see [Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows](https://go.microsoft.com/fwlink/p/?LinkId=618265) and [Update that enables Windows 7 and Windows Server 2008 R2 KMS hosts to activate Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=626590).
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Clients require RPC over TCP/IP connectivity to the KMS host to successfully activate.
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Volume Activation for Windows 10](volume-activation-windows-10.md)
|
||||
- [Key Management Services (KMS) activation planning](/windows-server/get-started/kms-activation-planning).
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.4 KiB |
@ -1,85 +1,116 @@
|
||||
---
|
||||
title: Install VAMT (Windows 10)
|
||||
description: Learn how to install Volume Activation Management Tool (VAMT) as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
|
||||
title: Install VAMT
|
||||
description: Learn how to install Volume Activation Management Tool (VAMT) as part of the Windows Assessment and Deployment Kit (ADK) for Windows.
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.prod: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/07/2022
|
||||
ms.date: 10/13/2023
|
||||
ms.topic: article
|
||||
ms.technology: itpro-fundamentals
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2022</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2019</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2016</a>
|
||||
---
|
||||
|
||||
# Install VAMT
|
||||
|
||||
This article describes how to install the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## Installing VAMT
|
||||
|
||||
You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
|
||||
This article describes how to install the Volume Activation Management Tool (VAMT). VAMT is installed as part of the Windows Assessment and Deployment Kit (ADK) for Windows.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>VAMT requires local administrator privileges on all managed computers in order to deposit confirmation IDs (CIDs), get the client products' license status, and install product keys. If VAMT is being used to manage products and product keys on the local host computer and you do not have administrator privileges, start VAMT with elevated privileges. For best results when using Active Directory-based activation, we recommend running VAMT while logged on as a domain administrator.
|
||||
>
|
||||
> VAMT requires local administrator privileges on all managed computers in order to deposit confirmation IDs (CIDs), get the client products' license status, and install product keys. If VAMT is being used to manage products and product keys on the local host computer and you don't have administrator privileges, start VAMT with elevated privileges. For best results when using Active Directory-based activation, we recommend running VAMT while logged on as a domain administrator.
|
||||
|
||||
>[!NOTE]
|
||||
>The VAMT Microsoft Management Console snap-in ships as an x86 package.
|
||||
>
|
||||
> The VAMT Microsoft Management Console snap-in ships as an x86 package.
|
||||
|
||||
### Requirements
|
||||
## Requirements
|
||||
|
||||
- [Windows Server with Desktop Experience](/windows-server/get-started/getting-started-with-server-with-desktop-experience), with internet access (for the main VAMT console) and all updates applied
|
||||
- [Windows Server with Desktop Experience](/windows-server/get-started/getting-started-with-server-with-desktop-experience), with internet access (for the main VAMT console) and all updates applied.
|
||||
|
||||
- Latest version of the [Windows 10 ADK](/windows-hardware/get-started/adk-install)
|
||||
- Latest version of the [Windows ADK](/windows-hardware/get-started/adk-install).
|
||||
|
||||
- Any supported [SQL Server Express](https://www.microsoft.com/sql-server/sql-server-editions-express) version, the latest is recommended
|
||||
- Any supported [SQL Server Express](https://www.microsoft.com/sql-server/sql-server-downloads) version. The latest is recommended.
|
||||
|
||||
- Alternatively, any supported **full** SQL instance
|
||||
- Alternatively, any supported **full** SQL instance.
|
||||
|
||||
### Install SQL Server Express / alternatively use any full SQL instance
|
||||
## Install SQL Server Express / alternatively use any full SQL instance
|
||||
|
||||
1. Download and open the [SQL Server Express](https://www.microsoft.com/sql-server/sql-server-editions-express) package.
|
||||
1. Download and open the [SQL Server Express](https://aka.ms/sqlexpress) package.
|
||||
|
||||
2. Select **Basic**.
|
||||
1. For **Select an installation type:**, select **Basic**.
|
||||
|
||||
3. Accept the license terms.
|
||||
1. In the **Microsoft SQL Server Server License Terms** screen, accept the license terms by selecting the **Accept** button.
|
||||
|
||||
4. Enter an install location or use the default path, and then select **Install**.
|
||||
1. In the **Specify SQL Server install location** screen under **INSTALL LOCATION \*:**, specify an install location or use the default path, and then select the **Install** button.
|
||||
|
||||
5. On the completion page, note the instance name for your installation, select **Close**, and then select **Yes**.
|
||||
1. Once the installation is complete, in the **Installation Has completed successfully!** page, under **INSTANCE NAME**, note the instance name for the installation. The instance name will be used later in the [Configure VAMT to connect to SQL Server Express or full SQL Server](#configure-vamt-to-connect-to-sql-server-express-or-full-sql-server) section.
|
||||
|
||||
|
||||
1. Once the instance name has been noted, select the **Close** button, and then select the **Yes** button to confirm exiting the installer.
|
||||
|
||||
### Install VAMT using the ADK
|
||||
## Install VAMT using the ADK
|
||||
|
||||
1. Download the latest version of [Windows 10 ADK](/windows-hardware/get-started/adk-install).
|
||||
1. Download the latest version of [Windows ADK](/windows-hardware/get-started/adk-install).
|
||||
|
||||
If an older version is already installed, it's recommended to uninstall the older ADK and install the latest version. Existing VAMT data is maintained in the VAMT database.
|
||||
If an older version is already installed, it's recommended to first uninstall the older ADK before installing the latest version. Existing VAMT data is maintained in the VAMT database.
|
||||
|
||||
2. Enter an install location or use the default path, and then select **Next**.
|
||||
1. Open the ADK installer that was downloaded in the previous step. The **Windows Assessment and Deployment Kit** window opens.
|
||||
|
||||
3. Select a privacy setting, and then select **Next**.
|
||||
1. In the **Windows Assessment and Deployment Kit** window:
|
||||
|
||||
4. Accept the license terms.
|
||||
1. At the **Specify Location** page, under **Install Path:**, enter an install location or use the default path. It's recommended to install at the default path. Once done, select the **Next** button.
|
||||
|
||||
5. On the **Select the features you want to install** page, select **Volume Activation Management Tool (VAMT)**, and then select **Install**. If desired, you can select additional features to install as well.
|
||||
1. In the **Windows Kits Privacy** page, select a privacy setting, and then select the **Next** button.
|
||||
|
||||
6. On the completion page, select **Close**.
|
||||
1. In the **License Agreement** page, accept the license terms by selecting the **Accept** button.
|
||||
|
||||
### Configure VAMT to connect to SQL Server Express or full SQL Server
|
||||
1. In the **Select the features you want to install** page, select **Volume Activation Management Tool (VAMT)**. If desired, select any additional features to install. Once done, select the **Install** button.
|
||||
|
||||
1. Open **Volume Active Management Tool 3.1** from the Start menu.
|
||||
1. Once installation is complete, the **Welcome to the Windows Assessment and Deployment Kit!** page is displayed. Select the **Close** button.
|
||||
|
||||
2. Enter the server instance name (for a remote SQL use the FQDN) and a name for the database, select **Connect**, and then select **Yes** to create the database. See the following image for an example for SQL.
|
||||
## Configure VAMT to connect to SQL Server Express or full SQL Server
|
||||
|
||||
|
||||
1. In the Start Menu under **Windows Kits**, select **Volume Active Management Tool 3.1**. The **Database Connection Settings** window opens.
|
||||
|
||||
For remote SQL Server, use `servername.yourdomain.com`.
|
||||
1. In the **Database Connection Settings** window:
|
||||
|
||||
1. Next to **Server:**, enter the server instance name as determined in the [Install SQL Server Express / alternatively use any full SQL instance](#install-sql-server-express--alternatively-use-any-full-sql-instance) section. If SQL is remote, make sure to use the FQDN.
|
||||
|
||||
1. Next to **Database:**, add a name for the database.
|
||||
|
||||
1. Once the database server and database names have been entered, select the **Connect** button.
|
||||
|
||||
1. Select the **Yes** button to create the database.
|
||||
|
||||
## Uninstall VAMT
|
||||
|
||||
To uninstall VAMT using the **Programs and Features** Control Panel:
|
||||
To uninstall VAMT:
|
||||
|
||||
1. Open **Control Panel** and select **Programs and Features**.
|
||||
1. Right-click on the Start Menu and select **Settings**.
|
||||
|
||||
2. Select **Assessment and Deployment Kit** from the list of installed programs and select **Change**. Follow the instructions in the Windows ADK installer to remove VAMT.
|
||||
1. Select **Apps** in the left hand pane.
|
||||
|
||||
1. In the right hand pane under **Apps**, select **Installed apps**.
|
||||
|
||||
Alternatively, select the following link to automatically open the **Settings** app to the **Installed apps** page:
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Installed apps](ms-settings:appsfeatures)
|
||||
|
||||
1. Scroll through the list of installed apps and find **Windows Assessment and Deployment Kit**.
|
||||
|
||||
1. Select the three dots **...** next to **Windows Assessment and Deployment Kit** and then select **Modify**. The **Windows Assessment and Deployment Kit** window opens.
|
||||
|
||||
1. In the **Windows Assessment and Deployment Kit** window:
|
||||
|
||||
1. In the **Maintain your Windows Assessment and Deployment Kit features** page, select **Change**, and then select the **Next** button.
|
||||
|
||||
1. In the **Select the features you want to change** page, uncheck **Volume Activation Management Tool (VAMT)**, and then select the **Change** button.
|
||||
|
||||
1. Once the uninstall is complete, the **Change is complete.** page is displayed. Select the **Close** button.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows feature update summary dashboard
|
||||
description: Provides a broader view of the current Windows OS upgrade status for all devices registered with Windows Autopatch.
|
||||
ms.date: 07/25/2023
|
||||
ms.date: 10/11/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -17,19 +17,19 @@ ms.collection:
|
||||
|
||||
# Windows feature update summary dashboard
|
||||
|
||||
The summary dashboard provides a broader view of the current Windows OS update status for all devices registered with Windows Autopatch.
|
||||
The Summary dashboard provides a broader view of the current Windows OS update status for all devices registered with Windows Autopatch.
|
||||
|
||||
The first part of the summary dashboard provides you with an all-devices trend report where you can follow the deployment trends within your organization. You can view if updates were successfully installed, failing, in progress, not ready or have their Windows feature update paused.
|
||||
The first part of the Summary dashboard provides you with an all-devices trend report where you can follow the deployment trends within your organization. You can view if updates were successfully installed, failing, in progress, not ready or have their Windows feature update paused.
|
||||
|
||||
**To view a generated summary dashboard for your Windows feature update deployments:**
|
||||
**To view a generated Summary dashboard for your Windows feature update deployments:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Select **Reports** from the left navigation menu.
|
||||
1. Under the **Windows Autopatch** section, select **Windows feature updates (preview)**.
|
||||
1. Under the **Windows Autopatch** section, select **Windows feature updates**.
|
||||
|
||||
## Report information
|
||||
|
||||
The following information is available in the summary dashboard:
|
||||
The following information is available in the Summary dashboard:
|
||||
|
||||
| Column name | Description |
|
||||
| ----- | ----- |
|
||||
@ -48,5 +48,5 @@ The following options are available:
|
||||
|
||||
| Option | Description |
|
||||
| ----- | ----- |
|
||||
| Refresh | The option to **Refresh** the summary dashboard is available at the top of the page. This process will ensure that the summary dashboard view is updated to the latest available dataset from within the last 24-hour period. |
|
||||
| Refresh | The option to **Refresh** the Summary dashboard is available at the top of the page. This process ensures that the Summary dashboard view is updated to the latest available dataset from within the last 24-hour period. |
|
||||
| Summary links | Each column represents the summary of included devices. Select the hyperlinked number to produce a filtered report in a new browser tab. |
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality update summary dashboard
|
||||
description: Provides a summary view of the current update status for all devices enrolled into Windows Autopatch with Autopatch groups
|
||||
ms.date: 07/25/2023
|
||||
ms.date: 10/04/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -17,7 +17,7 @@ ms.collection:
|
||||
|
||||
# Windows quality update summary dashboard
|
||||
|
||||
The summary dashboard provides a summary view of the current update status for all devices enrolled into Windows Autopatch.
|
||||
The Summary dashboard provides a summary view of the current update status for all devices enrolled into Windows Autopatch.
|
||||
|
||||
**To view the current update status for all your enrolled devices:**
|
||||
|
||||
@ -29,7 +29,7 @@ The summary dashboard provides a summary view of the current update status for a
|
||||
|
||||
## Report information
|
||||
|
||||
The following information is available in the summary dashboard:
|
||||
The following information is available in the Summary dashboard:
|
||||
|
||||
| Column name | Description |
|
||||
| ----- | ----- |
|
||||
@ -47,5 +47,5 @@ The following options are available:
|
||||
|
||||
| Option | Description |
|
||||
| ----- | ----- |
|
||||
| Refresh | The option to **Refresh** the summary dashboard is available at the top of the page. This process will ensure that the summary dashboard view is updated to the latest available dataset from within the last 24-hour period. |
|
||||
| Refresh | The option to **Refresh** the Summary dashboard is available at the top of the page. This process ensures that the Summary dashboard view is updated to the latest available dataset from within the last 24-hour period. |
|
||||
| Summary links | Each column represents the summary of included devices. Select the hyperlinked number to produce a filtered report in a new browser tab. |
|
||||
|
||||
@ -34,7 +34,7 @@ sections:
|
||||
Windows Autopatch doesn't support local (on-premises) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Azure AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid).
|
||||
- question: Will Windows Autopatch be available for state and local government customers?
|
||||
answer: |
|
||||
Windows Autopatch is available for all Windows E3 customers using Azure commercial cloud. However, Autopatch isn't currently supported for government cloud (GCC) customers. Although Windows 365 Enterprise is in the Azure Commercial cloud, when Windows 365 Enterprise is used with a GCC customer tenant, Autopatch is not suppported.
|
||||
Windows Autopatch is available for all Windows E3 customers using Azure commercial cloud. However, Autopatch isn't currently supported for government cloud (GCC) customers. Although Windows 365 Enterprise is in the Azure Commercial cloud, when Windows 365 Enterprise is used with a GCC customer tenant, Autopatch is not supported.
|
||||
- question: What if I enrolled into Windows Autopatch using the promo code? Will I still have access to the service?
|
||||
answer: |
|
||||
Yes. For those who used the promo code to access Windows Autopatch during public preview, you'll continue to have access to Windows Autopatch even when the promo code expires. There's no additional action you have to take to continue using Windows Autopatch.
|
||||
|
||||
@ -70,7 +70,7 @@ To register the applications, follow these steps:
|
||||
:::column span="3":::
|
||||
3. Review the permissions requested by the *Microsoft Pin Reset Service Production* application and select **Accept** to confirm consent to both applications to access your organization.
|
||||
>[!NOTE]
|
||||
>After accepance, the redirect page will show a blank page. This is a known behavior.
|
||||
>After acceptance, the redirect page will show a blank page. This is a known behavior.
|
||||
:::column-end:::
|
||||
:::column span="1":::
|
||||
:::image type="content" alt-text="Screenshot showing the PIN reset service permissions final page." source="images/pinreset/pin-reset-service-prompt-2.png" lightbox="images/pinreset/pin-reset-service-prompt-2.png" border="true":::
|
||||
|
||||
@ -44,12 +44,12 @@ The table shows the minimum requirements for each deployment. For key trust in a
|
||||
|
||||
The table shows the minimum requirements for each deployment.
|
||||
|
||||
| Key trust <br/> Group Policy managed | Certificate trust <br/> Group Policy managed|
|
||||
| --- | --- |
|
||||
|Any supported Windows client versions|Any supported Windows client versions|
|
||||
| Windows Server 2016 Schema | Windows Server 2016 Schema|
|
||||
| Windows Server 2008 R2 Domain/Forest functional level | Windows Server 2008 R2 Domain/Forest functional level |
|
||||
| Any supported Windows Server versions | Any supported Windows Server versions |
|
||||
| Any supported Windows Server versions | Any supported Windows Server versions |
|
||||
| Any supported Windows Server versions | Any supported Windows Server versions |
|
||||
| AD FS with 3rd Party MFA Adapter | AD FS with 3rd Party MFA Adapter |
|
||||
| Requirement | Key trust <br/> Group Policy managed | Certificate trust <br/> Group Policy managed|
|
||||
| --- | --- | ---|
|
||||
| **Windows Version** | Any supported Windows client versions|Any supported Windows client versions|
|
||||
| **Schema Version**| Windows Server 2016 Schema | Windows Server 2016 Schema|
|
||||
| **Domain and Forest Functional Level**| Windows Server 2008 R2 Domain/Forest functional level | Windows Server 2008 R2 Domain/Forest functional level |
|
||||
| **Domain Controller Version**| Any supported Windows Server versions | Any supported Windows Server versions |
|
||||
| **Certificate Authority**| Any supported Windows Server versions | Any supported Windows Server versions |
|
||||
| **AD FS Version**| Any supported Windows Server versions | Any supported Windows Server versions |
|
||||
| **MFA Requirement**| AD FS with 3rd Party MFA Adapter | AD FS with 3rd Party MFA Adapter |
|
||||
Loading…
x
Reference in New Issue
Block a user