asked on Windows 2012 RDS Collection published app configuration.
We have a Windows 2012 RDS collection - 1 connection broker, 2 session hosts.
I have published an application and able to access it from RD WEB without a problem.
There are two issues:
1. When I click on the app from the RE WEB page, I see a RDP file being downloaded and I need to open it to access the app. How do I make it so that user can just click on the app and open?
2. After the app is opened, I check the drives that the app can access by clicking FILE>OPEN. I see the C drive of the web server is available to the users. How do I hide it?
Thanks,
I have published an application and able to access it from RD WEB without a problem.
There are two issues:
1. When I click on the app from the RE WEB page, I see a RDP file being downloaded and I need to open it to access the app. How do I make it so that user can just click on the app and open?
2. After the app is opened, I check the drives that the app can access by clicking FILE>OPEN. I see the C drive of the web server is available to the users. How do I hide it?
Thanks,
Windows Server 2012Citrix
Last Comment
Cliff Galiher
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
1. If that is the case, users who use the RD WEB to access the published app will end up endless number of .RDP files in their download folder, right? How could Microsoft come up with a design like that? This does not make any sense.
1) again, this is up to the browser. You are "blaming" Microsoft for something they don't control. MS used to lock down rdweb to IE and it only worked with IE and active-x enabled and you didn't "see" the .rdp file. But as IE faded, Firefox became dominant, and active-x was loathed, they were criticized.
So it was a no-win choice. Keep it IE only, and get the behavior you want, or open it up to other browsers, and accept *their* default behavior. MS chose the latter. But in So doing, they relinquished control of the behavior. This is 100% on the browser being used.
With that said, .rdp files are simple text files. You can have hundreds of thousands and never have a problem. Mountain, molehill.
So it was a no-win choice. Keep it IE only, and get the behavior you want, or open it up to other browsers, and accept *their* default behavior. MS chose the latter. But in So doing, they relinquished control of the behavior. This is 100% on the browser being used.
With that said, .rdp files are simple text files. You can have hundreds of thousands and never have a problem. Mountain, molehill.