Forum Widgets
Latest Discussions
WAC Extension VM Conversion: Pre-checks failed: PowerCLI is not installed
Hi, i have Windows Administration Center Version 2410 Build 2.4.2.1, i try to migrate VMware VMs to Hyper-V using WAC Extension VM Conversion and when i start sync i get this error: Pre-checks failed: PowerCLI is not installed. Please install PowerCLI and try again.. Check the logs for details. (1%) but PowerCLI is already installed with offline installation procedure because no internet connexion available in my environment, i can import vmware.powercli module in powershel but same error in WAC Than you for your help
WAC not login
Hi, i'm trying to use and understanding WAC, but i did't have fortune to installing. I try to install Windows Server core 2025 on a physical server and i install with right power sheell command WAC and the service is running, but when from a Windows 11 i try to login the button seems to not function, no error. i try to install on a virtual machine, same result, i click on login button ma no error and no login. where i mistake? thanks for supportRegister-WACLocalCredSSP: Failed to register CredSSP session configuration.
Every time when install Windows Admin Center (v2), I will get this error when installation accomplished. How to deal with it? Thanks 2025/08/17 15:34:48 Level=INFO ExitCode=0 Message=Enable-WACPSRemoting: Successfully configured PowerShell Remoting. 2025/08/17 15:34:48 Level=INFO ExitCode=0 Message=Remove-WACSelfSignedCertificate: Successfully removed self signed certificate. 2025/08/17 15:34:49 Level=INFO ExitCode=0 Message=Set-WACEndpointFqdn: Added Service FQDN to the hosts file. 2025/08/17 15:34:49 Level=INFO ExitCode=0 Message=Set-WACEndpointFqdn: Updated Endpoint and Service FQDN. 2025/08/17 15:34:52 Level=INFO ExitCode=0 Message=Copy-WACTempUpdaterProcessFiles: Successfully copied Windows Admin Center Updater process files. 2025/08/17 15:34:54 Level=INFO ExitCode=0 Message=Register-WACUpdaterScheduledTask: Successfully registered Windows Admin Center Updater scheduled task. 2025/08/17 15:34:55 Level=INFO ExitCode=0 Message=Unregister-WACService: Successfully unregistered Windows Admin Center service. 2025/08/17 15:34:55 Level=INFO ExitCode=0 Message=Register-WACService: Successfully registered Windows Admin Center service. 2025/08/17 15:34:58 Level=INFO ExitCode=0 Message=Set-WACWinRmTrustedHosts: Successfully set TrustedHosts to *. 2025/08/17 15:34:59 Level=INFO ExitCode=0 Message=Set-WACWinRmOverHttps: Successfully set WAC WinRM over HTTPS configuration. 2025/08/17 15:35:00 Level=INFO ExitCode=0 Message=Set-WACSoftwareUpdateMode: Successfully set WAC software update mode. 2025/08/17 15:35:01 Level=INFO ExitCode=0 Message=Set-WACTelemetryPrivacy: Successfully set WAC telemetry privacy mode. 2025/08/17 15:35:02 Level=INFO ExitCode=0 Message=Set-WACOperationMode: Successfully updated WAC operation mode: Production. 2025/08/17 15:35:02 Level=INFO ExitCode=0 Message=Set-WACLoginMode: Successfully set WAC login mode. 2025/08/17 15:35:03 Level=INFO ExitCode=0 Message=The certificate subject name for the front-end endpoint has been set to admin.compute.microbin.cn. 2025/08/17 15:35:03 Level=INFO ExitCode=0 Message=The certificate subject name for the service endpoint has been set to admin.compute.microbin.cn. 2025/08/17 15:35:03 Level=INFO ExitCode=0 Message=Set-WACCertificateSubjectName: Successfully set WAC certificate subject name. 2025/08/17 15:35:04 Level=INFO ExitCode=0 Message=Set-WACCertificateAcl: Successfully set WAC certificate access control list. 2025/08/17 15:35:05 Level=INFO ExitCode=0 Message=Set-WACHttpsPorts: Successfully set WAC HTTPS ports. 2025/08/17 15:35:06 Level=INFO ExitCode=0 Message=Unregister-WACAccountManagementService: Successfully unregistered Windows Admin Center Account Management service. 2025/08/17 15:35:06 Level=INFO ExitCode=0 Message=Register-WACAccountManagementService: Successfully registered Windows Admin Center Account Management service. 2025/08/17 15:35:07 Level=INFO ExitCode=0 Message=Unregister-WACFirewallRule: Successfully removed WAC firewall rule. 2025/08/17 15:35:07 Level=INFO ExitCode=0 Message=Register-WACFirewallRule: Successfully created WAC firewall rule. 2025/08/17 15:35:09 Level=ERROR ExitCode=1 Message=Register-WACLocalCredSSP: Failed to register CredSSP session configuration. 2025/08/17 15:35:13 Level=INFO ExitCode=0 Message=Initialize-WACDatabase: Successfully initialized database. 2025/08/17 15:35:14 Level=INFO ExitCode=0 Message=Import-WACExistingExtensions: No previously installed extensions to import. 2025/08/17 15:35:14 Level=INFO ExitCode=0 Message=Import-WACExistingPlugins: No previously installed plugins to import. 2025/08/17 15:35:15 Level=INFO ExitCode=0 Message=New-WACEventLog: Successfully created Windows Admin Center event log.
Uncaught SyntaxError in the Italian version of Login Page
Good morning, We've just installed the latest version of Windows Admin Center (2410) and when we try to login from the HTML form, we can't login and we get this error in console: Uncaught SyntaxError: Unexpected identifier 'accesso' (at (index):398:49) In fact, if you go to the exact line there is a syntax error due to the Italian translation of the string that adds a ' character that is not escaped. Is it possible to fix it in order to use the System language? Ty
Multiple terminal servers setup
I'm looking to replace my old (like really old 2k8 r2) terminal server with 3 new ones (win2k5). Instead of each department going to one server as it is now, I would like to break up the departments to a specific server. For example. HR and Fiscal go to server 1, C suites go to server 2, etc. How can this easily be achieved? Can I give them all the same virtual server name, group the servers together, and terminal knows which one to go to based on the users group or do I have to make 3 individual servers and tell each division to go to server1 or server2? I've thought about just grouping them together, having roaming profiles and allowing terminal to pick the server based on load but, I don't want to have to fight the terminal server vs their desktop computer when they are in the office. Not to mention the amount of storage needed for all of the profiles. Any help or suggestions would be appreciated.
The SSL certificate contains a common name (CN) that does not match the hostname.
I'm after a bit of assitance for the WAC 2025 deployed in Azure. The fundamentals are setup, and I can add standalone servers, however when I add the hyper v cluster or the nodes underneath individually, and connect, it throws up the following error. There's a self signed cert bound to the cluster listener and verified working, but it still throws the below. I'm not sure what i'm missing. The cert is also in the personal store of the local nodes with their SAN within that same certificate bound to the listener. cluster.domain.com node1.domain.com node2.domain.com Connecting to remote server name.domain.com failed with the following error message : The server certificate on the destination computer (name.domain.com: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.
Demoting 2016 server problems
I am trying to demote a Windows 2016 server and am running into errors. I am using a Domain Admin account. The error that comes up is that the domain cannot be reached which is strange, considering that all DCs are reachable from this server. It is not running a GC and the DNS server on it has been removed. This is a relatively small domain with only three DCs. We are demoting this one so that we can add a new Windows 2022 DC and eventually 2025 DCs. We have two sites: Office and Datacenter. There are two DCs at Office and one at Datacenter. Going forward we will be removing one of the office DCs and adding a second one at Datacenter. Let's call these servers: Server Alpha, 172.16.1.1, Datacenter Server Bravo, 172.17.1.1, Office (this is the server to be removed) Server Charlie, 172.17.1.2, Office When I run the command: dcdiag /test:dns /DnsRecordRegistration on each of these servers I get the following: Server Alpha: Success, no errors Server Bravo: Success, no errors Server Charlie: DNS error, points to very old IP (172.20.1.1) that Server Bravo used to have when it was at an older, DR datacenter. The error is: "PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.1.1" We do still have the reverse DNS zone for that subnet however neither of the other two servers have this problem. Also I cannot find any other entries for that IP address anywhere. What am I missing?Storage Migration Service fails at 18% from server 2016 to server 2022
Hi, we have setup a storage migration from a physical server 2016 to physical server 2022. This fails at 18%, the validation passes and transfer starts but then stops at 18% I have downloaded the "proxy admin" and "Storage migration service admin" event logs from the storage migration service in admin center.WAC over WinRM HTTPS for non-domain-joined Devices
When configuring Windows Admin Center to use WinRM over HTTPS, it's not possible to add non-domain-joined devices (such as Windows Server 2025) if UAC remote restrictions are enabled on the target machine. Adding a device using a local account with administrator permissions fails with the error "Credentials needed - Access was denied". The self-signed certificate of the remote machine is present in the trusted root store and remote PowerShell over WinRM HTTPS is also working but the only workaround is to disable remote UAC entirely which brings a security risk. GPO Computer Configuration -> Administrative Templates -> MS Security Guide -> Apply UAC restrictions to local accounts on network logons Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy = 1 Is there a way to overcome this ?
