MicrosoftDocs / Windows-Admin-Center-Ideas-and-Feedback

Windows Admin Center's hub for ideas and feedback.
Creative Commons Attribution 4.0 International
20 stars 9 forks source link

"Managed Server" installation type desired, but defaults to "Gateway" installation type. Error is "Access is Denied." Troubleshooting Steps Insufficient. What is Wrong? #103

Open geogherkins opened 2 years ago

geogherkins commented 2 years ago

Gateway Version: 1.3.44065.0 Extension Version: None

To Reproduce Steps to reproduce the behavior:

  1. From a Windows 10 client in the same domain, go to 'https://osfstst.domain.com' to connect to a Windows Server 2019 Data Center Edition server containing a newly installed Windows Admin Center.
  2. Click on 'osfstst.domain.com [Gateway]' hyperlink on the main Windows Admin Center | All connections page.
  3. 'Specify your credentials' window opens, provided Domain Admin credential does not work.
  4. Error message result: "The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol."

There are two identically-configured Win2019 servers, OSFSTST and ASFSTST. I can connect to ASFSTST when the WAC is running from OSFSTST. And vice-versa. If the gateway is running from ASFSTST I can connect to OSFSTST but not to itself (ASFSTST).

I think the root cause is the installation type. I did NOT specify that I wanted a "Gateway" installation type. I merely am trying to use the "Managed Server" installation type. https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/plan/installation-options

Log contains: 400 - CimException: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. 401 - PSRemotingTransportException: Connecting to remote server osfstst.corp.domain.com failed with the following error message : Access is denied. DELETE - 404 - (31): /api/nodes/asfstst.corp.domain.com/features/powershellApi/pssessions/aff976a7-fcbf-4051-90b4-58b15b1607a7?api-version=2019-02-01 404 - PSRemotingTransportException: Connecting to remote server asfstst.corp.domain.com failed with the following error message : The request for the Windows Remote Shell with ShellId AFF976A7-FCBF-4051-90B4-58B15B1607A7 failed because the shell was not found on the server.

Expected behavior Connection to server OSFSTST to manage the server... This is also the server which is hosting Windows Admin Center.

Screenshots & Additional context

Attaching file Microsoft-ServerManagementExperience.log

geogherkins commented 2 years ago

Attached logs. Microsoft-ServerManagementExperience.log

geogherkins commented 2 years ago

Additional symptom: Cannot configure "Storage Replica" because WAC can only authenticate to the "Gateway" server hosting WAC. The Storage Replica wizard needs to authenticate to both the gateway hosting WAC (which in this case is the primary file server) and the target (another server secondary storage replica partner).

I will use native PowerShell Storage Replica cmdlets to manage the primary and secondary Storage Replica partners. At this time WAC is completely useless.

ghost commented 2 years ago

Dont you love how you got no response?

geogherkins commented 2 years ago

Ironic, isn't it?

x-layer commented 2 years ago

Same problem here.

WAC 2110 installed on WS 2022. Get the same errors when trying to install Storage Migration Service.

trungtran-msft commented 2 years ago

@geogherkins Our engineers weren't able to reproduce this issue. Did you configure configure WinRM over HTTPS by mistake?

geogherkins commented 2 years ago

Trungtran, Well, I just don't know whether I've "configured WinRM over HTTPS" by mistake. The original posting says that there are few troubleshooting tips, and I've followed all of those I can find. How do I confirm how WinRM is configured (or not)? Also, note that posting earlier from x-layer and perhaps? ghost has the same difficulty. It has been over two months since I attempted WAC, my recall is not adequate to even guess. Probably need to uninstall WAC and try again. Do you have troubleshooting steps to do that?