Windows-Admin-Center-Ideas-and-Feedback
Windows-Admin-Center-Ideas-and-Feedback copied to clipboard
[RBAC] - RBAC users unable to fetch data or successfully connect to endpoints
Gateway Version: 1.3.2111.01001
To Reproduce Steps to reproduce the behavior:
- Apply Role Based Access to multiple machines, using this guide: https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/user-access-control#apply-role-based-access-control-to-multiple-machines
- Assign user permission of Admin Center Reader / Hyper-V Administrator / Admin Center Administrator / or amend InstallJeaFeature script to use Domain Groups
- Log into Admin Center using Admin center user assigned to groups in step 2
- Connect to endpoint to which RBAC has been deployed
- Endpoint details do not load correctly: Error The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. Try fixing any computer connection issues and refreshing the browser. We couldn't query the computer inventory data to determine the set of tools. Error: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots & Additional context
@vanniekerkjaco Do you have WDAC enabled on your server?
@prasidharora No we do not have WDAC enabled
Hey @vanniekerkjaco, this build is currently not supported so please do not deploy it in production. However, we made a lot of fixes to RBAC so this may resolve your issue.
https://microsoft-my.sharepoint-df.com/:u:/p/praror/EV_E1yve_b1KvHxkpTE3_YkBGfda_SMqMVCkNibjEi6h_g?e=4IEzpg&isSPOFile=1
Thanks @trungtran-msft I'll give it a go in the lab
I'm also having this issue in my environment. I set-up RBAC on a target server and add a user account to it. When trying to connect to the server It fails 99% of the time with the following errors:
- Exception: This operation was blocked by role based access control settings
- The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. When it works, it asks for credentials upon connecting to the server Gateway Version: 1.3.53858.0