Fep clients not updating definitions
We also had to create some additional DCM configuration items and collections.This whole thing became a pretty tedious process to setup, but in the end it worked and the clients could get the definitions from their local DPs instead of the Software Update Point, WSUS server, UNC Share, or Microsoft Update. Now, I and many other SCCM admins have never understood why they didn’t solve that in a more elegant manner. First of all this should make any Config Mgr admin shiver, as it should have been drilled into your head that you are supposed to do software updates management from the Config Mgr administrator console.
This collection leverages a custom SQL query created by FEP that identifies machines that have an old version of the FEP client. Finally the Forefront team came up with a solution that since the release of the product they really missed . The following list is a summary of the updates in FEP Update Rollup 1 for server functionality.The reporting fix needs to be installed on your Reporting server.
Once you have downloaded FEP 2010 Update Rollup 1 and KB2554364 for the architecture types in your environment (32 or 64 bit) you also need to download the FEP 2010 Update Rollup 1 has a client upgrade as well.
In order to use the software updates feature for definition updates, you must perform the following high-level steps: in Config Mgr, Config Mgr 2007, Config Mgr 2007 R2, Config Mgr SP2, configmgr2007, Config Mgr2007 R3, FE, FEP, FEP2010, Installation, R3, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2 by Kenny Buntinx [MVP] In some cases, after the FEP client has been installed, the computer is no longer remotely accessible using any form of remote control utility or Computer Management tools, including but not limited to Windows Computer Management, Config Mgr Remote Control utility, Dame Ware, VNC.