By default, the FEP 2010 Deployment – Install package is configured to download and run the installation program on the client computer. If you modify the advertisement to run the install from the Distribution Point (DP), the install fails with the following error message:
“The program for advertisement "XYZ" failed ("XYZ - "Install"). The failure description was "FEP failed compiling CCM_ISV_SoftwarePolicy required for applying policy. Error code: 0x1".”
If you want to run the FEP Client install from the DP you need to do the following:
Gershon Levitz, Technical Writer MSDiX
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:
The FEP2010 Reporting account is defined during the FEP server setup, with the installation of the Reporting role to be exact. The account is used by SQL Reporting Services (SRS) to access the FEP data source used by reporting. Incorrect credentials may result in an error as below or similar:
This post is to provide you with the steps needed to change the reporting account in the occasion you have a need to do so.
Note: all below steps must be executed with an administrator account.
These steps must be executed on the SQL Server hosting the data warehouse database (FEPDW_XXX, where XXX is your Configuration Manager site code).
These steps must be executed on the SQL server hosting the data warehouse database (FEPDW_XXX, where XXX is your Configuration Manager site code).
These steps can be executed from any system. XXX is your Configuration Manager site code.
These steps must be executed on the server hosting the FEP2010 Reporting role.
Kurt Sarens, Senior Support Engineer
FEP 2010 clients require the Windows Filtering Platform (WFP) rollup package KB981889 on Windows Vista, 2008, 2008 R2, and Windows 7 – and installation of this package requires a client reboot.
One of our support engineers, Jeramy, recently needed to assist a customer in getting the rollup distributed to client computers ahead of time, to allow the reboot to happen during the normal maintenance cycle.
Jeramy wrote up the steps you need to take in order to deploy rollup KB981889 before deploying the FEP client software – take a look:
Thanks for reading – and thanks Jeramy!