Fep clients not updating definitions role playing dating games for guys
I just left out the Power Users group as it’s not used in our environment.
It is imperative that you test this on one or two systems before rolling it out, and make sure it works well in your environment.
FEP creates a collection called Out of Date which is under FEP Collections – Deployment Status.
This collection leverages a custom SQL query created by FEP that identifies machines that have an old version of the FEP client.
When an attempt is made to start the service, the resulting error is: Error 0x80004015: The class is configured to run as a security id different from the caller.
The Authentic Users group only gets read permissions, not start/stop permissions as I feared, so I’m fine with that.
Chances are you likely want to use a new advertisement to upgrade your clients.
I will assume that you know how to create an advertisement for your environment, however what I would like to point out is a potential collection you can target.
Rollup 1, you will have the option for x86 and x64 versions as well as a hotfix KB2554364 which is reporting fix that must be installed prior to installing Rollup 1.
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.
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.
We also had to create some additional DCM configuration items and collections.