Solutionįor VMs running Windows 10 Enterprise multi-session (also known as Windows 10 Enterprise for Virtual Desktops) in Azure Virtual Desktop, this step isn't required. Generally, Azure VM activation issues occur if the Windows VM isn't configured by using the appropriate KMS client setup key, or the Windows VM has a connectivity problem to the Azure KMS service (, port 1688). Please see the Application Event Log for additional information. No Key ManagementService (KMS) could be contacted. When you try to activate an Azure Windows VM, you receive an error message resembles the following sample:Įrror: 0xC004F074 The Software LicensingService reported that the computer could not be activated. Azure US Gov national cloud regions: :1688.Azure Germany national cloud regions: :1688.Azure China 21Vianet national cloud regions: :1688 or :1688.Azure public cloud regions: :1688 or :1688.When using this troubleshooting guide, use the appropriate KMS endpoint that applies to your region. ![]() ![]() Understanding Azure KMS endpoints for Windows product activation of Azure Virtual MachinesĪzure uses different endpoints for KMS (Key Management Services) activation depending on the cloud region where the VM resides. If you have trouble when activating Azure Windows virtual machine (VM) that is created from a custom image, you can use the information provided in this document to troubleshoot the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |