Symantec AntiVirus Corporate Edition and Terminal Server support

Article:TECH99966  |  Created: 2002-01-30  |  Updated: 2007-01-02  |  Article URL
Article Type
Technical Solution




Symantec AntiVirus Corporate Edition supports Windows NT, 2000, and 2003 Terminal Servers. This document describes guidelines for installing Symantec AntiVirus to a Terminal Server, along with a list of known problems.


Either the client or the server component of Symantec AntiVirus can be installed on a Terminal Server. Symantec AntiVirus must be installed in Remote Administration mode (called Remote Desktop mode in Windows 2003), instead of Application Mode.

In versions of Symantec AntiVirus 10.0.x and previous, and Symantec Client Security 3.0.x and previous, operations through a Terminal session, such as installation, manual scans, and configuration, are not supported. However, starting with Symantec AntiVirus 10.1 and Symantec Client Security 3.1, these functions are supported.

In all versions, Symantec System Center will not install on a Terminal Server that is running in Application Mode. For more information, read the document Support for Symantec System Center on Terminal Services or Terminal Server.

Note: Symantec AntiVirus on a Terminal Server will protect terminal session thin clients, and terminal session clients with local hard drives that are operating on files within the session. Symantec AntiVirus on the Terminal Server will not protect file operations on a client's local hard drive. In the case of a client with a local hard drive, the client should have the Symantec AntiVirus client installed locally.

AMS2 alerts work correctly for users who are logged on to the console computer. Users who are connected through a terminal client session will not receive alerts.

Symantec AntiVirus will function on Terminal Servers in the same manner as it works on file servers, with the exception of alerting.

Installation order for Citrix Metaframe on Terminal Server
Symantec AntiVirus does not support drive remapping for Citrix Metaframe. If you plan to use Citrix Metaframe and remap your drives, then complete these tasks in the following order:
  1. Install Citrix Metaframe.
  2. Remap the drives.
  3. Install Symantec AntiVirus.

For more information on installing to Citrix Metaframe, see the document Server or client installation stops responding or fails when using Dynamic Disk and no drive C: is available.

Known problems:
  • Realtime Protection messages will not show up on remote sessions.
  • Logs cannot be forwarded from secondary to primary servers on remote sessions.
  • The Symantec AntiVirus icon and alerts will only show on the local console of the terminal server.
  • Selecting "Scan a floppy drive" from the user interface causes the floppy to be scanned before initiating the actual scan.
  • The server's floppy drive is scanned when a remote user logs off.
  • The floppy drive is scanned when Vpc32 window is opened.
  • If multiple thin client sessions run LiveUpdate, a LiveUpdate error message will appear on all but the first thin client session to initiate LiveUpdate.
  • NTFS partition issues:
    • The user must have at least Read permissions on the network share on which User Profile is located.
    • In the case of a Roaming Profile, ensure that the user has at least Change permissions.


See the following documents in the Microsoft Knowledge Base:

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices