First, Introduction
RD is a Windows Server Remote Desktop service that can implement software from a client running a server. First install the software on the server, set up the apps and accounts that can be accessed remotely, and create an. rdp shortcut file, and then client opens the. rdp or opens the program using the Web. In the client's view, the virtual program is as if installed locally, but it is always a remote desktop, the disadvantage is also inherited: The smoothness is not high, the screen is lossy.
I am in the company of some employees to set up a relatively complex way to browse the Web: Client Remote Desktop Access 192.168.1.200 server--Account login-Open the browser. The 192.168.1.200 server itself is a VMware virtual machine running on top of a physical machine, so the internet is so smooth that it can't bear to look straight. Another problem is that a colleague's downloaded files are not deleted, causing the virtual machine hard drive to be constantly in full state.
When you switch to Rd, colleagues double-click a browser-like shortcut to surf the web, and the fluency is improved due to the physical machine being accessed. Browser-downloaded files can be stored locally on the client, eliminating the process of copying files from the server.
Second, the server configuration
1, the erection process slightly
Refer to: http://blog.sina.com.cn/s/blog_53e059e30100enis.html
2. Install the browser
Browser cannot install "C:\Users\ user name \appdata\local\" or client Login error
3. The browser creates an. rdp shortcut
4. Create a remote account
Third, client testing
Copy the server's. RDP (browser shortcut) to run locally
This article is from "Operation and maintenance rookie. Log" blog, declined reprint!
RD Case: Client surfing the web via server's browser