Forum Widgets
Latest Discussions
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?SamBaschMar 31, 2026Copper Contributor6Views0likes0CommentsHow to add a new domain controller to an existing Active Directory domain?
The specific situation is as follows: The company has one forest and domain, and two Active Directory (AD) servers. These two servers communicate and synchronize data. One server is deployed in the local data center, and the other is deployed on Azure Cloud. The forest and domain functional levels are both Windows Server 2008 R2. Both servers are running Windows Server 2016 Standard. Because there are computers running Windows XP and Windows 7 in the domain, upgrading the forest and domain functional levels is not possible. Windows Server 2008 R2 must be retained. The company now needs to add a new AD server on Huawei Cloud and join it to the company's forest and domain. The main questions are: How do I determine which operating system the new server should run? Excluding Windows Server 2016. How should I choose between Windows Server 2019, 2022, and 2025? How do I determine how to allocate CPU, memory, disk, and network resources during system deployment? How to determine which operating system is best suited for running a domain controller without conflicts or incompatibility? What preparations should be made before deploying a new server?peanut123Mar 16, 2026Copper Contributor51Views0likes1CommentGroups and roles issues
Hello, We use two user accounts, one that is a server administrator and that we use to connect to the servers via RDP (ADMaccounts). The other is not an administrator and we use it on our workstations (USRaccounts). I deleted from Gateway Users the Builtin\users group because I don't want users to access even though they can't do anything. For now I added another group as Gateway Users with our USR accounts. ADM accounts are member of Gateway Administrators. When Im logged into WAC with the ADM user and access to WAC, the browser asks me for credentials, I enter the ADM credentials, and I log in. When I am at my workstation, I access the URL and log in without being asked for credentials with the USR account session. I do not understand this behavior. I need to access from my workstation with the ADM account. How can I make the browser ask me for credentials? Do I have to open the browser with the admin credentials every time I want to manage WAC? Thanks, Best regardsPAM77Mar 06, 2026Copper Contributor20Views0likes0CommentsWAC can connect to itself or to other servers.
Hello, I have installed WAC with an internal certificate of my company. I can login to the web, the certificate appears correct in the browser. When I try to connect to the gateway itself or to other servers. No connection could be made because the target machine actively refused it: servergw.domain.com:6601 On event viewer: Event Winrest: Hosting failed to start Exception: System.InvalidOperationException: The requested certificate E=email address removed for privacy reasons could not be found in LocalMachine/My with AllowInvalid setting: False. The certificate is correct like other from company that used in other services, It has private key, and server authentication: E = email address removed for privacy reasons CN = email address removed for privacy reasons OU = company O = company bla bla L = City S = City C = Country I tried to create with other SAN: DNS=servergw.domain.com DNS=servergw DNS=localhost I have also tried to give permissions to the private key to Network Service, change the service to run with Local System. WinRM and trusted hosts are correctly. It only works when I install it with the self-signed certificate that WAC creates and it will say 60 days. What else can I try? Thanks !!PAM77Mar 06, 2026Copper Contributor105Views0likes3CommentsWindows Admin Center - Vmware migration to HyperV
We have a vCenter (multiple hosts) with about 30 VMs and need to migrate them to a single HyperV host. I installed the Windows Admin Center and the other components (https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/migrate-vmware-to-hyper-v). I migrated 2 servers, one at a time, and both seemed to work, though I had to set the IP manually. I then chose 2 servers to migrate both at the same time and it seems to be hung. The sync process completed successfully. The migration process for both got to 25% and has been stuck there for a day now. The disks aren't that big and, presumably most of that was created/copied during the sync process. I also don't see an option to stop the process or restart it. I know the VM Conversion is a Preview function, so I'm sure support it limited. Any help or direction would be appreciated.bobtimmons1Mar 02, 2026Copper Contributor596Views1like4CommentsMandatory AccessKey parameter for Import-WACConnection Powershell cmdlet in 2410
Hello, I have recently updated to Admin Center 2410, needed to do a fresh install because I ran into some Ajax error 500 problems when I dried to updrade the existing installation. Now I had a script running one a week which fetched all AD computers and Clusters and imported them as shared connection. I have already figured that I need to use a different path to import the Microsoft.WindowsAdminCenter.ConnectionTools module, and that the syntax for Import-Connection is now Import-WACConnection. However, when trying to connect, the commandlet now has a mandatory AccessKey parameter. The help suggests: "-AccessKey <String> The access key to the endpoint for form login. The access key can be created from Advanced menu of Settings on Windows Admin Center UI." However, I cannot find that option in the UI, there is only "Advanced" in the Development section of the UI, and there is no option for generating an access key. P.S. I have installed WAC to use Kerberos integrated Windows Authentication. In the past, the Import-Connection CMDlet was also just using the credentials of the currently logged-on user. Thank you for your help, MarcMa-PoFeb 23, 2026Copper Contributor1.6KViews0likes15CommentsWindows Admin Center 2410: cannot add computers
After a fresh installation of Windows Admin Center 2410, I cannot add any servers, clusters, PCs etc. WAC gives me "You can add this computer to your list of connections, but we can't confirm it's available" when I enter a computer name (either of FQDN or computer name alone). When I change to the Search Active Directory tab, I get: "We can’t search Active Directory because the Windows Admin Center computer isn’t joined to an Active Directory domain. It’s also possible that your account doesn’t have permission to read from Active Directory." The account I use is a domain admin, and the server running WAC is definitely joined to the AD DS. The server had the previous version of WAC installed where everything worked. Now, with the new version, that's no longer the case...ahinterlFeb 11, 2026Brass Contributor10KViews11likes22CommentsModernized 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.robcoFeb 05, 2026Copper Contributor54Views0likes0Comments
Tags
- Windows Admin Center39 Topics
- WAC33 Topics
- Storage Migration Service12 Topics
- Admin Center8 Topics
- Active Directory8 Topics
- windows server8 Topics
- Group Policy5 Topics
- Error5 Topics
- azure4 Topics
- general3 Topics