To clarify do you mean you were unable to use "cd RDS:\"? If so, you need to run the following before this:
Import-Module RemoteDesktopServices
Now you should be able to use "cd RDS:\".
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi there,
We are trying to get off of NTLM for our entire Domain and the last tricky spot seems to be our RDS implementation.
When we Restrict NTLM and set it to Deny All we RDS breaks. From looking at this old post (https://techcommunity.microsoft.com/t5/security-compliance-and-identity/creating-kerberos-identity-for-rd-session-host-farms-part-i/ba-p/246775) it seems like I need user Powershell to create a Kerberos identity for the deployment but I can't get past step 2. This makes me think that I'm either doing something wrong or the process has changed and I can't figure out what.
Does anyone have any ideas or directions you can point me in?
To clarify do you mean you were unable to use "cd RDS:\"? If so, you need to run the following before this:
Import-Module RemoteDesktopServices
Now you should be able to use "cd RDS:\".
I have an similar issue at Step 3. "RDSFarms" doesn't exists. Only "LicenseServer" is available.
But Im definitely connected on my Connection Broker (the affected Server is License Server and Connection Broker at once).
Have anyone an idea, how can I fix this?