Best Practices in Delivering Applications with Server 2008's Terminal Services: What Works and What Won't
You probably already know that Terminal Services in Windows Server 2008 is a whole new ballgame. The introduction of individual application publishing in addition to traditional full desktops means you can now deploy only a single application to your users. This new feature alone provides you added flexibility for deploying apps, while at the same time reducing your requirement for complicated desktop lockdowns. You also stand to see performance gains and improved security as you isolate your users to just the apps they need.
But with this change you now have added options for getting users to their needed applications. Some will make sense for your environment, while others can actually reduce your users experience instead of improving it.
Dial into this important webcast to learn about the new ways of deploying Terminal Services-hosted apps to your users. You'll learn about TS Web Access versus local desktop installation. You'll discover how file extension modifications can mean a seamless experience for your users. In the end, you'll leave with best possible ways to deploy apps that make sense for your IT environment.