I noticed that FEP 2010 on Configuration Manager sometimes processes packages in a weird fashion – it simply keeps refreshing the “FEP – Deployment 1.0” package. After 24 hours the version of the package was over 300.
To solve the problem I disabled the Status Filter Rule “FEP policy modification from parent site status filter”. The filter calls plcupdtr.exe which triggers an update to packages.
Down side is that now I need to manually manage my FEP package after modifications to the policy files.