Unfortunately, Germany West Central is not supported right now. I'll update the docs to support this. I'll also work to ensure that the Portal UX reflects this, sorry for the inconvenience! These are the list of supported regions: Australia East
Brazil South
Canada Central
Canada East
Central India
Central US
East Asia
East US
East US 2
France Central
Japan East
Korea Central
North Central US
North Europe
Norway East
South Africa North
South Central US
Southeast Asia
Sweden Central
Switzerland North
UAE North
UK South
UK West
West Central US
West Europe
West US
West US 2
West US 3
Sucessfull installation of Arc-enabled server and WAC extension but no WAC-LogIn to any ARC-server possible
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 ?
-
Prasidh Arora 75 Reputation points Microsoft Employee
2023-11-01T18:11:25.5733333+00:00
2 additional answers
Sort by: Most helpful
-
Prasidh Arora 75 Reputation points Microsoft Employee
2023-11-01T16:00:23.6833333+00:00 Hey, what region is your Arc-enabled server running in? There are still a couple of regions that WAC doesn't support (that result in this error), and we are working to close that gap ASAP.
-
Rudolf Dietz 20 Reputation points
2023-11-01T17:58:55.2166667+00:00 Arc-enabled servers are working in region Germany.