When you run the Microsoft Forefront Client Security (FCS) client setup tool (ClientSetup.exe), you may experience one or more of the following symptoms:
Microsoft Operations Manager (MOM) agent components appear in the Add or Remove Programs dialog box. However, these components did not previously appear in this dialog box.
When you run the SetActionAccount.exe tool from the InstallationDirectory\Microsoft Forefront\Client Security\Server\Microsoft Operations Manager folder, a MOM action account appears. However, this account is not the MOM action account that you specified when you set up FCS. The SetActionAccount.exe tool is configured to run as the service identity account.
The hourly script on the MOM server automatically approves new FCS client computers that reside in the Pending-Approval state.
In the Client Security console, the 14-day History chart and some historical reports that appear on the Dashboard tab may not be displayed correctly.
This problem occurs because the FCS client setup tool cannot detect an evaluation edition of MOM 2005 SP1 that has been installed for FCS. Therefore, when the FCS client setup tool runs, it tries to reinstall the MOM agent on the FCS collection server. Then, MOM no longer functions correctly.
If you have already installed the FCS client on the FCS collection server by running the FCS client setup tool, follow these steps to resolve the problem:
Uninstall the FCS collection server, MOM server, and MOM agent components from the list in the Add or Remove Programs dialog box.
Reinstall the collection server role on FCS by using the FCS ServerSetup.exe tool.
Note If FCS collection server has other roles, you do not have to make any changes to these roles.
If you have not installed the FCS client on the FCS collection server by running the FCS client setup tool, work around this problem by using the /NOMOM switch.
Note When you install the FCS client, we recommend that you install the full version of MOM 2005 SP1 instead of the evaluation version.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.