Forefront Endpoint Protection Blog

All the latest news and information on Forefront Client Security, Forefront Endpoint Protection and System Center Endpoint Protection 2012

  • Forefront Endpoint Protection Blog

    FCS v1 March 2011 update

    • 3 Comments

    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 updates and shutdown Windows feature to update to the latest version of FCSv1.   After restart, the computer does not have the Antimalware agent installed, but will still have the Security State Assessment(SSA) and Microsoft Operation Manager components installed.

     

    The problem:

     This issue only occurs on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.   It does not occur on Windows XP, Windows Server 2003 or Windows 2000.  This issue was  not introduced in the March Update.  It is caused by a previously undetected problem in the October 2010 update.  Please review the steps below for what options you should take.

     For the bug to occur, the system must have either th policy setting changing the default shutdown behavior or the user clicks on “Apply updates at Shutdown”.   If the update is deployed or manually installed in other ways, this bug does not occur.   


    Key facts:

    1. If you have already successfully installed the March update, you do NOT need to roll it back.
    2. This bug doesn’t apply to either Microsoft Security Essentials or Forefront Endpoint Protection in anyway.
    3. It can only occur if the option for “Install Updates and Shutdown” is selected by the user or is set by policy.
    4. On unaffected computers, it in no way impacts the ability to get definition updates to stay secure.

     
    What can I do to address this issue myself?

    There are a number of workarounds that can be used currently.

     

    Avoiding the issue

    • WSUS administrators can decline or not approve for installation
    • Avoid installing KB2508823 with  “Install updates and shutdown”.   This may be accomplished by
      • a recommendation by administrators to user
      • enforcement by Automatic Updates group policy:  Computer Configuration/Administrative Templates/Windows Components/Windows Update- Do not display ‘Install Updates and shut down’ option in Shut Down Windows dialog box.
      • installing the update KB2508823 through WSUS deadlines.  That triggers to install immediately.


    Issue correction

    If you have computers which experience this issue and are now unprotected, there are a number of options

    • Download and install KB2508823 manually.  There are steps to do this in the KB: http://support.microsoft.com/kb/2508823  in the Hotfix information  section
    • Approve in WSUS “Client Update for Microsoft Forefront Client Security (1.0.1728.0)”  and decline both the March update(KB2508823) and the Client Update for Microsoft Forefront Client Security (1.0.1736.0) (2508824).  This will redeploy the prior update
    • Approve the “Client Update for Microsoft Forefront Client Security (1.0.1736.0)”   slipstream update.
      NOTE:  We have seen that in some cases this will fail with 0x666 ERROR_PRODUCT_VERSION 
      If you are seeing ERROR_PRODUCT_VERSION  failures installing the slipstream you can uninstall SSA and that should allow it to work.  To do this, choose to uninstall "Microsoft Forefront Client Security State Assessment Service" in Control Panel>Programs>Uninstall a program or by executing the command line: msiexec.exe /x {2AB5A838-9DAC-45F5-8EC2-019DDDC4B4F6} /quiet

     

    What is Microsoft doing to address this?

     We are doing the following:

    1. We have already throttled downloads of KB2508823 on Microsoft update so that users connecting directly Microsoft Update, will not have the package proactively delivered. 
    2. We are changing the logic on Microsoft update to only allow the update to apply to Windows 2000, Windows XP, and Windows Server 2003 today.   That will prevent further incidents from occurring.   We are testing this change now, and will update the blog on when you can expect to see this change.
    3. We are authoring a patch update that will address this issue on Microsoft update.   This patch will supersede the current patches for all platforms.  We will provide more information soon on when you can expect to see that package. 

    We take the support of our customers very seriously.   If you need additional assistance please contact your support professional or visit http://support.microsoft.com/ph/12632 .

    Sincerely, the Microsoft Forefront Client Security Engineering team.

     


    Update 9 March 2011

     

     

    Hello all,

     

     

    Today (8 March 2011), we released an update to FCSv1.   Changes include:

    • This update enables computers running Forefront Client Security to update definitions at the scheduled time while running on battery power.
    • This update contains changes to allow computers running Forefront Client Security service to open files encrypted by Prim'X ZoneCentral that are located in a network shared folder.
    • This update corrects issues in the mpfilter.sys kernel component used by Client Security that causes real-time protection errors on computers running Windows 2000.

    For already installed FCS client installations, install the update for Microsoft Knowledge Base article 2508823 (http://support.microsoft.com/kb/2508823).
    For new FCS Client installations, deploy the client components listed in Microsoft Knowledge Base article
    2508824 (http://support.microsoft.com/kb/2508824).

    For more information about the update, Microsoft Knowledge Base article 2508823 (http://support.microsoft.com/kb/2508823) has the detail.

     

    Thanks!


     

    We have recieved reports that in some cases the FCS update fails to install correctly.   We are reviewing these reports now, and will update this blog when we have details we can share.   If you are a WSUS administrator you may want to hold off approving this update for the moment. 
  • Forefront Endpoint Protection Blog

    Using the SMSMap tool to document FEP components in your ConfigMgr hierarchy

    • 0 Comments

    From Jeff Tondt

    Visio is one of the most popular tools for creating diagrams that describe effective systems and processes. In every project in which I participate, when it comes to documenting what you did I always have to create a diagram where I defined architecture, server configuration, network, etc. A picture is worth a thousand words and Visio is the tool of choice in these documentation tasks.

    With SMSMap you can read FEP components and ConfigMgr/SMS site roles through COM and automate Visio to draw a diagram of the hierarchy including the FEP SQL Reporting Server, FEP Data Warehouse SQL Server, and the FEP Reporting Component.

    Developed by Jeff Tondt this free utility is available at http://www.tondtware.com and works on ConfigMgr SP2 / R3 and down to SMS 2003. Seeing the whole FEP/ConfigMgr hierarchy as a picture can help you quickly understand how your infrastructure is laid out. This handy tool automates creation of your infrastructure documentation and frees you up for other Forefront product installations.

    Some screenshots of SMSMap:

    clip_image002

    clip_image006

    clip_image004

  • Forefront Endpoint Protection Blog

    FEP, MSE and FCS - and Windows 7 SP1

    • 4 Comments

    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:

    If in doubt about what you have installed, view your version number, on the Help menu, click About.

    If your version is reported in the range of 2.0.1677 to 2.0.2530, then you should:

    • Uninstall the unsupported pre-release version of the of the client currently installed, and
    • Install one of the release antimalware packages listed above, according to your organizational needs.

    Thanks!

    Note:  The same statements apply for Windows Server 2008 R2 SP1 as well; you need the same update to allow FCS function. (Douglas Hill 3/23/2010)

     

  • Forefront Endpoint Protection Blog

    Microsoft SpyNet?

    • 13 Comments

    So have you ever wondered what the Microsoft SpyNet opt in page is really all about?

    image

    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 for previously unknown threats can be created and distributed, minimizing the time that a new threat is spreading in the wild before protection is available. (Note: older clients, like FCS and Windows Defender, also participate in SpyNet, but to get the full benefits of SpyNet, which includes Dynamic Signature Service, you should move to FEP or MSE.)

    Additionally, when your FEP or MSE client reports new malware to the Microsoft SpyNet cloud service, the Dynamic Signature Service can recognize when a definition is available but not yet released, and deliver that definition for that specific threat in real-time from the cloud. Upon delivery of the dynamic signature, the threat will be detected and can be removed from the system

    Hey – here’s a thought. Take 3 minutes and watch this – Microsoft SpyNet and the Dynamic Signature Service in action:

    Click here to play this video

  • Forefront Endpoint Protection Blog

    Reporting Workbooks

    • 0 Comments

    Hello!

    A while back we posted a reporting workbook for the Forefront Endpoint Protection Security Management Pack. This workbook allows you to connect to your FEP Security Management Pack database and create custom reports based on the data contained within the database.

    We have a new addition to this – a workbook you can use to create custom FEP reports. This new workbook works in much the same way as the one previously released. You must first connect the workbook to your FEP database, and then you can use the worksheets to generate custom reports based on the data contained within the database.

    In order to make it easier for you to find both workbooks, I’ve attached a zip file that contains both of them to this blog article (if you already downloaded the one for the FEP Security Management Pack, it has not changed). Each workbook has instructions on the first worksheet on how to connect it to your database.

    Enjoy!

Page 9 of 28 (138 items) «7891011»