deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 10:53:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Added missing comma; fixed awkward phrasing

Browse Source
This commit is contained in:
Gary Moore
2021-03-15 16:56:50 -07:00
committed by GitHub
parent 45bbec6a6a
commit 0ca5e2d747
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/volume-activation/install-vamt.md
View File

@ -25,7 +25,7 @@ This topic describes how to install the Volume Activation Management Tool (VAMT)
You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for Windows 10.
>[!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 Active Directory-Based Activation use, for best results 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 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. 
>[!NOTE]
>The VAMT Microsoft Management Console snap-in ships as an x86 package.
@ -75,7 +75,7 @@ You install VAMT as part of the Windows Assessment and Deployment Kit (ADK) for
![Server name is .\SQLEXPRESS and database name is VAMT](images/vamt-db.png)
For remote SQL Server use `servername.yourdomain.com`.
For remote SQL Server, use `servername.yourdomain.com`.