Home

RDS RemoteApp and Desktop Connections

%3CLINGO-SUB%20id%3D%22lingo-sub-90168%22%20slang%3D%22en-US%22%3ERDS%20RemoteApp%20and%20Desktop%20Connections%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90168%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20reference%20to%20RDS%202016%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20using%20RDS%20RemoteApp%20and%20Desktop%20Connections%20I%20know%20that%20if%20you%20use%20Group%20Policy%20to%20create%20the%20connection%20it%20becomes%20the%20%22Default%22%20connection%20which%20then%20allows%20file%20type%20associations%20to%20pass%20through%20with%20Remote%20Apps.%20You%20cannot%20however%20use%20Group%20Policy%20to%20establish%20%22Default%22%20connections%20on%20computers%20that%20are%20part%20of%20the%20RDS%20deployment%20(specifically%20an%20RDSH%20server).%20%26nbsp%3BWhen%20you%20look%20in%20the%20event%20log%20after%20configuring%20the%20Group%20Policy%20to%20create%20the%20%22Default%22%20connection%20you%20see%20a%20message%20that%20the%20policy%20cannot%20be%20applied%20because%20the%20computer%20is%20a%20member%20of%20the%20RDS%20Deployment.%20%26nbsp%3BDoes%20anyone%20know%20why%20this%20functionality%20can't%20be%20used%20within%20the%20RDS%20deployment%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20isn't%20really%20troubleshooting%20why%20it%20doesn't%20work%20it%20is%20more%20to%20understand%20the%20Technical%20Limitation%2FDesign%20decision.%20%26nbsp%3BI'm%20curious%20as%20RDS%20moves%20forward%20if%20this%20is%20a%20hurdle%20that%20can%20and%20will%20be%20overcome%20or%20if%20it%20is%20something%20I%20need%20to%20stop%20thinking%20about%20because%20it%20can't%20be%20done%20for%20some%20reason.%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20ideal%20setup%20is%20to%20stream%20my%20applications%20from%20a%20collection%20of%20RemoteApp%20servers%20over%20to%20a%20collection%20of%20RDSH%20servers%20to%20control%20application%20access.%20Ideally%20users%20should%20be%20able%20to%20click%20on%20a%20file%20in%20their%20documents%20folder%26nbsp%3Band%20have%20it%20open%20via%20a%20streaming%20app.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20any%20insights%2C%3C%2FP%3E%3CP%3EDave%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-90168%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
drukamp
New Contributor

In reference to RDS 2016

 

When using RDS RemoteApp and Desktop Connections I know that if you use Group Policy to create the connection it becomes the "Default" connection which then allows file type associations to pass through with Remote Apps. You cannot however use Group Policy to establish "Default" connections on computers that are part of the RDS deployment (specifically an RDSH server).  When you look in the event log after configuring the Group Policy to create the "Default" connection you see a message that the policy cannot be applied because the computer is a member of the RDS Deployment.  Does anyone know why this functionality can't be used within the RDS deployment?

 

My question isn't really troubleshooting why it doesn't work it is more to understand the Technical Limitation/Design decision.  I'm curious as RDS moves forward if this is a hurdle that can and will be overcome or if it is something I need to stop thinking about because it can't be done for some reason.

  

My ideal setup is to stream my applications from a collection of RemoteApp servers over to a collection of RDSH servers to control application access. Ideally users should be able to click on a file in their documents folder and have it open via a streaming app.

 

Thanks for any insights,

Dave

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies