Forefront Client Security deployment package (1.0.1732.0) for Windows 2000 SP4

This article describes the Microsoft Forefront Client Security (FCS) revised installation package which is specifically for Windows 2000 SP4 computers.


This package revises the current deployment package described in:
976669 Forefront Client Security deployment package (1.0.1725.0): December 2009
The purpose for this revision is to enable Windows 2000 computers to install the latest version of the Client Security client without having to apply multiple updates. This package is published to Windows Server Update Services (WSUS) and is used to perform new installations of the Forefront Client Security client components.

Hotfix information

A supported hotfix is available from Microsoft.

Note This hotfix is available only from Windows Server Update Services.


There are no prerequisites for installing this update.

Update replacement information

This update replaces the following:
976669 Forefront Client Security deployment package (1.0.1725.0): December 2009
This update also replaces the initial release of the Forefront Client Security deployment package that is available from WSUS under the following title:
Client Update for Microsoft Forefront Client Security (1.0.1703.0)

More Information

The contents of this update are as follows:
  • clientsetup.exe
  • MOMAgent.MSI
  • mp_AMBits.MSI


This update installation starts the clientsetup.exe program which is in the package. ClientSetup.exe program starts the subordinate installation files in this section.
Changes in this release
  • Checks were added to detect the following products. If they are detected setup will not continue and an error will be written to the setup log file.
    • Microsoft Security Essentials version 2
    • Forefront Endpoint Protection client
Forefront Client Security, x86-based versions
File nameFile versionFile sizeDateTime


This subordinate component will install the Microsoft Forefront Client Security State Assessment (SSA) client. The SSA client is compromised of the service host and the assessment definitions.

The assessment definitions functionality is the same as the release listed in the following article, but the version number has been incremented to match the version in the title of the update package. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

974253 Description of a Security State Assessment update (1.0.1710.103) for Forefront Client Security

The service host (FcsSAS.exe) functionality has not changed from the release to manufacturing build, but its version number has been incremented to match the version in the title of the update package.

Forefront Client Security, x86-based versions
File nameFile versionFile sizeDateTime


The Microsoft Operations Manager agent installation has not changed from the deployment package release. The installation package is the version released with MOM 2005 Service Pack 1. For more information, visit the following Microsoft website:


This subordinate component installs the Microsoft Forefront Client Security antimalware client. The changes and binary versions of this antimalware client installation are described in the following Microsoft Knowledge Base article:
2459065 Real-time protection fails on Windows 2000 after you apply Forefront Client Security October 2010 update

WSUS Applicability Logic

As described earlier, this update is published only to Windows Server Updates Services (WSUS) and is not available to computers directly from Microsoft Update. WSUS uses detection logic to determine which computers should receive this update. The logic it uses is as follows:
  1. Supported operating system
    The computer must be running Windows 2000 operating system with Service Pack 4.
  2. FCS policy registry settings
    or the deployment package to apply to potential clients those computers must have already received Client Security policy produced by the FCS management server console. The policy contains certain registry values which are used in determining package applicability. Additionally, when clientsetup.exe runs, the registry settings determine the Collection server to which the client reports.
  3. All three agents client components are not installed
    The update detection logic looks for all three Client Security client components (anti-malware, security state assessment, Operation Manager 2005 agent). If any of these components are missing, and the other applicability rules match, the update applies and tries to install all three components. This can be useful if client computers are installed or imaged without one or more of the three components (for example, installed with the /NoMOM switch).

As soon as the applicability logic is passed, the client computer downloads and installs the appropriate localized version of the Client Security client, as described in the Client Security planning guide at, in compliance with the configured Windows update policy.