Unable to activate Win Server 2022 DC Azure edition

Hi Ghulam,

As per Microsoft you will need to allow 2 additional IP addresses via the FW and check this blog for detailed steps - https://techcommunity.microsoft.com/t5/azure-compute-blog/azure-windows-virtual-machine-activation-two-new-kms-ip/ba-p/3621189

Hope this helps.

JS

==

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

Hello @Ghulam Abbas

Activation issues can stem from a variety of factors. Let's go through some troubleshooting steps to help you identify and potentially resolve the root cause:

Network Connectivity:

• You mentioned that both ping and TCP tests to kms.core.windows.net on port 1688 are failing. This could be indicative of a network issue. Ensure that outbound internet connectivity is allowed for these instances.
• Check if there are any network security group (NSG) rules or Azure Firewall rules that might be blocking outbound traffic on port 1688. Make sure that the instances can reach external servers, especially the KMS server.
• Verify that the route table associated with the subnet containing these instances is correctly configured to route traffic to the internet.

Firewall Settings:

• You mentioned that you've allowed port 1688 in the Windows Firewall. Double-check that the rule is correctly configured and applied to both the domain and private profiles.
• If there's a network-level firewall within your organization, make sure it's not blocking traffic to the KMS server.

DNS Resolution:

• Ensure that the instances can resolve the DNS name kms.core.windows.net. Incorrect DNS resolution could lead to connectivity issues.

Time Synchronization:

• KMS activation relies on accurate time synchronization. Ensure that the system time on the affected servers is correct and synchronized with a reliable time source.

Proxy Configuration:

• If you're using a proxy server to access the internet, make sure that the proxy configuration on the affected servers is correctly set up.

Azure Route Table and Network Configuration:

• Verify that the route table associated with the subnet is correctly configured to route traffic to the Azure KMS server.
• Check the network configuration of the instances, including subnet associations, route tables, and network security groups, to ensure they match the working servers.

Azure Resource Health and Service Issues:

• Check Azure Resource Health and Service Health to see if there are any ongoing issues in the Azure region that could be affecting activation or network connectivity.

Azure Support:

• If the issue persists, consider reaching out to Azure support for more personalized assistance. They can provide insights into the specific Azure environment and help troubleshoot the issue.

Remember that diagnosing activation and connectivity issues can sometimes be complex due to the interaction of multiple factors. It's recommended to systematically go through each potential cause, checking and validating the configuration at each step.

If this does answer your question, please accept it as the answer as a token of appreciation.