Have FCS? Moving to FEP?

Hey folks! I wanted to let you know that we have guidance for migrating from FCS v1 to FEP 2010 here (http://technet.microsoft.com/en-us/library/gg477033.aspx). The process involves the following high level steps: Document the policy settings you want to preserve from FCS to FEP. There is no policy migration between the two versions. In WSUS, unapprove all…


FCS - Upcoming solution for installation issues with March 2011 Update

We have been working hard on a solution for customers that encountered issues with our update in March. I wanted to let you know what we are planning to address this. We are authoring a package that is specifically designed to find systems that have a failed upgrade to our March update. To do this,…

0

FCS v1 March 2011 update

Update 10 March 2011 We have received reports of an installation issue with our March update of Forefront Client Security when the option of “install updates and shutdown” is used.  We wanted to be clear on the issue and exactly what steps we are taking to rectify it. Symptom:  A computer attempts to use the install…


FEP, MSE and FCS - and Windows 7 SP1

Hello folks! Did you know that Windows 7 SP1 is available for download? Windows 7 SP1 brings some great features to the platform, and everyone’s pretty excited about it. We want to make absolutely clear that Windows 7 SP1 is supported by the following endpoint security products: FCS with KB2394433 or later MSE v1 with KB2254596 or later…


Microsoft SpyNet?

So have you ever wondered what the Microsoft SpyNet opt in page is really all about? Microsoft SpyNet is a cloud service that allows the FEP or MSE client on your computer to report information about programs that exhibit suspicious behavior to the Microsoft Malware Protection Center (MMPC) researchers. When this information is reported, definitions…


FCS: 64-Bit Clients do not report the antimalware version in the Computer Details report in the Forefront Client Security management console

An issue has been identified in Forefront Client Security (FCS) where when viewing the computer details report from the Forefront Client Security management console, the antimalware client version on 64-bit clients is not reported accurately. This is because of an error in the way the Operations Manger 2005 Management Pack collects this information. During Forefront…


FCS Path based exclusions do not apply to mount points

Hi, If you’ve configured path based exclusions in FCS 1.0, you may notice that mount points in the path tree are still scanned. This happens because the mount point resides on a different volume than the parent folder. When a file is accessed on the mount point, FCS receives a device path that is not…


QFE9 KB2394433 introduces RTP error 0x8007007f on Windows 2000

There is an issue with the changes made in QFE9 (KB2394433) that prevents the Antimalware minifilter mpfilter.sys from loading properly on Windows 2000. This causes a failure to provide On Access Real-Time Protection. If you do not have any Windows 2000 computers in your organization, this issue does not apply to you. UPDATE: This morning…


FCS v1 Update

Hello all, A short note, but on October 12th, we released an update to FCSv1.   This update contains: This update is supported on Windows 7 SP1 RC or greater.  Windows 7 Service Pack 1 will check for the presence of this update or a superseding update before installing. This update contains changes to the Forefront…


Forefront Client Security Offline Asset Removal Tool available

Our support folks have created a tool that enables you to remove permanently offline computers from your FCS database. Client computers go offline for many reasons, including decommission, re-tasking, and re-imaging. After a day, these computers are shown in the "Not Reporting" section of the Client Security console. After 30 days, these computers are removed…