Endpoint Encryption

 View Only
  • 1.  SEE Device Control failed to push policy

    Posted Nov 05, 2012 02:30 AM
      |   view attached

    Hi, I have a strange error, when I try to update my clients i get "failed to push policy" and in the ditailes I get "Not found",

    after few hours the clients update themselves from the server but I can't update them "manually"...

    what can be the problem?



  • 2.  RE: SEE Device Control failed to push policy

    Posted Nov 05, 2012 03:42 AM

    From what I recall, SEE-DC uses WMI to a client to get it to check in with the server.

    Is WMI enabled on your endpoint, and does the service account running SEE-DC have admin rights on that endpoint?



  • 3.  RE: SEE Device Control failed to push policy

    Posted Nov 05, 2012 04:16 AM

    WMI is enabled and I have domain admin account...



  • 4.  RE: SEE Device Control failed to push policy

    Posted Nov 05, 2012 04:47 AM

    In that case can you confirm if/what errors you are receiving when following the below article (as recommended by the SEE-DC documentation):

    http://msdn.microsoft.com/en-us/library/aa394603(v=vs.85).aspx



  • 5.  RE: SEE Device Control failed to push policy

    Posted Nov 06, 2012 04:17 AM

    How can I fix errors like this:

    "ERROR: (CheckWMIFeatures) : 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found"

    I have few of them...



  • 6.  RE: SEE Device Control failed to push policy
    Best Answer

    Posted Nov 08, 2012 04:14 AM

    What kind endpoints are you seeing these errors on?  MS have loads of articles on this error, a selection of which are below.

    http://support.microsoft.com/kb/2465990

    http://support.microsoft.com/kb/919698

    http://support.microsoft.com/kb/2257980

    http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559(v=vs.85).aspx

    Perhaps it might be worth contacting MS for further investigation of this issue, if your own investigations do not resolve it?



  • 7.  RE: SEE Device Control failed to push policy

    Posted Nov 13, 2012 04:02 AM

    Thank you!!

     

    Microsoft Hotfix-

    http://support.microsoft.com/kb/2465990/en-us

    Fixed the problem!!!