Windows RDS – “The security identifer could not be resolved” on multiple domains


To totally unlock this section you need to Log-in


Login

Scenario

You’ve successfully deployed a new Windows Server 2012 R2 Remote Desktop Services farm in your environment and have begun assigning permissions to users located in another forest that you are forest trust with:

Windows RDS - "The security identifer could not be resolved" on multiple domains

While you are able to browse the domain in the separate forest and select a user or group, you quickly notice you receive the following error message when you attempt to apply the settings:

The security identifier could not be resolved. Ensure that a two-way trust exists for the domain of the selected users.

Exception: The network path was not found.

Windows RDS - "The security identifer could not be resolved" on multiple domains

Solution

This problem could come even with a Windows Server 2008 R2 Remote Desktop Services deployment and it looks like this problem still persists in the newer Windows Server 2012 R2 version. To get around this issue, we would need to create a Domain local group in the domain where the RDS server is installed:

Windows RDS - "The security identifer could not be resolved" on multiple domains

Then proceed and add the user or group from the federated forest domain into the Domain local group:

Windows RDS - "The security identifer could not be resolved" on multiple domains

Because we can’t add a Domain local group into any other type of group such as Global or Universal in the domain, we would have to assign it directly to the RDS Collection and RemoteApp:

Windows RDS - "The security identifer could not be resolved" on multiple domains

This solution will let you to enable different users or groups of multiple domains on the same RDS Host server.