Migrating to FCS EFF Forefront EndPoint Protection with SCCM 2010

[Inigo]

Migrating to 2.3 FCS EFF

Forefront EndPoint Protection 2010 brought a real change in the functioning of the range of antivirus company Microsoft. Unlike Forefront Client Security (FCS) which was built on a specific version of Microsoft Operations Manager (MOM) 2005; EFF 2010 is built for it on the basis of the System Center. Thus, this involves changes in depth. Forefront EndPoint Protection 2010 does not migrate itself with conditions line In-Place or Side-by-Side. The following points explains the same :

1. In the console FCS, document all the settings for each of the strategies you use to power then recreate them in VET.
2. In WSUS, disable the approval of the installation packages FCS.
3. Install Forefront Endpoint Protection with your infrastructure System Center Configuration Manager 2007
4. Recreate strategies EFF with the settings you have documented on your upstream server FCS.
5. Massively deploy the client EFF. This will migrate your desktops by uninstalling the client FCS and conducting the installation of the new client EFF.
6. Then uninstall FCS infrastructure once all clients have been migrated to EFF.

[Inigo]

Migrating to 2.4 FCS EFF

The installation of Forefront EndPoint Protection 2010 (EFF) completed successfully, you can open the management console of System Center Configuration Manager 2007. Expand the Site Database tree => Computer Management => Collections. We thus find a collection EFF Collections containing different sub-collections. These sub-collections are blocked and can not be deleted. The content of dynamic queries and settings are also unchangeable. These collections can thus give you an overview of the status of customers including information on:

• The state definitions (date)
• The state of the client deployment FPS (In failure, Pending, deployed, untargeted ...)
• A collection dedicated to operations; This collection can be used for all operations on the client EFF (Starting a scan ...)
• The prior distribution strategies (distributed, pending, failed)
• The protection status (On, unreported, service disabled)
• The security status (full scan required, infected, reboot required ...)

[Inigo]

The prerequisites necessary hardware to install Forefront client EndPoint Protection are:

• CPU:
  
  • Windows XP: 500 MHz or higher
  • Windows Vista or Windows 7: 1.0 GHz or higher
• Memory:
  
  • Windows XP: 256 MB RAM or more
  • Windows Vista or Windows 7: 1 GB of RAM or more
• Available disk space: 300 MB

The installation of Forefront Client Endpoint Protection uninstall automatically following antivirus if they are present on the machine:

• Symantec Endpoint Protection version 11
• Symantec Corporate Edition version 10
• McAfee VirusScan Enterprise version 8.5 and version 8.7 and Its Agent
• Forefront Client Security version 1 & the Operations Manager agent
• TrendMicro OfficeScan version 8 and version 10

[Inigo]

The installation of infrastructure Forefront EndPoint Protection 2010 requires certain prerequisites from the following:

• Operating Systems: Windows XP SP3 (x86), Windows Vista RTM or higher (x86 or x64), Windows 7 RTM (x86 or x64), Windows 7 XP user, Windows Server 2003 SP2 (x86 or x64), Windows Server 2008 RTM or higher (x86 or x64), Windows Server 2008 R2 (x64) or higher, Windows 2008 R2 Server Core (x64)
• Note that the Server Core version of Windows Server 2008 is not supported by the client EFF.
• Versions: Windows 7 Starter, Windows Home Premium, Windows Vista Basic, Windows Vista Home Premium, Windows XP Home Edition support the installation manual but can not receive clients strategies (policies) of the server.
• A client System Center Configuration Manager functionality. The site the SCCM client must have a server installed EFF.
• Windows Installer 3.1
• The hotfix package manager filter for Windows XP SP2 (KB914882)
• WFP (Windows Filtering Platform) driver hotfix rollup for Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2 (KB981889)
• Windows Update