Export (0) Print
Expand All

Checklist: Making RemoteApp Programs Available Through Remote Desktop Web Access

Published: March 2, 2011

Updated: March 2, 2011

Applies To: Windows Server 2008 R2

This parent checklist includes cross-reference links to important concepts about the design to configure RD Web Access to make RemoteApp programs available through RemoteApp and Desktop Connection. It also contains links to subordinate checklists that will help you complete the tasks that are required to implement this design.

noteNote
Complete the tasks in this checklist in order. When a reference link takes you to a procedure, return to this topic after you complete the steps in that procedure so that you can proceed with the remaining tasks in this checklist.

Checklist Checklist: Make RemoteApp Programs Available Through Remote Desktop Web Access

 

  Task Reference
Checkbox

Before you can make RemoteApp programs available to users through RD Web Access, you must complete installation prerequisites.

Checklist topic Checklist: Deploying Application Virtualization

Checkbox

Enable RemoteApp programs for RD Web Access.

Checklist topic Enabling RemoteApp Programs for Remote Desktop Web Access

Checkbox

Install the RD Web Access role service on the server that you want users to connect to over the Web to access RemoteApp programs.

Checklist topic Installing the Remote Desktop Web Access Role Service

Checkbox

Add the computer account of the RD Web Access server to the TS Web Access Computers group on the RD Session Host server.

Checklist topic Populating the TS Web Access Computers Security Group

Checkbox

Specify the source that provides the RemoteApp programs that will be available through RemoteApp and Desktop Connection.

Checklist topic Configuring the RD Web Access Server for RemoteApp and Desktop Connection

Checkbox

Make the RD Web Access Web site available from the Internet.

Checklist topic Checklist: Making RemoteApp Programs Available from the Internet

ImportantImportant
The RD Web Access Web site is automatically configured to use Secure Sockets Layer (SSL) with a self-signed certificate. By default, the self-signed certificate is not a trusted certificate, and self-signed certificates are recommended only for testing and evaluation purposes.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft