Forefront Client Security deployment package (1.0.1728.0): October 2010

Prerequisites

There are no prerequisites for installing this update.

Restart requirement

Windows XP SP2 client without KB914882 must restart the computer after you apply 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)

Clientsetup.exe

This update installation starts the clientsetup.exe program that 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

Forefront Client Security, x64-based versions

FCSSSA.MSI

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 its 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

Forefront Client Security, x64-based versions

MOMAgent.MSI

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:

MOM 2005 Service Pack 1
http://technet.microsoft.com/en-us/opsmgr/bb498239.aspx

mp_AMBits.MSI

This subordinate component installs the Microsoft Forefront Client Security anti-malware client. The changes and binary versions of this anti-malware client installation are described in the following Microsoft Knowledge Base article:

2394433 Forefront Client Security antimalware client update: October 2010

WindowsXP-kb914882-x86-XXX.exe

This updates is only applied on 32-bit Windows XP Service Pack 2 computers which do not have it already installed. Each localized Forefront Client Security deployment package will contain a corresponding localized version of this update.

If KB914882 is applied during installation of this update package then a restart is required.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

914882 The filter manager rollup package for Windows XP SP2

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 an FCS supported operating system. A list of supported operating systems can be found on the FCS system requirements page at the following TechNet Library page: http://go.microsoft.com/fwlink/?LinkId=77561

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 http://go.microsoft.com/fwlink/?LinkId=103309, in compliance with the configured Windows update policy.