Forum Widgets
Latest Discussions
WAC vMode fails validating SMB
Hi Reviewing vMode and try add a Hyper-V 2025 (non hyperconverged) cluster with a FC SAN. Fails on Validating "SMB port accessibility". Have gone through firewall settings and opened all neccesary ports that i can find mentioned. Even tried without FW turned off without any success so hit the wall now. WAC vMode is installed on a vm running Win2025std and in same domain as the cluster (and hosts) i try to add. Probably some obvious thing i have missed so any suggestions?
Certificate Error Connecting to only to some of the Cluster's resources
Latest version of WAC, winrm configured to connect over HTTPS. No issues connecting to the servers that are members of the cluster, or clients and other servers in our AD. No issues connecting to the cluster Dashboard (I can see health, CPU usage, etc.) and some of the resources (such as Drives, Volumes, Servers). Configuration -> Settings or Security works fine. It's only when I go to some resources, such as virtual switches, GPU's or a handful of others that I get errors connecting to member servers; Specifically, the error will state that for each server: Connecting to remote server servername.local failed with the following error message : The server certificate on the destination computer (servername.local:5986) has the following errors: The SSL certificate contains a common name (CN) that does not match the hostname. The one oddity I see is that .local is being added to the end of the server name. Also, servername will not contain the domain extension, just the name. Here's what I've checked so far: DNS is correct for the member servers and the cluster, both with Host (A) and PTR entries, can be pinged and resolved. As far as I can tell the certificates are setup correctly, no issues connecting to the member servers individually, or the cluster at first. The AD entry for the cluster is in place with the correct permissions for the cluster's service account I've read that .local is appended if the server/cluster is not part of AD, but that's not the case. We have two additional clusters and this issue does not appear on them. I also have not been able to identify any obvious differences between the setup of the two fully functioning clusters and this one. In the Event Viewer on the WAC server, under Applications and Service Logs _> WindowsAdminCenter, I can see Error Entries ID 304 for each member server with a similar message as above: Unable to create PowerShell session on node, status: 400, error code:PSRemotingTransportException, error message:Connecting to remote server server.local failed with the following error message : The server certificate on the destination computer (server.local:5986) has the following errors: The SSL certificate contains a common name (CN) that does not match the hostname. For more information, see the about_Remote_Troubleshooting Help topic.. As a side note, opening a remote Powershell session to each member server via WAC works fine and by contrast, in the WAC Event viewer there will be corresponding Information entries list the server's FQDN. Here's an example Category: Microsoft.AspNetCore.Hosting.Diagnostics EventId: 2 SpanId: 50d2635d1f6eb737 TraceId: b8c8e1de80ac2f84f1230c5ec3305b38 ParentId: 3e0619ce2c5decca ConnectionId: 0HNMB39BE0AS7 RequestId: 0HNMB39BE0AS7:0000009F RequestPath: /api/PowerShell/nodes/serverFQDN/invokeCommand Request finished HTTP/2 POST https://WACserverFQDN:6601/api/PowerShell/nodes/serverFQDN/invokeCommand - 200 - application/json;+charset=utf-8 230.3283ms It seems that when it comes to accessing only some of the cluster's resources WAC no longer has the member servers FQDNs, and I'm not sure where to look for changing that. Anyway, any guidance would be appreciated.
Shared Connections not deleting
Hi there - I have Windows Admin Center v1.5.2306.14001 installed and have 1142 shared connections. When I attempt to delete all shared connections, WAC looks like it goes through deleting them - but then gets to a specific number and just stops. If I then refresh the browser, it returns 1142 shared connections again - so, it looks like no shared connections have actually been deleted. If I try to delete just one shared connection, I get the same outcome. I've also tried re-importing some connections again with the below PowerShell command in the hope it'll remove any connections not specified in the csv, but it's still the same outcome. Import-Connection <WAC URL> -fileName WAC.csv -prune FYI - the above is being done with my user account, which has gateway administrator permissions in WAC. Has anyone else experienced this issue? Thanks
Modernized Gateway Extension Support via WAC SDK
Hello, I would like to build a gateway plugin for the latest WAC v2511 but according to this documentation, the latest SDK package does not support the latest modernized gateway extensions. Is there a way to workaround this without downgrading WAC version? https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/extend/develop-gateway-plugin “The Windows Admin Center SDK and developer tools have not yet been updated to support development of gateway plug-ins compatible with the Windows Admin Center modernized gateway. Following this guide will not result in a .NET 8 extension compatible with the modernized gateway.
WAC can't connect to gateway itself. workgroup
I have Hyper-V server core. And WAC installed on it. WAC version 2009, 1.2.2009.2102 When I opening it from PC inside my network, I can see the server itself. But when I'm trying to open server itself - I'm getting warning: To perform a single sign-in using your Windows account, you might need to set up Kerberos constrained delegation. And error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". Did everything what mentioned in this article. https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/support/troubleshooting#using-windows-admin-center-in-a-workgroup Everything is enabled on the server. User is local admin, and in the group Remote Management Users. WinRM is working and enabled. (Actually, before WAC I've configured remote access for Hyper-V console, system console, and everything is working.) But when I'm trying to connect via WAC with any user - I'm receiving this error.Windows Admin Center - Couldn't configure PowerShell authentication error
We have a lab setup to test migrating VMWare VMs to Hyper-V. Everything was working fine, however today whenever we try and access the settings of a VM we get an error. We're going through Cluster Resources -> Virtual Machines -> VMName -> Settings. The error is: Notification details Error Error Couldn't configure PowerShell authentication 1:25:15 PM Sourcehttps://edutech-hv-2.edutech-rd.local/clustermanager/connections/cluster/edutechrd.edutech-rd.local/tools/virtualmachines/settings/parent/virtualmachineview/server/edutech-hv-2.edutech-rd.local/vmid/981389c7-3880-4794-8897-dc1fe48170fd/vmname/Edutech-RD-DC2/general Type Error Message Unable to configure either CredSSP or local PowerShell options. Error: RemoteException: You cannot call a method on a null-valued expression. Now, the two Hyper-V hosts had been disconnected from the network for quite a while during some network upgrades and were only reconnected to the network this morning, having been disconnected for 56 days. domain health is fine. we're using an admin account. not really sure what the issue is. Thanksstorage migration service not visible in windows admin centre
Hello. Wanting to evaluate Windows Server 2022 Standard, WAC and SMS. WAC is installed as a gateway on the evaluation version of Windows Server 2022. WAC version 2306 Build 1.5.2306.14001. SMS extension 2.32.0 is installed in the WAC. SMS feature is installed on the Windows Server 2022 evaluation and service is running. SMB-In firewall rule is enabled as per SMS requirements. SMS Known Issues page says this was an issue with Windows Server 2019 evaluation versions but was fixed in more recent versions of Windows Server. https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues I'm presuming that Known Issues page is wrong and SMS is still blocked for eval versions of Windows Server but thought I'd ask here in the meantime. Has anyone successfully run SMS on an evaluation version of Windows Server 2022? Thanks.No way to import shared connections WAC 2.6.4
hello, reaching out to to see if I am missing anything with the import-wacconnections change in the powershell module. Previous versions i had everything scripted and running smoothly where I could scrape AD for servers and tags and then import as shared connections for other engineers to use. Now, despite being a gateway admin, if I try and import a CSV via the windows admin center gui, I get an error that only personal connections can be imported. if I use powershell, despite providing the generated access token, I get a 403 error. my issued PKI certificate is good, I am a gateway and server admin, I even corrected the errors in the powershell module regarding $credential vs $credentials that copilot spotted Any advice or pointers to push forward?
