SCR system tips

  • Article

 

Applies to: Forefront Security for Exchange Server

The following are additional guidelines when using FSE on an SCR system:

  • Install FSE on the source system, not the target system (since, by their nature, all target nodes are passive). If the source installation fails over to the target installation, the target installation now becomes the new source. Install FSE on the new source system and uninstall it from the failed over system.

    After FSE has been uninstalled, run the Exchange Setup command with the RecoverCMS parameter to remove the original source Clustered Mailbox Server. The syntax is:

    Setup /recovercms

  • Configuration data such as ScanJobs.fdb and Notifications.fdb will be associated with a CMS and not with the physical nodes. Because of this behavior, the data must be configured for each CMS only, regardless of how many nodes you have.

  • Scanner signature files are associated with a CMS so that active nodes and passive nodes will be up to date.

  • Configuration data that is kept in the registry will be replicated on a CMS basis when the CMS moves from one server to another server during a failover event.

  • When you use the Forefront Server Security Administrator console to connect to the Forefront Security for Exchange Server installation on a cluster, you must connect to the CMS. If you try to connect to the physical node, you will be prompted to select the CMS to which you want to connect.

For more information about uninstalling FSE, see "Uninstalling FSE From an SCR System" at Uninstalling FSE.