Windows Admin Center version 2110.2 generally available!
With version 2110.2, you'll find: Support for HTTP Strict Transport Security (HSTS) The ability to specify session duration time and also require manage-as sessions to reauthenticate after a set time. Bug fixes Extension updates Read Windows Admin Center version 2110.2 is now generally available! for full details.
[msft.sme.remote-desktop v4.30.2] RDP extension fails to load in WAC 2.4.1
Description Product: Windows Admin Center v2.4.1 Extension: Connect to a server or PC via Remote Desktop ID: msft.sme.remote-desktop Version: 4.30.2 Authors: Microsoft License: MIT Issue: When attempting to launch the Remote Desktop extension, the UI never renders (infinite spinner) and the browser console reports: Uncaught SyntaxError: Unexpected token '<' In addition, certain .js module requests return HTTP 403, and the loader falls back to “null” instead of the correct main.<hash>.js. Steps to Reproduce: Install or enable the msft.sme.remote-desktop extension (v4.30.2) on WAC 2.4.1. Open WAC in a modern browser and navigate to Remote Desktop. Press F12 → Console and Network tabs. Observe: The <base href="/modules/msft.sme.remote-desktop/"> page loads, but subsequent scripts (main.<hash>.js) resolve to “null” or return 403. Console errors Unexpected token '<' Remote Desktop never initializes. Expected Behavior: The RDP extension UI should load normally, register its translation tables, and allow launching a remote session without syntax or module‐loading errors. Impact: Cannot use the built-in Remote Desktop tool within Windows Admin Center. Work-around: deinstalling the remote desktop v4.30.2 and reinstalling the old version v4.26.0 until the problem is resolved in the newer versionWAC Future
I'm curious what the future of Windows Admin Center is? Looking at some of the extensions like Active Directory, DNS, and DHCP you don't get a lot of feature parity with their MMC counterparts. With Linux available in just about every environment, will there every be in the future a way to manage them inside of the admin center? Will be the best way to manage this is through Azure instead of the On-Premises Windows Admin Center. Thanks.
Windows Admin Center 2110 - Storage Migration Service (Missing Start Transfer button)
Hi guys, testing out Storage Migration Service on the latest Windows Admin Center version 2110. At the transfer phase, somehow the Start Transfer button to start the migration is missing. Anyone else facing this? All validation is passed and tested on a few different VMs and its still showing the same. Is this a bug, or am i missing something? Refer to the picture.Deploy and Install Windows Admin Center in an Azure VM
The great thing about Windows Admin Center (WAC) you manage every Windows Server doesn't matter where it is running. You can manage Windows Servers on-prem, in Azure or running at other cloud providers. Now if you want to use Windows Admin Center to manage your virtual machines running in Azure, you can use either an on-prem WAC installation and connecting it using a public IP address or a VPN connection, or you can deploy and install Windows Admin Center in Azure. This blog post will show you how you can deploy and install Windows Admin Center in an Azure virtual machine (VM). Check out my blog post to read more: https://www.thomasmaurer.ch/2019/10/deploy-and-install-windows-admin-center-in-an-azure-vm/
Getting error when trying to manage local pc with windows admin center
I just installed the 1910 version of windows admin center on my windows 10 pro pc. Whenever I click on connect i get the error of: Connection error Connecting to remote server gaming-laptop failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. I an unsure what to do at this point, any help would be greatly appreciated.
