Attached to this blog post is the FEP Datawarehouse Space Capacity Planning worksheet. You can use this worksheet to help estimate the amount of disk space needed based on the following values:
After you enter in your values in the yellow area, the calculated results appear in the next set of rows. Each row contains information about average record sizes, number of records per computer per day, total size of the record type in the database, and the percent of the total space used by the record item.
The final row in the spreadsheet, in green, gives you the total estimated size of the FEP Datawarehouse, given the values you supplied.
We wanted to update you about an issue with FEP that you may have seen in your organization. This is a known issue, and we’ll keep you up to date with developments.
Periodically, the FEP data collection job (FEP_GetNewData_FEPDW_xyz) fails. When the job fails, the FEP Health Management Pack for Operations Manager and the FEP BPA report an error with the FEP datawarehouse job either failing or not running. The failure is in one of the following job steps:
This happens because of the following scenario:
Here’s a hotfix for FEP 2010 that we recently published. This one’s an update that adds Windows 8 and Windows Server 2012 support to Forefront Endpoint Protection 2010 clients
This article describes an update that enables the Microsoft Forefront Endpoint Protection 2010 client to support Windows 8 and Windows Server 2012. After you install this update, you can install the Forefront Endpoint Protection 2010 client on a computer that is running Windows 8 or Windows Server 2012.
Note This update only applies to Forefront Endpoint Protection 2010 clients that are integrated with Microsoft System Center Configuration Manager 2007.
To continue reading and to get a download link, please see the following:
2758685 - Update adds Windows 8 and Windows Server 2012 support to Forefront Endpoint Protection 2010 clients (http://support.microsoft.com/kb/2758685)
J.C. Hornbeck | Knowledge Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
While you’ve always had the ability to use MOM 2005 to monitor things like IIS and SQL for your Client Security servers, this management pack gives you the additional ability to monitor some key FCS services:
I should clarify; the management pack is installed in your MOM 2005 environment to extend existing MOM functionality, not on your FCS servers.
Of course, loading the management pack doesn’t impact how you’ll be monitoring your client computers. In other words, you won’t need to redeploy your implementation in order to add this additional monitoring functionality. You’ll continue to use the Client Security consoles you’re familiar with for your client monitoring. The Health Management pack is just for monitoring your FCS servers, not client computers. And just for environments that choose to implement a MOM 2005 monitoring solution. (notice, it’s a MOM 2005 management pack, not a SCOM management pack, just in case you were wondering “Hey, will this work with SCOM?”)
The FCS management pack is ready for download at this location: http://www.microsoft.com/downloads/details.aspx?FamilyID=0672b4ca-c6dc-4093-bae6-30eb1560a429&DisplayLang=en
Today we posted guidance on using an existing WSUS server from an Configuration Manager deployment for FCS definition distribution. The complete guidance, Deploying FCS definition updates with a shared System Center Configuration Manager WSUS infrastructure (http://technet.microsoft.com/en-us/library/dd185652.aspx
), can be read on TechNet.
Refer to Supported configurations for using WSUS to distribute Forefront Client Security Definition updates within System Center Configuration Manager 2007 (http://support.microsoft.com/default.aspx/kb/958491) for supported FCS and Configuration Manager shared configurations.