by
Brian Madden
I can think of no better way to kick off our BriForum 2005 video series than with this video. The attendee feedback from this session was generally something like, "best session I have ever seen at any trade show ever."
In this session, Rick Mack does a great job of explaining (in everyday terms) how you can use basic tools to understand how applications work (or don't work) in Terminal Server environments.
Rick talks about the unique aspects of a terminal server environment that affect an application's security, resource utilization, graphics utilization, and installation. He talks about common application problems and how to identify them. Rick then shows you what applications you need in your basic application toolkit and touches on how you should use each tool. Finally, he closes with a bit on application virtualization.
Download the video of this session (WMV format - 59MB)
Download the audio from this session (MP3 format - 13MB)
Download the PowerPoint slides from this session (2.4MB)
Rick's Application Toolkit
After you watch the video, you'll most likely want to download the free tools that Rick talks about to help you make your sticky applications work in your terminal server or Citrix environments. Here are the essential tools that Rick recommends:
Windows Application Compatibility Toolkit (Download the toolkit) (Here's a video from Microsoft that explains this in more detail.)
- Application verifier 2.5
- Compatibility Administrator
Sysinternals tools (www.sysinternals.com)
- NT registry Monitor
- NT file system monitor
- Process Explorer
- Listdlls
Windbg (Windows Debugger from Microsoft)
Resource Hacker (http://www.users.on.net/johnson/resourcehacker/)
Commandbar Controls Browser (http://www.siam-consulting.com/download/CmdBarBrowser.exe)
Microsoft Windows Installer SDK
CMPTMAN
Patience
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.