Forum Discussion
Error when trying to add AD group to Gateway Access
Windows Admin Center version: 2.4.0 is running on a fully updated Server 2022 platform. WAC is up to date. I am accessing our WAC instance directly on the server that is hosting it.
When I attempt to add an AD group using the format domain\group_name to the Gateway Users group, I receive the following error.
Error: System.DirectoryServices.Protocols is not supported on this platform.
Prior to upgrading to V2, this was not a problem as there are some domain groups already in place. For implementing RBAC, we kind of need this feature.
4 Replies
I have this same problem, and we are deploying multiple new Dell Apex Azure Local clusters that require v2. I also have problems with both the new Dell extensions
Thank you for the reply.
As we are a test environment, WAC is not a critical component at this time. Yesterday, I reloaded Windows Server Standard 2022 fully updated it. I also downloaded the install of WAC V2 (not the upgrade) and installed it from scratch. It is also fully updated.
WAC does talk to AD as it was able to find and install servers without a hitch. I just need to get my users to be able to manage Hyper-V VMs.
So, still working through tweaks. Worst case, I open a case with M$oft. I did that with V1 RBAC issues and got an outstanding engineer to assist.
Thanks for the update! It sounds like you're making some progress. Sometimes it is hard to reply specific scenarios. If you end up opening a case with Microsoft, I hope they’re as helpful as last time.
I’ve encountered this issue once before after upgrading Windows Admin Center. It seems that the error happens because certain components, like System.DirectoryServices.Protocols, aren't fully compatible or supported in the latest version on Server 2022. To try to resolve it, I recommend you checking if all related Windows features and roles for AD and remote access are properly installed. Sometimes, a fresh install or repair of the WAC components may help resolve compatibility issues. Also you should verify that all relevant updates and patches for both the OS and WAC are fully applied. If the issue persists, you can also manage the group memberships directly through Active Directory or PowerShell, at least until a fix is available.
Hope it helps!
