'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Configure Office 2021 LTSC Installation XML for KMS Activation
Question details
The user needs to know which key to use in the configuration XML when deploying Office 2021 LTSC volume edition using KMS activation.
- Product
- Microsoft Office 2021 LTSC
- Device & OS
- not provided
- Scenario
- An organization is preparing an enterprise volume deployment of Office 2021 LTSC and setting up KMS activation.
- Observed behavior
- There is confusion over whether the Office Deployment Tool XML configuration file should contain the generic KMS client key or the organization's specific volume license key.
Ensure you have downloaded the latest Office Deployment Tool (ODT) and that your organization's KMS host is fully configured, discoverable, and reachable by client computers on your network.
Configure the Deployment XML and KMS Host
Deploy Office 2021 LTSC via KMS by using a generic KMS client key in your XML file and applying your actual volume license key exclusively to the KMS host server.
In a Key Management Service (KMS) environment, individual client computers do not need your organization's unique volume license key. Instead, they use a generic key that directs them to authenticate against your centralized KMS host.
Open your Office Deployment Tool configuration XML file in a text editor like Notepad.
Ensure the generic KMS client key (GVLK) for Office 2021 LTSC is used in the PIDKEY field of your configuration file. Do not input your organization's unique volume key here.
Install and activate your organization's valid volume license key on the central KMS host server using the Volume Activation Management Tool (VAMT) or command line.
Confirm that the KMS host is properly configured, discoverable via DNS, and reachable by the client computers attempting to activate.
Simplify Your Office Deployment with WPS Office
Avoid complex KMS server setups and deployment XML configurations. WPS Office offers a lightweight, highly compatible alternative that is easy to deploy across your organization without the heavy activation overhead of Microsoft Office.
- 1. Download the installer: Visit the official WPS Office website to download the lightweight installation package.
- 2. Deploy to client machines: Run the installer on your target computers without needing to configure complex activation servers.
- 3. Open your files: Launch WPS Office and open your existing Word, Excel, and PowerPoint files with seamless formatting preservation.
Frequently Asked Questions
What is a generic KMS client key?
A generic KMS client key, also known as a GVLK (Generic Volume License Key), is a default product key used in the deployment XML. It tells the Office installation to bypass standard internet activation and instead seek out a local KMS host server on your network for activation.
Where should I install my actual volume license key?
Your actual volume license key (CSVLK) should only be installed and activated on your centralized KMS host server. It should never be included in the deployment XML file distributed to individual client computers.
Why are my client computers failing to activate via KMS?
Client computers typically fail to activate if the KMS host is unreachable on the network, if the necessary DNS SRV records for the KMS host are missing, or if the KMS host has not yet reached the minimum activation request threshold required by Microsoft (typically 5 for Office).
