by Greg Shields

The last step in this process comes only if you plan to “install” your RDP files to desktops and laptops around your environment. By wrapping a RemoteApp into an MSI file, it is possible to distribute that RemoteApp’s connection to the various computers in your environment using a software deployment mechanism such as Group Policy Software Installation, System Center Configuration Manager, or System Center Essentials. Doing so enables you to create easy-to-use icons on users’ desktops or in their Start Menus for launching applications.

You can further integrate the RemoteApp into your desktops’ explorer shell by re-associating the file extensions for documents that relate to the RemoteApp’s application. For example, if you publish Microsoft Word, this process can re-associate the .DOCX extension to launch the RemoteApp rather than any local installation of the software. Doing so enables your users to double-click documents to have them automatically and seamlessly launch in the RemoteApp.

This integration obviously has some benefits to your users’ workflow. They don’t have to navigate to a separate page to access their apps; the apps are right there in the Start Menu or accessed through a double-click. Launching a RemoteApp involves the exact same process as launching a local app.

Yet at the same time, these applications become installed to the desktop. That means that your job in ensuring the availability of the application goes up. If that application for some reason goes down, users will get some very interesting error messages. Further, if you plan to change the application in the future, you’ll also need to update the installation on your users’ desktops.

To create an MSI file out of an existing RemoteApp, navigate back to the TS RemoteApp Manager, select the application, and click the link for Create Windows Installer Package. A wizard that looks very similar to the Create .rdp File wizard will appear, with the same settings to be modified in its first screen. This wizard adds a second configuration screen that provides configuration control over which shortcuts are created (desktop versus Start Menu folder) as well as whether you want to re-associate your document extensions. Clicking Next, then Finish creates the MSI file, which must then be deployed through one of the software deployment mechanisms discussed earlier.

Care must be taken to determine whether this mechanism is a good idea for your environment. If you plan for a high rate of application change in your environment, this mechanism will require more administrative overhead in changing the installed apps. But if your environment and available application suite is relatively static, this can be a boon to you and your users’ workflow.

About the Author

Greg Shields is an independent author, speaker, and IT consultant, as well as a Partner and Principal Technologist with Concentrated Technology. With 15 years in information technology, Greg has developed extensive experience in systems administration, engineering, and architecture specializing in Microsoft OS, remote application, systems management, and virtualization technologies. He is a Contributing Editor and columnist for TechNet Magazine and Redmond Magazine, and serves as the Series Editor for Realtime Publishers, the world’s leading provider of high-quality content for the IT market. Greg is a highly sought-after and top-ranked speaker for both live and recorded events, and is seen regularly at conferences like TechMentor Events, Microsoft Tech Ed, VMworld, and more. He is a multiple recipient of Microsoft “Most Valuable Professional” award.