Experience the RemoteApp of Windows R2

Description This is a excerpt from some of the chapters in the SME Virtual machine Solutions encyclopedia. The book is expected to be published by the electronic industry press in early December 2009, please look forward to it! With Remote Desktop services, organizations can provide users with access to standard Windows programs on any Windows device, anytime, anywhere, over the Internet or Intranet. REMOTEAPP helps you configure programs so that users can remotely access programs through Remote Desktop Services just as end users run these programs on the local computer. These programs are called REMOTEAPP programs. Use the RemoteApp Manager to make programs installed on a Remote Desktop session host (RD session Host) server available to users as REMOTEAPP programs. The REMOTEAPP Manager is automatically installed on the computer where the RD Session Host role service is installed.

1 What is REMOTEAPP?

REMOTEAPP allows you to remotely access programs through Remote Desktop Services as if they were running on the end user's local computer. These programs are called REMOTEAPP programs. The REMOTEAPP program is integrated with the client's desktop instead of being displayed to the user in the desktop of the Remote Desktop Session host (RD session Host) server. The REMOTEAPP program runs in its own resizable window, can be dragged between multiple monitors, and has its own entry in the taskbar. If a user runs more than one REMOTEAPP program on the same RD session Host server, the RemoteApp program will share the same Remote Desktop Services session. Users can access REMOTEAPP programs in a variety of ways. Users can: ü Use Remote Desktop Web Access (RD Web Access) ü Double-click a Remote Desktop Protocol (. rdp) file that has been created and distributed by an administrator. ü On the desktop or Start menu, double-click the program icon that is created and distributed by the administrator using the Windows Installer (. msi) package. ü Double-click the file extension associated with the REMOTEAPP program. This can be configured by an administrator using the Windows Installer package. The. rdp file and the Windows Installer package contain the settings that are required to run the REMOTEAPP program. After you open the REMOTEAPP program on the local computer, users can interact with the program that is running on the RD Session Host server as if they were running locally. Why use RemoteApp? In many cases, RemoteApp can reduce complexity and reduce administrative overhead, including: Ü Branch offices, where local IT support and network bandwidth may be limited. ü The user needs remote access to the program. ü Deploy industry (LOB) programs, especially custom LOB programs. ü You do not have an environment for users to assign computers to, such as a "public desk" or "hotel-style office" workspace. ü A conflict may occur if you deploy multiple versions of a program, especially if you install multiple versions locally. Description The above information is referenced from the Windows Server R2 Help. In fact, RemoteApp is the "improvement" of Windows Terminal Services, the previous Terminal Services, the default is to publish the entire desktop "including Start menu, Resource Manager and so on", even if the user only need to run a program on the Terminal server, but also publish the entire desktop (you can modify the settings, Run only one of the specified programs). In Windows Server 2008, Microsoft extends Terminal Services, which provides more and more meaningful functionality。 Because the RDP protocol is used to access the Terminal server and use the application provided by the Terminal Server, the requirements for the workstation are low: Because all programs are running on the server side, the workstation side simply shows the results of the program that the server is running and the user's keyboard, Mouse input feedback to the server side to perform the appropriate action, the server side will run the results displayed on the workstation. Therefore, this method can be used to upgrade workstations. I test the purpose of this product, but also want to upgrade the school two low-profile room to use to run VS2008, AutoCAD 2005 and other large software. As a Terminal Services improvement, RemoteApp can interact well with the local disks and printers of the user's workstation. With RemoteApp, you have direct access to the user's disk and can use the user's printer instead of installing print drivers on both the Terminal server and the client, as in previous Terminal Services. The following will experience the RemoteApp feature in the R2 Chinese version of Windows Server.

2 Installing Remote Desktop on the server

On the Windows Server R2 server, install IIS with Remote Desktop Services, 1, as shown in Figure 2. Figure 1 Add role Diagram 2 After you add IIS to the Remote Desktop Services installation service, restart the computer.

3 Installing a program for RemoteApp

Programs that require a separate RemoteApp, the main steps are as follows: (1) in the server, go to "Control Panel → program", as shown in 3. Figure 3 Add a program (2) Click Install application on Remote Desktop server, as shown in 4. Figure 4 Insert the CD in the Remote Desktop Server installation application (3), browse to select the program to install, as shown in 5. Figure 5 Browsing selects the installer (4) to install the program in the traditional way, as shown in 6. A lite version of AutoCAD 2002 is used here. Figure 6 Installing AutoCAD (5) After Setup is complete, click the "Finish" button, as shown in 7. Figure 7 Setup completes the instructions for each program you install, repeat the steps in Figure 4~ Figure 7. (6) Install other programs later, such as Office, VC, VB, etc. Need to explain again, Windows Server R2 already does not support VC, VB and other development tools, but can also be used after installation. It is recommended to install a new version of development tools such as VS2008.

4 Add RemoteApp

When the program for RemoteApp is complete, return to Server Manager, navigate to roles → Remote Desktop Services →remoteapp Manager, and click Add RemoteApp Program on the right, as shown in 8. Figure 8 Add RemoteApp Program in the RemoteApp Wizard, in the Name list, select the RemoteApp program that you want to add, just precede "√" and 9. Figure 9 Select the program you want to add in review settings, click the Finish button, as shown in 10. Figure 10 Add program complete

5 Creating an RDP file

After you add the RemoteApp program, you can click the Create. rdp file link to create the RDP file that the client uses, as shown in 11. Figure 11 Create an. rdp file and in specify package settings, set the. rdp file to save the path, the server name, and so on, typically save the default name, as shown in 12. Figure 12 Before you create an RDP file, you copy the created RDP file to the client, and the user double-clicks the appropriate client to invoke the corresponding program on the server. In order to facilitate the use of customers, you can set the Save RDP folder in Figure 12 to share, as shown in 13. Figure 13 is set up for sharing so that these RDP files can be accessed on the client side through a network share to run the published RemoteApp program on the server.

6 Publishing a RemoteApp program to a Web page

If users think that the RDP file is "troublesome" to access through a network share, you can also publish these programs to a Web site for user browsing, which is simple, as long as you select the program you want to publish in the RemoteApp Programs list, and then click on RD Web Access display on the right. As shown in 14. Figure 14 Publishing to a Web page

7 Creating a Windows Installer package

If you want to publish the RemoteApp program to the user's Start menu, you can select the program you want to publish in the RemoteApp Programs list, and then click the Create Windows Installer package link, as shown in 15. Figure 15 Releases the MSI package published by the Windows install package, which allows you to specify a save path, which, by default, is saved in the same folder as the RDP file and can be assigned to each workstation that is joined to the domain by publishing the MSI package as Group Policy, and the published program will "attach" In the "All Programs → remote Programs" folder of the workstation, 16 is shown. Figure 16 The program published

8 Testing RemoteApp Programs on the workstation side

After that, you can test the published RemoteApp program on the workstation side. (1) When the server is not a domain server, use the NetBIOS name, you need to edit the workstation's Hosts file, resolve the server's name to the appropriate IP address. As shown in 17. Figure 17 Editing the Hosts file (2) Open IE Browser, type http://server name/rdweb,18 as shown. Figure 18 Browsing the RemoteApp Server (3) Type the server user name, password login. The user name can be a normal user, but the user needs to be added to the Remote Desktop Users group, as shown in 19. Figure 19 Login (4) See the "RemoteApp Program" and "Remote Desktop" published, as shown in 20. Figure 20 Server-published program (5) Click on a link to a program that pops up a remote desktop-like Connection Settings dialog box, as shown in 21, where you can select drives, printers, clipboard, and so on, which can run Terminal Server programs, using local resources, as shown in 21. Figure 21 Remote Desktop Client connection settings (6) Re-enter the user name, password, which is the user name and password to log on to the remote Desktop, as shown in 22. Figure 22 Type the server user name and password (7) to run the program, as shown in 23. Figure 23 running the published program where the input method is also the input method in the server, you cannot use the input method of the local workstation. (8) When you run AutoCAD 2002 on the server, save/Open the local hard disk data. where w2008ent on the F, is the client's e disk, where W2008ent is the name of the client computer, as shown in 24. Figure 24 Local Disk

9 Other tests

You can also double-click the RDP file on the server in a "shared" manner to use the published RemoteApp program, as shown in 25. Figure 25 Double-click RDP to access the published program after you run the published MSI program, which is attached to the RemoteApp program in program → remote program, as shown in 26. Figure 26 The program that the attached program runs in Figure 25, figure 26, is the same as browsing the RemoteApp "Web site" to run the program. These are not introduced.

10 Test PostScript

After a few days of simple use, the overall effect is good. In practice, it is found that directly double-clicking RDP uses the published RemoteApp program faster than using the Web site. Also, if you use a published MSI program, you skip the authentication process when you run the RemoteApp program, and the experience is better.

Experience the RemoteApp of Windows R2