Remote Desktop Services Web Access is a great feature that administrators can use to publish hosted applications to users around the world.
With it, users only need a browser to log in to the port, and the version of Windows used supports remote desktop client software (Vista and higher versions of Windows are available, Windows XP also has a dedicated client) ), they are able to access Terminal Services hosted apps from anywhere.
For some advanced users, you can customize the applications that can be accessed within the scope of user rights through Group Policy, and perform more detailed control. When users access ports in the enterprise network, different users according to them Permissions will show different applications.
To establish a remote desktop service web access port, there are several requirements to be met in advance:
●The role of installing Remote Desktop Services.
●You can only use Windows Server 2008 R2 as the server for the remote desktop access port.
● There must be a server running the roles of Remote Desktop Session Host and Remote Desktop Connection Broker, both of which are installed through the Server Manager of Windows Server 2008.
●Installation of Remote Desktop Web Access Role Service
First, deploy the correct code to the server hosting the portal. The following steps will install the Remote Desktop Web Access role service:
1. Log in to the server on the Remote Desktop Web Access port as an administrator.
2. Click Start > Administrative Tools > Server Manager.
3. In the “Character Summary” section, click the “Add Role” item and click ““Next” on the wizard introduction page.
4. Select the "Remote Desktop Services" role and click "Next" to click on the "Remote Desktop Services page" <;Next”.
5. Select “Remote Desktop Web Access& role; In the dialog prompt, click the “Install Required Role Services” button and click “Next”.
6. On the Web Server (IIS) page, click “Next", on the Select Role Services page, click “Next”.
7. On the Confirm Installation Selection page, click “Install”.
Now that the Remote Desktop Web Access port is ready, the only thing missing is the application it hosts. They can be from a Remote Desktop Connection proxy server, a remote desktop session server, or a server farm. You also need to add the Remote Desktop Web Access server to the TS Web Access Computers security group on the Remote Desktop Session Host server. Of course, this is easy to do:
1. Log in as administrator to https:///rdweb (the site of the Remote Desktop Web Access Service).
2. Select the “Configure” page.
3. Select "Remote Desktop Connection Proxy" or "One or more RemoteApp Sources". Specify the appropriate address and click “OK" to save your changes.
Configuring RemoteApp and Desktop Connection Properties
At this point, you need to configure the relevant properties for the remote application on the connection proxy server. It allows the web access server and the server hosting the remote desktop service to exchange 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&rdquo ;
2. In the panel on the left side of the interface, click on the node at the top, then click on “Properties” in the panel on the right.
3. Define the display name and connection ID in the "Connection Settings" tab.
4. Navigate to the "Remote Desktop Web Access" tab and type the full DNS address for the Remote Desktop Web Access Server in the Server Name text box.
5. Click the “Add” button, then click “Apply”, and finally “OK”.
Adding the App to the RemoteApp List
The final step is to add an app to the user you are accessing. This process is quite simple:
1. On the session host, click “Start”>“Administrative Tools>>“Remote Desktop Services>>“RemoteApp Manager&rdquo ;
2. In the operation panel, click “Add RemoteApp Program", and click “Next” in the wizard introduction page.
3. Select the program you want to add to RemoteApps from the list. The dialog box displays all the entries in the All User Start Menu folder, or you can click the “Browse” button and specify some applications that are on disk.
4. Click “Next”, view the settings, then click “Complete”.
Once everything is done, users can access the portal, they can click on the icon of the application they want to run, and their sessions and connections will be created automatically. At this point, the application runs on the server side. This is a controlled environment where the user's data is only kept on the internal network of the enterprise, and the client is only responsible for rendering the picture.
The blue screen vulnerability threatens the server operating system Windows Server 2008, which means
Although the stability of the Windows 2000/XP system based on the NT architecture has been greatly e
A popular phrase in the previous period, meat machine, in fact, if you want to control the remote co
The following is a general solution, and the registry and xp in the actual installation of win serve
Windows 2008 Server Data Security
Windows 2003 operating system acceleration 20 strokes
Four Cheats to Enhance the Security of Win2003 System
SNMP service network security in Win2003
Windows2000 weird failure two cases
How to implement network sharing restore in Win 2003
Diskless Windows 2003 Installation Guide
Windows 2003 system uses SyGate agent to access the Internet fault
Win2000 optimized full version
Several common faults in Windows Server 2003
Win2008 uses shadow copy to achieve on-demand recovery
Windows 2008 system how to cancel Ctrl+Alt+Delete key combination login
Using a USB flash drive to encrypt the system
Win7 computer management causes desktop crash resolution
How to change the boot sound of win7 system?
How to clone WindowsXP with Ghost2003
Win10 preview version 10072 custom way to add desktop icons
What file is srt in Win10 system?
Use the space bar to call the Windows 7 boot manager
What should I do if the error code 8024402F appears in the Windows update system?