Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

This article describes the Microsoft Forefront Client Security (FCS) revised installation package.

INTRODUCTION

This package revises the current release to manufacturing deployment package:

Client Update for Microsoft Forefront Client Security (1.0.1703.0)The purpose for this revision is to let new computers to install the latest version of the Client Security client without having to later apply previously released 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.


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 current Forefront Client Security deployment package that is available from WSUS and that has 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

  • FCSSSA.MSI

  • MOMAgent.MSI

  • mp_AMBits.MSI

  • windowsxp-kb914882-x86-XXX.exe (x86 only)

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

The following revisions were made to ClientSetup.exe for 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

    • Microsoft Security Essentials Codename "Morro" beta

    • Forefront Endpoint Protection Beta client

  • In earlier version of ClientSetup.exe installation on Windows XP Media Center Edition was blocked. That block has been removed in accordance with a revised support statement.

  • In earlier version of ClientSetup.exe installation on Windows Vista Home Editions produced warnings in the setup log file. Those warnings have been removed in accordance with a revised support statement.

Forefront Client Security, x86-based versions

File name

File version

File size

Date

Time

Clientsetup.exe

1.0.1725.0

116,104

23-Oct-2009

03:46

Forefront Client Security, x64-based versions

File name

File version

File size

Date

Time

Clientsetup.exe

1.0.1725.0

121,224

22-Oct-2009

22:57

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

File name

File version

File size

Date

Time

Bpacommon.dll

1.0.1725.0

223,112

23-Oct-09

0:31

Bpaconfigcollector.dll

1.0.1725.0

364,936

23-Oct-09

0:31

Eula.rtf

206,773

20-Apr-07

20:45

Fcssas.exe

1.0.1725.0

69,512

23-Oct-09

0:31

Fcssasengine.dll

1.0.1725.0

84,360

23-Oct-09

0:31

Fcssasmsg.dll

1.0.1725.0

18,824

23-Oct-09

3:46

Fcssasondemand.exe

1.0.1725.0

17,800

23-Oct-09

0:31

Fcssasrpc.dll

1.0.1725.0

22,408

23-Oct-09

0:31

Gdiplus.dll

5.2.6001.22319

1,748,992

23-Oct-09

0:09

Muauth.cab

7,699

20-Apr-07

20:45

Vacatalog_chinesesimplified

6,342

23-Oct-09

0:31

Vacatalog_chinesetraditional

6,342

23-Oct-09

0:31

Vacatalog_english

6,342

23-Oct-09

0:31

Vacatalog_french

6,342

23-Oct-09

0:31

Vacatalog_german

6,342

23-Oct-09

0:31

Vacatalog_italian

6,342

23-Oct-09

0:31

Vacatalog_japanese

6,342

23-Oct-09

0:31

Vacatalog_korean

6,342

23-Oct-09

0:31

Vacatalog_spanish

6,342

23-Oct-09

0:31

\2052\Vulnerabilitydefinitions.manifest

125,628

23-Oct-09

0:24

\1028\Vulnerabilitydefinitions.manifest

126,035

23-Oct-09

0:24

\1033\Vulnerabilitydefinitions.manifest

134,024

23-Oct-09

0:01

\1036\Vulnerabilitydefinitions.manifest

132,407

23-Oct-09

0:24

\1031\Vulnerabilitydefinitions.manifest

131,532

23-Oct-09

0:24

\1040\Vulnerabilitydefinitions.manifest

131,118

23-Oct-09

0:24

\1041\Vulnerabilitydefinitions.manifest

138,909

23-Oct-09

0:24

\1042\Vulnerabilitydefinitions.manifest

131,933

23-Oct-09

0:24

\3082\Vulnerabilitydefinitions.manifest

131,854

23-Oct-09

0:24

Forefront Client Security, x64-based versions

File name

File version

File size

Date

Time

Bpacommon.dll

1.0.1725.0

264,584

22-Oct-09

19:37

Bpaconfigcollector.dll

1.0.1725.0

408,968

22-Oct-09

19:37

Eula.rtf

206,773

20-Apr-07

20:45

Fcssas.exe

1.0.1725.0

73,608

22-Oct-09

19:37

Fcssasengine.dll

1.0.1725.0

99,720

22-Oct-09

19:37

Fcssasmsg.dll

1.0.1725.0

18,824

22-Oct-09

22:57

Fcssasondemand.exe

1.0.1725.0

17,800

22-Oct-09

19:37

Fcssasrpc.dll

1.0.1725.0

23,432

22-Oct-09

19:37

Muauth.cab

7,699

20-Apr-07

20:45

Vacatalog_chinesesimplified

6,342

22-Oct-09

19:37

Vacatalog_chinesetraditional

6,342

22-Oct-09

19:37

Vacatalog_english

6,342

22-Oct-09

19:37

Vacatalog_french

6,342

22-Oct-09

19:37

Vacatalog_german

6,342

22-Oct-09

19:37

Vacatalog_italian

6,342

22-Oct-09

19:37

Vacatalog_japanese

6,342

22-Oct-09

19:37

Vacatalog_korean

6,342

22-Oct-09

19:37

Vacatalog_spanish

6,342

22-Oct-09

19:37

\2052\Vulnerabilitydefinitions.manifest

125,628

22-Oct-09

19:31

\1028\Vulnerabilitydefinitions.manifest

126,035

22-Oct-09

19:31

\1033\Vulnerabilitydefinitions.manifest

134,024

22-Oct-09

19:07

\1036\Vulnerabilitydefinitions.manifest

132,407

22-Oct-09

19:31

\1031\Vulnerabilitydefinitions.manifest

131,532

22-Oct-09

19:30

\1040\Vulnerabilitydefinitions.manifest

131,118

22-Oct-09

19:31

\1041\Vulnerabilitydefinitions.manifest

138,909

22-Oct-09

19:31

\1042\Vulnerabilitydefinitions.manifest

131,933

22-Oct-09

19:31

\3082\Vulnerabilitydefinitions.manifest

131,854

22-Oct-09

19:31

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 Web site:

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:

976668 Forefront Client Security anti-malware update: December 2009

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 S

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 TechNet system requirements page at the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=77561

  2. FCS policy registry settings
    In order for 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 applicability. Additionally, when clientsetup.exe runs the settings will 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 will download and install 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 accordance with the configured Windows update policy.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×