Line One
asked on
Windows 2008 R2 - Remote App - making it available through an RDP link
I have taken the following from the following link:
ttp://technet.microsoft.co m/en-us/li brary/cc73 0673(WS.10 ).aspx
++++++++++++
Create an .rdp file from a RemoteApp program
You can use the RemoteApp Wizard to create an .rdp file from any program in the RemoteApp Programs list.
To create an .rdp file
Start TS RemoteApp Manager. To do this, click Start, point to Administrative Tools, point to Terminal Services, and then click TS RemoteApp Manager.
In the RemoteApp Programs list, click the program that you want to create an .rdp file for. To select multiple programs, press and hold the CTRL key when you click each program name.
In the Actions pane for the program or selected programs, click Create .rdp file.
Note
If you selected multiple programs, the settings described in the rest of this procedure apply to all of the selected programs. A separate .rdp file is created for each program.
On the Welcome to the Remote App Wizard page, click Next.
On the Specify Package Settings page, do the following:
In the Enter the location to save the packages box, accept the default location or click Browse to specify a new location to save the .rdp file.
In the Terminal server settings area, click Change to modify the terminal server or farm name, the RDP port number, and the Require server authentication setting. (For more information about these settings, see Configure terminal server settings.) When you are finished, click OK.
In the TS Gateway settings area, click Change to modify or to configure whether clients will use a TS Gateway server to connect to the target terminal server across a firewall. (For more information about these settings, see Configure TS Gateway settings.) When you are finished, click OK.
Note
For more information about TS Gateway, see the TS Gateway Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=85872).
To digitally sign the .rdp file, in the Certificate Settings section, click Change to select or to change the certificate to use. Select the certificate that you want to use, and then click OK. (For more information about these settings, see Configure digital signature settings (optional).)
When you are finished, click Next.
On the Review Settings page, click Finish.
When the wizard is finished, the folder where the .rdp file was saved opens in a new window. You can confirm that the .rdp file was created.
+++
Questions:
1) It seems if I use TS Web Access to 'publish' apps per earlier sections of the above document, I need XP SP3. Do I need XP SP3 if I use the RDP method outlined above?
2) Also after I've created the RDP link, how do I distribute it to the clients? That's not clear here.
a) Do I copy the various RDP files that get created - one for each app - to each user's desktop? If so will they have appropriate names e.g. Office? Adobe?
or
b) Do I make shortcuts on everybody'd desktop and name them appropriately e.g. Office, Adobe - and point them to the specific RDP files that were created in the process outlined above?
3) If there is any choice I want it so that I can manage centrally what shows up on different people's desktops - I don't want to go to each desktop and customize separately? Can I distribute and manage RDP apps from a singe point?
ttp://technet.microsoft.co
++++++++++++
Create an .rdp file from a RemoteApp program
You can use the RemoteApp Wizard to create an .rdp file from any program in the RemoteApp Programs list.
To create an .rdp file
Start TS RemoteApp Manager. To do this, click Start, point to Administrative Tools, point to Terminal Services, and then click TS RemoteApp Manager.
In the RemoteApp Programs list, click the program that you want to create an .rdp file for. To select multiple programs, press and hold the CTRL key when you click each program name.
In the Actions pane for the program or selected programs, click Create .rdp file.
Note
If you selected multiple programs, the settings described in the rest of this procedure apply to all of the selected programs. A separate .rdp file is created for each program.
On the Welcome to the Remote App Wizard page, click Next.
On the Specify Package Settings page, do the following:
In the Enter the location to save the packages box, accept the default location or click Browse to specify a new location to save the .rdp file.
In the Terminal server settings area, click Change to modify the terminal server or farm name, the RDP port number, and the Require server authentication setting. (For more information about these settings, see Configure terminal server settings.) When you are finished, click OK.
In the TS Gateway settings area, click Change to modify or to configure whether clients will use a TS Gateway server to connect to the target terminal server across a firewall. (For more information about these settings, see Configure TS Gateway settings.) When you are finished, click OK.
Note
For more information about TS Gateway, see the TS Gateway Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=85872).
To digitally sign the .rdp file, in the Certificate Settings section, click Change to select or to change the certificate to use. Select the certificate that you want to use, and then click OK. (For more information about these settings, see Configure digital signature settings (optional).)
When you are finished, click Next.
On the Review Settings page, click Finish.
When the wizard is finished, the folder where the .rdp file was saved opens in a new window. You can confirm that the .rdp file was created.
+++
Questions:
1) It seems if I use TS Web Access to 'publish' apps per earlier sections of the above document, I need XP SP3. Do I need XP SP3 if I use the RDP method outlined above?
2) Also after I've created the RDP link, how do I distribute it to the clients? That's not clear here.
a) Do I copy the various RDP files that get created - one for each app - to each user's desktop? If so will they have appropriate names e.g. Office? Adobe?
or
b) Do I make shortcuts on everybody'd desktop and name them appropriately e.g. Office, Adobe - and point them to the specific RDP files that were created in the process outlined above?
3) If there is any choice I want it so that I can manage centrally what shows up on different people's desktops - I don't want to go to each desktop and customize separately? Can I distribute and manage RDP apps from a singe point?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's about the size of it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks. I will go through the lab. One final question/clarification before I sign off that I asked above. Is there a more elegant way of distributing the RDP file/shortcut link to individual desktops than individual manual insertion?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks I've read this article. But it doesn't actually talk about distributing the RDP file/link to multiple users in an automated fashion. It only talks about creating the original RDP file.
ASKER
Still responding?
did you read whole article ?
ASKER
I thought I did. If there's a part in there that explains how to distribute it and I missed it, please point it out for me. There's reference to putting it on a network share but then I still need the link on each desktop to that share.
ASKER
Still on this?
•via a Windows Installer (.MSI) package that can be deployed to users with GPO and will create a program icon on the user's Desktop or Start Menu
ASKER
I wrote:
" There's reference to putting it on a network share but then I still need the link on each desktop to that share."
None of the responses have answered this question. How do I get the shortcut onto everybody's desktop I don't want the MSI install, I don't want to distribute the RDP file itself, I want a shortcut to the share that has the RDP file.
" There's reference to putting it on a network share but then I still need the link on each desktop to that share."
None of the responses have answered this question. How do I get the shortcut onto everybody's desktop I don't want the MSI install, I don't want to distribute the RDP file itself, I want a shortcut to the share that has the RDP file.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the distinction. As far as the MSI goes, when a user logs on for the first time does that mean they will have to go through an install and possibly have to respond to prompts?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the tips.
kevinhsieh:
You write:
"The clients would pick the closest available server to conserve bandwidth"
I would rather not have the client 'pick' the closest server but it to be automated - based on who the client is they get the app from a specific server. How would I program that?
kevinhsieh:
You write:
"The clients would pick the closest available server to conserve bandwidth"
I would rather not have the client 'pick' the closest server but it to be automated - based on who the client is they get the app from a specific server. How would I program that?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the further clarification. I think I might have been confusing when I used the word client - I meant user. I don't want the user to somehow manually have to choose the closest file server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great. Thanks.
ASKER