Release Notes › Feature Support Limitations › Windows Endpoint Limitations

Windows Endpoint Limitations

This section describes feature support limitations for Windows endpoints.

x64 Feature Support Limitations

The following are known limitations on Windows 2003 x64:

• Unicenter TNG migration and integration
• Mainframe password synchronization
• Impersonation interception (class SURROGATE functionality), if SurrogateInterceptionMode is set to 1

  Important! Impersonation interception is supported on x64, IA64 and x86 platforms by default via the RunAs plug-in (SurrogateInterceptionMode is set to 0).

  Note: For more information about the SurrogateInterceptionMode registry setting, see the Reference Guide.

IA64 Feature Support Limitations

The following features are not supported on IA64 platforms:

• Unicenter TNG migration and integration
• Mainframe password synchronization
• STOP
• Report Agent
• SAM Agent
• SSL
• FIPS 140-2 compliance

Windows Server 2008 Feature Support Limitations

The following are known limitations on Windows Server 2008:

• Impersonation interception (class SURROGATE functionality), if SurrogateInterceptionMode is set to 1

  Important! Impersonation interception is supported on x64, IA64 and x86 platforms by default via the RunAs plug-in (SurrogateInterceptionMode is set to 0).

  Note: For more information about the SurrogateInterceptionMode registry setting, see the Reference Guide.

SAN Support

CA ControlMinder supports a SAN (storage area network) environment when you install CA ControlMinder on:

• A local file system and use it to protect files on a SAN, when the SAN is accessible from a single host.

  Note: If the SAN is accessible from multiple hosts, install CA ControlMinder on each host that can access the SAN and use each installation to protect files on the SAN.

• A SAN disk, subject to the following limitations:
  • CA ControlMinder drivers must be installed on the local file system.
  • You must manually start CA ControlMinder on the SAN disk each time you start or restart the computer. Do not start CA ControlMinder automatically when you start or restart the computer.

    Note: The previous condition only applies when you install CA ControlMinder on a SAN disk. If you install CA ControlMinder on a local file system and use it to protect files on a SAN, you do not need to manually start CA ControlMinder each time you restart the computer.

If the SAN is accessible from multiple hosts and CA ControlMinder is installed on the SAN, and you want to install CA ControlMinder from a different host to the same location on the SAN, consider the following before you begin:

• The new installation of CA ControlMinder replaces the existing installation of CA ControlMinder and overwrites the existing CA ControlMinder configuration files and database.
• You must stop the existing installation of CA ControlMinder before you begin the new installation.

McAfee Entercept Buffer Overflow

The CA ControlMinder STOP feature is incompatible with the McAfee Entercept buffer overflow technology.

Turn off the CA ControlMinder STOP feature or the McAfee Entercept buffer overflow protection feature.

Short File Name Rules (8.3 Format) Are Not Supported

CA ControlMinder does not support rules created as short file names (8.3 format). When you define any of the following classes, you must enter the full path name of the file or directory:

FILE, PROGRAM, PROCESS, SECFILE, SPECIALPGM

The following is an example of a rule using a full path name:

nr file ("C:\program files\text.txt")

The following is an example of a rule using a short path name that is not supported:

nr file ("C:\progra~1\test.txt")