|
Working With Terminal Services Remote Applications (Part 5) |
|
Thursday, 25 June 2009
by Michel Roth
|
|
Working With Terminal Services Remote Applications (Part 5)
This article concludes the series on Terminal Services Remote
Applications by explaining how to create traditional Windows
Installer packages for remote applications. Back in Part 3 of this
article series, I showed you how to create an .RDP file that you
could use to connect a client computer to a remote application.
Although this technique works pretty well, it is not entirely
seamless. The user can take one look at the application’s
icon and tell that the application is running remotely. The fact
that remote applications use a different icon than applications
that are running locally might not seem like a big deal, but I have
worked in IT long enough to know that some users will absolutely
lose their minds if they come in one day and the icon for Microsoft
Word has been replaced by an unfamiliar looking icon. If you start
deploying remote applications that are accessible to users through
.RDP files, you will probably see a spike in help desk calls
immediately after the deployment is complete, but the volume of
helpdesk calls should soon go back to normal. Even so, there is
another down side to using .RDP files to connect users to remote
applications. .RDP files are not always as easy to deploy as
traditional applications. Fortunately, there is a solution.
Microsoft has designed Terminal Services RemoteApp so that you can
create Windows Installer packages (.MSI files) for remote
applications.
Source: http://www.msterminalservices.org/articles/Working-Terminal-Services-Remote-Applications-Part5.html
|
