Why my Windows Server 2022 VM right after creating has been giving me Health Status: Unhealthy?

Question

Hello team,

For the first time, I have come across this issue which I had never experienced in the past. I had to spin up Windows Server 2022 DC which can be seen below in the screenshot on 10/28 for my testing. For some reason, there is only one option of NSG, no more NIC's NSG options is available which can be seen in the first screenshot anyways, I allowed port 3389 on NSG to RDP it and I was able to do it. Guest agent is working, VM is being RDPd, updates have been applied, I had reapplied+redeployed the VM, nothing changed. VM is set to autoshutdown, and I turned it back on after a couple of days, and in the second screenshot which is visible that Health State: Unhealthy, though it's a new feature but on the portal I haven't found any guidelines to remediate the issue. Additionally, 3rd screenshot below, it shows nothing in the boot diagnostics screenshot. This Unhealthy feature is totally new on the Azure portal but I am perplexed how would I be able resolved it. Any answer or resolution to that issue will be highly appreciated. Thanks.

Thanks,

Mody K

Answer 1

Hi Mahmood Khan,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

I understand that the issue you're experiencing with your Azure Windows Server 2022 virtual machine is that it is showing an 'Unhealthy' state and having problems with Boot Diagnostics. Here are some steps you can take to troubleshoot and resolve the issue

• Make sure all the NICs on the VM are properly configured and have NSGs assigned. In the Azure portal, navigate to the Networking tab for the VM and confirm that each NIC is associated with the appropriate NSG.
• Make sure the Azure VM Agent is properly installed and running. You can verify this in the Azure portal under the "Extensions + applications" section for your VM. If the agent is not working as expected, you may need to reinstall the Azure VM Agent.
• Ensure that all settings are correctly configured post-redeployment. your boot diagnostics screenshot is empty, enabling and reviewing the boot diagnostics logs may help identify any issues during the VM's boot process.
• To rely on the Health State, you will need to properly configure the probe.

Please refer to the link for more details on the issue:
Application Health extension
Azure boot diagnostics

If you have any further queries, do let us know.

If the answer is helpful, please click "Accept Answer" and "Upvote it."