WAC is a browser-based tool. It requires a WEB login each time you launch it. It does not use the credentials of the currently logged-in user. And each time you switch from a machine to another, you'll have to re-enter credentials again.

Please provide a working SSO system, so that we do not have to re-type our password several times an hour.

As already said, WAC is an admin tool. It must be "click and go". We definitely don't have time to administer the admin tool, and to understand why SSO does not work.

As said hundreds of times : when you provide a new admin tool, and you force people to use it instead of the old ones, please ensure it works at least as good as the old ones. For now, there are a few new interesting things in WAC, but there are far more problems with it. It's just more and more time lost for us...

Version 2007. Hyper-V test/dev sandbox, machines only have access to each other. Only the management Win 10 VM running WAC has access to the hypervisor, but still not our prod network or www.

File share on hypervisor set as feed. WAC sees extensions there, and pulls their metadata. WAC is set to no internet access. Extension installs still fail because they cannot reach 'aka.ms'

These are microsoft-published extensions, but all tested fail. WAC itself was installed from an MSI in the same share.

Issue: when local feed was added, the default feed was not removed. Despite WAC listing on the 'available extensions' entries which feed is offering the extension, it was still trying the default feed. The fix was to remove the default feed, at which point WAC successfully loaded the extensions.

WAC should be updated to try to install extensions using the feed listed in the displayed metadata /first/, and never try the default feed URL when configured to not use internet. In the meantime, WAC documentation should be updated to reflect this necessary configuration change for offline extension management; at present the documentation does not lead users to a working state.

Doesn't Microsoft have enough money to pay color screens to its developers ? ;-) Why is the UI using only two colors (black, white, and a little bit of blue) ?

The good old MMC snapins use a lot of icons, colors, graphics, which allow to distinguish things visually and rapidly.

If you want to develop a new admin tool, it has to be (at least) as good as the old one. This UI is terribly flat, with lots of things with the same color. This is a severe drawbacks for engineers who highly rely on "visual" aspect and ordering of things.

Don't create flat designs just because Google does that, or to follow a "mood". On an engineering point of view, this UI is clearly far less efficient than the old MMC snapins.That's not only related to aesthetics. Colors and graphics do really help for understanding data and identifying things.

Moreover, this UI also lacks some elementary features we've been using for years, such as context menu (right click) and modularity (I can add "extensions", but I can not remove things I don't need).

Kind regards

for several of our hyperv clusters we are unable to manage updates via WAC. If I run the standalone CAU tool (as admin) on my laptop I can verify the cluster updating readiness and all show as good (aside from proxy that we do not use). I can also initiate updates and they install as they have done since we first set this up several years ago. If I open updates for the clusters in WAC cluster manager I am told that
"The failover cluster nodes must be enabled for remote management via WMIv2"
and
"Windows PowerShell remoting should be enabled on each failover cluster node"
Powershell remoting and the WMI service and firewall rules are set by group policy and show as such via the standalone CAU tool so why does WAC find a false error? Due to this error we are unable to manage updates via WAC.

WAC/Gateway Server: 1910.2

Description
Gateway server is located in a site of a corporate domain. When adding security groups AD or local it fails saying that the group was not found in the sub site. Example below

Request:
Allow modification of the LDAP settings or use the FQDN of the domain rather than accepting the domain name of the gateway server.

Note: Please don't ask why it is configured that way or if I can change this. This configuration was in place long before my time and will not be modified.

Example:
AD Domain: na.corp.com
AD NETBIOS Domain: (CORP)
Gateway FQDN: wac.site.corp.com
- Gateway is part of CORP (na.corp.com) domain

Adding a group located in AD (CORP)
Group Name: WACSiteDBAs
- Added as CORP\WACSiteDBAs
- Added as na.corp.com\WACSiteDBAs

Adding a group located on the gateway (wac.site.corp.com)
Group Name: SiteDBAs
- Added as WAC\SiteDBAs
- Added as BUILTIN\SiteDBAs
- Added as SiteDBAs

Error:
Group <GroupName or Domain\GroupName> does not exist in domain site.corp.com or on the gateway machine. Individual users cannot be added to this list.
- This error is the same for each attempt

From Event Log:
Microsoft-ServerManagementExperience

• <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


• <System>
  <Provider Name="SMEGateway" />
  <EventID Qualifiers="0">0</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2020-04-02T17:06:11.258666700Z" />
  <EventRecordID>155665</EventRecordID>
  <Channel>Microsoft-ServerManagementExperience</Channel>
  <Computer>wac.site.corp.com</Computer>
  <Security />
  </System>


• <EventData>
  <Data>The server could not be contacted.</Data>
  </EventData>
  </Event>

When deploying WAC on a Windows Server as the ‘Windows Admin Center’ Service you cannot access Internet Feeds for Extensions (e.g. https://aka.ms/sme-extension-feed) via a proxy server if the Server does not have direct access to the Internet. This means the user experience is diminished as new Extensions cannot downloaded via the Extensions section in WAC and / or existing extensions cannot be updated via the Extensions section.

It can be achieved by setting a proxy for the Network Service account that the WAC Service runs under, but that's not ideal.

Suggest adding the option to configure a proxy the ‘Internet Access’ section under settings. Users would need to be able to specify the proxy server address, port, and any credentials if authentication is used (but have the option to just anonymous access with no credentials)

select all servers> manage as > Specify your credentials > error

WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.

which one? i tried few servers, it works, firewall open. So how i can know which one has a problem?

must be accessibility a status near each host in main list.

online\offline\online but can't access.