TSAC SCRIPTING DOCUMENTATION ONLINE
Readers have asked questions about how to script certain functions into a Web-based client. The answers aren't always simple because the way you write the script determines how the Terminal Services Advanced Client (TSAC) works. I hope to address this issue in more depth in a forthcoming article or column. For the moment, though, I strongly recommend you look at the documentation you'll find via the link listed below. If you're new to scripting, the documentation might seem a bit dense. However, if you can get through the article, it will help you figure out how to write a TSAC client that does what you need it to do.
COM+ AND DCOM ERRORS USING WIN2K TERMINAL SERVICES AND CITRIX METAFRAME 1.8
After installing Citrix MetaFrame 1.8 on Windows 2000, you might see a system error event 10010 and an application error event 4097 and find that you can't administer COM+ on that machine.
Installing Citrix MetaFrame 1.8 for Win2K and using the drive-remapping feature during the MetaFrame installation causes this behavior. When MetaFrame remaps the system drive, it goes through the registry and replaces occurrences of the old drive letter with the new, remapped letter. However, the information in the COM+ catalog is omitted. One vital piece of information is the Compensating Resource Manager (CRM) log file path the COM+ system application uses. Every time the COM+ system application starts up, it tries to read its log file. Because it can't find the log file, the COM+ system logs an error and shuts down. Depending on which applications are running on the computer, the COM+ system might repeat this action a few times per minute. This behavior also makes it impossible to administer COM+ on that computer. Microsoft article Q263900 has more details about the Event Log entries and suggests that you read the Service Pack 2 (SP2) documentation for Citrix MetaFrame for Windows (version 1.8). (The section referred to is on page 27 and explains how to manually update the COM+ catalog.)
ERRORS AFTER SPECIFYING DEFAULT LICENSE SERVER
After you specify a default Terminal Services license server for Win2K, if the normal Terminal Services Licensing discovery process doesn't succeed every 6 hours, the terminal server logs a warning event (named in Microsoft article Q281258) stating that the terminal server couldn't locate a license server. According to the article, this event doesn't mean that unlicensed clients can't connect because the server running Terminal Services can't locate a license server. Even if you set a default Terminal Services license server, the event continues to be logged; so far, no fix.
HOW TO INSTALL THE FILE COPY TOOL INCLUDED WITH THE WIN2K RESOURCE KIT
The file copy tool adds file-transfer functionality to the clipboard redirection feature in Microsoft Terminal Services. This tool can be used on client computers running Win2K, Windows NT 4.0, Windows 9x, and Windows for Workgroups. Microsoft article Q244732 explains how to configure the server and client to correctly install the file copy tool.
If you use this tool, keep a couple of important caveats in mind. First, if you work with Windows for Workgroups clients, be sure to get the updated version of rdpclip.exe from Microsoft's Web site; the copy on the Resource Kit CD-ROM lacks some of the files you'll need to support Win16 clients. Second, the instructions in the article apply only to using rdpclip.exe with the RDP client that comes with Win2K, not to the TSAC.