Publish Remote Desktop to RDWeb
This article refers to the MyCloudIT Gen 2 platform, which was launched in 2015. Look for MyCloudIT Gen 3 to be launched in early 2021. Show
If you have any questions about this configuration, please contact us at .
When a user uses the Launch App link in the web application, the launcher is called and obtains the necessary credential information for the application to launch. The application is launched from the jump server. In turn, VDI displays the remote application on the user's workstation like a local application. Before application launching can occur, RDS must be configured. Configure Remote App
Home / Windows 7 With RemoteApp programs, you can use RDS to make programs on a Remote Desktop Session Host (RD Session Host) server appear as if they are running on a user 's local computer. RemoteApp program windows are shown on and integrated with a client's Desktop instead of being presented as part of a session-based virtual desktop. A RemoteApp program open on a Desktop. Using a RemoteApp program is similar to using a local application. When you implement RDS to provide access to a few applications, RemoteApp programs generally are easier for users to understand and use than session-based virtual desktops. Users can become confused when there is a session-based virtual desktop and a local Desktop. This is particularly true if the session-based virtual desktop is used in full-screen mode. [For tablet users, working with a full session-based virtual desktop can be challenging because small tablet interfaces can make it difficult to navigate the full session-based virtual desktop and start applications. RemoteApp programs launch the program directly from the tablet to simplify the connectivity process. Scenarios in which RemoteApp programs can be useful include the following:
Understanding RemoteApp programsA RemoteApp program is an application installed on an RD Session Host server. Remote Desktop Connection (RDC) and the RD Session Host use Remote Desktop Protocol (RDP) to redirect screen information for just the application instead of the full session-based virtual desktop. If a user runs multiple RemoteApp programs from the same session collection, the RemoteApp programs share the same session on the RD Session Host. RemoteApp programs include the following features:
RemoteApp programs integrate so well with the local Desktop that users may not be aware that they are running on an RD Session Host server. This enables you to integrate specific apps from an RD Session Host server with locally installed apps on a desktop computer. Installing applications on RD Session Host serversWhether you are providing session-based virtual desktops or RemoteApp programs, you need to ensure that apps are installed properly on the RD Session Host servers. Before you attempt to install the app in a production environment, you need to verify that it works properly when installed on an RD Session Host server. When you install the app on an RD Session Host server, you need to follow a specific installation process. The following are some considerations for deploying apps on RD Session Host servers:
Installing an app on an RD Session Host server is different from installing an app on a traditional desktop. RD Session Host servers operate in two modes: install mode and execute mode. You must put a server in install mode to install multiuser apps properly. In install mode, the Windows operating system ensures that appropriate registry entries and initialization (.ini) file settings are configured for an app to function in multiuser environments. After an app successfully installs, the server must be placed back into execute mode. The Windows Installer Service is RDS-aware. This means that Windows Installer packaged apps (.msi) automatically are installed properly. Windows Installer switches to install mode and back to execute mode as part of the installation process. Most apps are distributed as Windows Installer packages as for installation, but you should verify before installing. If the app isn't distributed as a Windows Installer package, then you need to ensure that you install it by using the proper process. One way to install the application properly is by using the Install Application On Remote Desktop Server option in the Programs area of Control Panel. This option is added to all RD Session Host servers. Using this option opens a wizard that prompts you for the location of the installation files and puts the server into install mode while performing the installation. Alternatively, you can use a command prompt to manually put the RD Session Host server into install mode by using the following command: change user /installAfter the RD Session Host server is switched to install mode, install the application. Then, change the RD Session Host server back to execute mode by using the following command: change user /executeYou also can check the current server mode by using the following command: change user /queryYou also can use apps deployed by using Microsoft Application Virtualization (App-V) for sessionbased virtual desktops and RemoteApp programs. Using App-V can mitigate some compatibility issues and simplify application deployment and updates. Publishing RemoteApp programsBefore users can access RemoteApp programs, you must publish them. Publishing configures a session collection with the information necessary for users to access the apps on the RD Session Host servers. To publish a RemoteApp program from a session collection, perform the following steps:
Note: Configuring RemoteApp programsAfter you publish a RemoteApp program, it appears in the RemoteApp Programs area. In this area, you can see the name of the program and whether it is visible in RD Web Access. To configure a RemoteApp program, right-click the RemoteApp program and click Edit Properties. In the properties of a RemoteApp program, on the General page, you can change the RemoteApp Program Name. This value controls the name that is visible in RD Web Access for the application. You also can choose whether to Show The RemoteApp Program In RD Web Access. You can organize applications in RD Web Access by entering a folder name in the RemoteApp Program Folder box. Any folder name that you enter is used to generate a folder in RD Web Access in which the RemoteApp program appears. After you have entered a folder name for one RemoteApp program, it is available in the drop-down list when you edit other RemoteApp programs. This makes it easier to organize the applications in consistent folder names. The Parameters page has settings that control which command-line parameters can be passed to the application at startup. The options are as follows:
The User Assignment page, allows you to control which users have access to the RemoteApp program. By default, all users and groups that have access to the collection have access to a RemoteApp program in that collection. If you choose to give specific users and groups access to the RemoteApp program, then the allowed users must be given access to the collection and the RemoteApp program. The File Type Associations page, is used to define file associations that can be configured for the RemoteApp program. If you select a file type here, then clients with access to this RemoteApp program automatically launch the RemoteApp program when they double-click a file with that extension. For example, if the WordPad RemoteApp program is associated with the .docx file type, then the WordPad RemoteApp program will be launched to edit any .docx file that is opened. FTAs for RemoteApp programs only work when the client is using RemoteApp and Desktop Connections, which integrates with the Windows clients. Windows PowerShell cmdlets for RemoteApp programsAs for other parts of RDS, there are Windows PowerShell cmdlets for creating and configuring RemoteApp programs. To get a list of Windows PowerShell cmdlets for RemoteApp programs, run the follow command: |