Forum Discussion
Microsoft Office Standard 2019 volume license activation
Verify that the config file has the following <PIDKEY Value="AAAAABBBBBCCCCCDDDDDEEEEE" /> (AAAAABBBBBCCCCCDDDDDEEEEE should be replaced with your Product Key).
Also, I don't know if you are an Administrator, so you might need to enable a non-admin user to activate an Office by using MAK.
https://docs.microsoft.com/en-us/deployoffice/vlactivation/activate-office-by-using-mak#configure-mak-activation-in-the-configxml-file
You can see the content of Configuration file :-
<Configuration ID="8b4eb8be-3d7c-43e5-bd62-d2599ad52ec2">
<Add OfficeClientEdition="32" Channel="PerpetualVL2019">
<Product ID="Standard2019Volume" PIDKEY="6NWWJ-YQWMR-QKGCB-6TMB3-9D9HK">
<Language ID="en-us" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Publisher" />
</Product>
<Product ID="LanguagePack">
<Language ID="en-us" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="SCLCacheOverride" Value="0" />
<Property Name="AUTOACTIVATE" Value="0" />
<Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
<Property Name="DeviceBasedLicensing" Value="0" />
<Updates Enabled="TRUE" />
<RemoveMSI />
</Configuration>I also ran this config file using command prompt as an admin with Office Deployment Tool (setup.exe).
Do i have to connect to KMS server for successful activation of MS Office?
So the key you have is a Generic Volume License Keys (GVLK), and you will need to replace it with your MAK client activation key. If you want to use the KMS, you will need to stand up a KMS server on your network and license the KMS server to accept the GVLK of your Office Product.
KMS vs. MAK; Biggest difference is that KMS requires you to "re-activate," which is automatically done every 180 from client to KMS server to need some connection (VPN).
