This article describes the Microsoft Forefront Client Security (FCS) revised installation package.
INTRODUCTION
This package revises the current deployment package that is described in the following Microsoft Knowledge Base article:
2394439 Forefront Client Security deployment package (1.0.1728.0): October 2010The purpose for this revision is to enable new computers to install the latest version of the Forefront Client Security (FCS) 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 (FCS) client components.
Hotfix information
A supported hotfix is available from Microsoft. Note This hotfix is available from only Windows Server Update Services (WSUS).
Prerequisites
There are no prerequisites for installing this update.
Restart requirement
After you apply this hotfix to computers running Windows XP Service Pack 2 (SP2) without hotfix 914882, you must restart the computer.
Update replacement information
This update replaces the following hotfixes:
2464613 Forefront Client Security deployment package (1.0.1732.0) for Windows 2000 SP4
2394439 Forefront Client Security deployment package (1.0.1728.0): October 2010
976669 Forefront Client Security deployment package (1.0.1725.0): December 2009 This update also replaces the initial release of the Forefront Client Security (FCS) 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
-
Fcsssa.msi
-
Momagent.msi
-
Mp_ambits.msi
-
Windowsxp-kb914882-x86-XXX.exe Note The Windowsxp-kb914882-x86-XXX.exe file is for only x86-based computers.
Clientsetup.exe
This update installation starts the Clientsetup.exe program that is in the package. The Clientsetup.exe program starts the other installation files in this update.Forefront Client Security, x86-based version
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Clientsetup.exe |
1.0.1736.0 |
116,120 |
03-Feb-2011 |
02:47 |
Forefront Client Security, x64-based version
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Clientsetup.exe |
1.0.1736.0 |
121,240 |
03-Feb-2011 |
18:29 |
Fcsssa.msi
This file installs 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 are the same as in the following article. However, the version number of the definitions 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 SecurityAdditionally, the service host (Fcssas.exe) has not changed from the release to manufacturing (RTM) build. However, the version number has been incremented to match the version in the title of the update package.Forefront Client Security, x86-based version
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Bpacommon.dll |
1.0.1736.0 |
223,128 |
03-Feb-2011 |
19:24 |
|
Bpaconfigcollector.dll |
1.0.1736.0 |
364,952 |
03-Feb-2011 |
19:24 |
|
Eula.rtf |
206,773 |
03-Jun-2010 |
13:24 |
|
|
Fcssas.exe |
1.0.1736.0 |
69,528 |
03-Feb-2011 |
19:24 |
|
Fcssasengine.dll |
1.0.1736.0 |
84,376 |
03-Feb-2011 |
19:24 |
|
Fcssasmsg.dll |
1.0.1736.0 |
18,840 |
03-Feb-2011 |
22:27 |
|
Fcssasondemand.exe |
1.0.1736.0 |
17,816 |
03-Feb-2011 |
19:24 |
|
Fcssasrpc.dll |
1.0.1736.0 |
22,424 |
03-Feb-2011 |
19:24 |
|
Gdiplus.dll |
5.2.6001.22319 |
1,748,992 |
03-Feb-2011 |
19:10 |
|
Muauth.cab |
7,699 |
03-Jun-2010 |
13:23 |
|
|
Vacatalog_chinesesimplified |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_chinesetraditional |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_english |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_french |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_german |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_italian |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_japanese |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_korean |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vacatalog_spanish |
6,355 |
03-Feb-2011 |
19:24 |
|
|
Vamanifest_chinesesimplified |
125,628 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_chinesetraditional |
126,035 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_english |
134,024 |
03-Feb-2011 |
19:03 |
|
|
Vamanifest_french |
132,407 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_german |
131,532 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_italian |
131,118 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_japanese |
138,909 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_korean |
131,933 |
03-Feb-2011 |
19:17 |
|
|
Vamanifest_spanish |
131,854 |
03-Feb-2011 |
19:17 |
Forefront Client Security, x64-based version
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
Bpacommon.dll |
1.0.1736.0 |
264,600 |
03-Feb-2011 |
15:32 |
|
Bpaconfigcollector.dll |
1.0.1736.0 |
408,984 |
03-Feb-2011 |
15:32 |
|
Eula.rtf |
206,773 |
03-Jun-2010 |
13:24 |
|
|
Fcssas.exe |
1.0.1736.0 |
73,624 |
03-Feb-2011 |
15:32 |
|
Fcssasengine.dll |
1.0.1736.0 |
99,736 |
03-Feb-2011 |
15:32 |
|
Fcssasmsg.dll |
1.0.1736.0 |
18,840 |
03-Feb-2011 |
18:29 |
|
Fcssasondemand.exe |
1.0.1736.0 |
17,816 |
03-Feb-2011 |
15:32 |
|
Fcssasrpc.dll |
1.0.1736.0 |
23,448 |
03-Feb-2011 |
15:32 |
|
Muauth.cab |
7,699 |
03-Jun-2010 |
13:23 |
|
|
Vacatalog_chinesesimplified |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_chinesetraditional |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_english |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_french |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_german |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_italian |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_japanese |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_korean |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vacatalog_spanish |
6,355 |
03-Feb-2011 |
15:32 |
|
|
Vamanifest_chinesesimplified |
125,628 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_chinesetraditional |
126,035 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_english |
134,024 |
03-Feb-2011 |
15:09 |
|
|
Vamanifest_french |
132,407 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_german |
131,532 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_italian |
131,118 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_japanese |
138,909 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_korean |
131,933 |
03-Feb-2011 |
15:25 |
|
|
Vamanifest_spanish |
131,854 |
03-Feb-2011 |
15:25 |
Momagent.msi
The Microsoft Operations Manager agent installation has not changed from the deployment package release. The installation package is the same version that was released with MOM 2005 Service Pack 1 (SP1). For more information about MOM 2005 SP1, visit the following Microsoft TechNet website:
Mp_ambits.msi
This file 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:
2508823 Forefront Client Security anti-malware client update: March 2011
Windowsxp-kb914882-x86-XXX.exe
This updates is applied on only 32-bit Windows XP Service Pack 2 (SP2)-based computers that do not have this update already installed. Each localized Forefront Client Security (FCS) deployment package contains a corresponding localized version of this update. If hotfix 914882 is applied in the installation of this update package, 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 on only Windows Server Updates Services (WSUS) and is not available to computers directly from Microsoft Update. WSUS uses detection logic to determine which computers can receive this update. The following conditions must be met to receive this update:
-
Supported operating systemThe 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 website:
-
FCS policy registry settingsThe computer must have already received Client Security policy from the FCS management server console. This policy contains certain registry values that are used to determine package applicability. Additionally, these registry values determine the Collection server for the client when Clientsetup.exe runs.
-
Missing an agent client componentThe computer must be missing at least one of the three Client Security client components. The components are anti-malware, security state assessment, and the Operation Manager 2005 agent.
If any of these components are missing, and if the other applicability rules match, the update applies, and WSUS 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, a client computer is installed by using 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.
