Remote Desktop Service Web access is a great feature that administrators can use to publish hosted applications for users around the world.
With it, you only need a browser to log on to the port, and the Windows version supports Remote Desktop client software Vista and later Windows, windows XP also has a dedicated client) so that they can access terminal service-hosted applications from anywhere.
For some advanced users, you can use group policies to customize applications that can be accessed within the scope of user permissions and perform more detailed control. When users access ports in the enterprise network, different users will display different applications based on their permissions.
To create a port for Web access to the remote desktop service, you must meet the following requirements:
The role that installs the remote desktop service.
Only Windows Server 2008 R2 can be used as the Server with the remote desktop access port.
There must be a Server running the Remote Desktop Session host and Remote Desktop Connection proxy roles, both of which are installed through the Server Manager of Windows Server 2008.
Remote Desktop Web access role Service Installation
First, deploy the correct code on the server that hosts the portal. To install the Remote Desktop Web access role service, follow these steps:
1. log on to the server with the Remote Desktop Web access port as an administrator.
2. Click Start> Administrative Tools> Server Manager.
3. In the "role overview" section, click "add role" and click "Next" on the wizard introduction page ".
4. Select the remote desktop service role, click "Next", and click "Next" on the Remote Desktop Service Page ".
5. Select the Remote Desktop Web access role service. In the dialog box, click "install required role services" and click "Next ".
6. On the Web server IIS page, click "Next" and click "Next" on the select role Service Page ".
7. On the confirm installation selection page, click "Install ".
Now that the Remote Desktop Web access port is ready, the only thing that is missing is the application it hosts. They can be Remote Desktop Connection proxy, remote desktop session server, or server farm. You also need to add the Remote Desktop Web Access Server to the TS Web Access Computers Security Group of the Remote Desktop Session host server. Of course, this is easy to do:
1. log on to the https: // <server_fqdn>/rdweb Remote Desktop Web Access Service site as an administrator ).
2. Select the "configuration" page.
3. Select "Remote Desktop Connection proxy" or "one or more RemoteApp sources ". Specify the address and click OK to save the changes.
Configure RemoteApp and Desktop Connection Properties
In this case, you need to configure the properties of the Remote Application on the connection proxy server. It allows the web access server and the server hosting the remote desktop service to communicate with each other and exchange connection and session information.
1. on the Remote Desktop Connection proxy server, click Start> Administrative Tools> Remote Desktop Services> Remote Desktop Connection Manager ".
2. Click the node on the top of the panel on the left of the interface, and then click "properties" on the right panel ".
3. Define the display name and connection ID on the connection settings tab.
4. navigate to the Remote Desktop Web Access tab and enter the complete DNS address for the Remote Desktop Web access server in the server name text box.
5. Click "add", click "application", and click "OK ".
Add corresponding applications to the RemoteApp list
The last step is to add an application to the accessed user. This process is quite simple:
1. on the Session host, click Start> Administrative Tools> Remote Desktop Services> RemoteApp manager ".
2. on the Operation Panel, click "add RemoteApp" and click "Next" on the wizard introduction page ".
3. Select the programs to be added to RemoteApps from the list. The dialog box displays all entries in the Start Menu folder of all users. You can also click the Browse button to specify applications on the disk.
4. Click "Next" to view the settings, and then click "finish ".
After everything is done, users can access the portal. They can click the icon of the application to be run, and their sessions and connections will be automatically established. The application runs on the server. This is a controlled environment. User data is only stored on the internal network of the enterprise, and the client is only responsible for presenting images.