If you have a legitimate Volume License but the server refuses to accept it, Microsoft has a known issue with the LicenseDIAG.cmd tool. Run:
C:\Program Files\Microsoft\Exchange Server\V15\Bin\LicenseDiag.cmd -Reset
This forces Exchange to purge its local cache of the license and re-query AD. After a reboot, the "invalid" error usually vanishes.
To resolve the issue, follow this structured troubleshooting path: exchange 2019 product key invalid
A common misconception is that you need a different product key for Enterprise CAL features. You do not. The product key only unlocks either "Exchange Server 2019 Standard Edition" or "Exchange Server 2019 Enterprise Edition." The CALs (Client Access Licenses) are a separate legal licensing matter, not a technical product key.
The error occurs strictly on the edition mismatch or syntax issues. If you have a legitimate Volume License but
If you prefer to use the standard method, follow these steps carefully:
Sometimes the graphical EAC fails while PowerShell works. Use the same Set-ExchangeServer cmdlet. If that fails with a licensing error, run: This forces Exchange to purge its local cache
Reset-ComputerMachinePassword -Credential (Get-Credential)
(A domain trust issue can cause licensing validation to fail.)
Assuming you have a valid key and the environment is healthy, follow this exact process:
Microsoft does not offer a public "key checker" for Exchange, but you can test the key using the Volume Activation Management Tool (VAMT) or by attempting to use the key on a fresh, offline, disposable virtual machine (e.g., a trial VM you delete after testing). If the key works there, your original server has an environmental issue.