I did install the ARC agent on a few onprem Server2022 machines (virtual server on a VMware host) and in addition on one physical Server2022. All these hybrid servers are member servers of my AD DS. There has been no local WAC installation running on any of these machines before enabling them to act as ARC-enabled servers. All installation steps described in document https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/manage-arc-hybrid-machines
have been executed without any shown errors. I am using the new ARC icon appearing since recent in the taskbar of each Server2022 for starting up the Azure Arc Setup procedure. For network connectivity I did select : Public endpoint
All servers did show at the end a well connected state like shown in the following screenshot:
Next step : Installing the WAC extension to the Arc-enabled servers clicking on WAC (Preview ) button in the Azure Arc pane. As for the configuration of the WAC listening port I did stay with port 6516.
After approx. 10 minutes the WAC setup terminates with the following message:
I did check the status of service ServerManagementGateway, it was active on all servers.
I did run through all recommended test steps of the linked Troubleshoot connection documentation, but there was no negative result at any of test steps.
Then I tried to open WAC directly on the ARC-enabled server: https://localhost:6516
WAC starting page comes up but stays there like a frozen app. Maybe this no bug, because a Azure Arc-connected server with installed WAC extension should no longer be used anymore like a classic locally installed WAC tool for managing local onprem servers.
Has anybody an idea what the root cause could be of this connection issue ?
What can I do else to catch and fix my problem ?