Forum Widgets
Latest Discussions
Language Bug
I'd like to report a bug between WS2025 (english version not affected) and WAC. I tried to download Windows Server 2025 evaluation Italian version from https://www.microsoft.com/en-us/evalcenter/download-windows-server-2025?msockid=1c4d54ba113b6b020d1942b710e66a95, I installed all the updates, installed WAC App, present in start (but also by downloading from the website) once the procedure was completed the WAC website opens in Edge but the "Sign in" button does not send any command. there is a problem translating a command because it is accented
How to managed Active Directory using Windows Admin Center
Hello, Can I manage Active Directory using Windows Admin Center ? If yes, please provide the link to give me the documentation on the same. I can see that the Active Directory extension is in preview stage: https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/manage-servers#active-directory-preview but this document is dated 2019. Any help on the above mentioned is appreciated. Thanks Sushanth Amin
Using Active Directory Extension on Member Server
Hello WAC fellows, Is it possible to use the Active Directory extension on Member Server (with RSAT-AD-Tools installed) instead of connecting directly to a Domain Controller? I'd like to let users do certain tasks using an AD-Frontend of WAC, but I don't want to give them any kind of permission on the Domain Controllers. Ideally they would connectto a Management-Server using WAC and edit the AD using the AD-Extension. Any ideas?
SSO for PowerShell in WAC
So we have WAC setup working with Delegated access for the servers with no login prompts, however once you attempt to load PowerShell it does prompt for creds, I take it this is by default to re-verify the creds. The problem we have is that we are transitioning to a PAM solution and will not have access to the passwords, does anyone know if there is a way to force it to use delegation or to inject the creds of the service account running WAC?
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
Modernized Gateway - WinRM over HTTPS
Hi I wanted to try the modernized gateway preview but I get the "WinRM cannot complete the operation" when trying to connect to any server imported in WAC. The same action works just fine with the 2311 version though. It's like the Modernized Gateway just ignores the "Force WinRM over HTTPS" setting. Has anyone faced the same issue ? Is there a workaround for this ? We do not want WinRM over HTTP.Unable to get Windows Admin Center v2 (2410) to work at all
So I had the old Windows Admin Center installed and working, using Windows Credentials in my domain. There were a few issues with some of the menus that just would not work like they should, but normal updates to Windows Admin Center would fix it for a little while. They release Windows Admin Center v2 and I do an install of that with the old Windows Admin Center still installed. I am able to use the existing cert and could log into Windows Admin Center and see all the machines. Though after the Windows Admin Center v2 install, always got a ajax 500 error, when trying to connect any machine with Windows Admin Center, even the local machine. This past week, uninstall Windows Admin Center off of the Windows 11 computer that I had been using, both the v2 and v1 versions of it. I then reboot and install the Windows Admin Center v2, using custom setup. Prior to this I went into certificates on the computer and requested a web server cert for this computer using the name of the computer in DNS. My AD CS provided the new cert and I installed it as a computer certificate, under personal. Afterwards I then assigned Network Service full control of the certificate. I selected that certificate during the Windows Admin Center v2 setup and selected Windows authentication, and left everything else as default. Windows Admin Center installs and I launch it, I get to the prompt for username and password from Windows, enter the correct domain credentials and it repeatedly loops through. I went 17 tries and was never able to get into Windows Admin Center. Never got anything saying that I couldn't login, just repeatedly ask for the credentials. So how do I get this blasted thing to work? Uninstall it again, install the Windows Admin Center v1 then the v2 and try and deal with the ajax 500 issue? Nuke the entire computer and install it from a fresh Windows 11 install? Or just give up and always use remote desktop to manage all the servers, which Windows Admin Center v1 helped me half avoid?