ePO and Protection Workspace Reporting

[FG_Mark]

Has anyone experienced a sudden drop in compliance reporting after a repository update? Also, notice two extensions missing. They were there but are not now. Thanks in advance for any advice.

[cdinet]

What particular products did you update?  What specific extensions are missing?  The compliance determines if systems are up to date, not just with content, but product versions.  So if you didn't update the clients to latest versions you checked in, they may show out of compliance due to not at the latest version.  

[FG_Mark]

Hmmm, you may be on to something I overlooked. The adaptive threat on my client is version 10.7.0.2481 but I do not see that version in my software catalog at all. I only see 10.6. It seems I may have removed that from the software catalog. But, it still shows up as a deployable product in client task? I am definitely doing something wrong.

How do I update the software catalog? I tried a master repository pull multiple times. They are successful but no change in the software library.

[FG_Mark]

Oh, to answer your first question, we did a check-in on all the software in the library catalog for endpoint applications. 

[FG_Mark]

Its always the easy and obvious answers. My compliance numbers dropped because software was updated on server catalog but a vast majority of my systems were still on the previous version. I assumed, for some strange reason, ePO was like a WSUS server. It is not, i think. I assumed my previously created client task would use the latest software versions and did not realize I was pushing the previous version every time I tried to deploy after I updated. I had also managed to remove an extension I was using when I was getting rid of unneeded extensions .

To fix my issues I added the missing server extension, and updated my client task catalogs with the most up to date software. I also learned to be a little more attentive when deleting used extensions from ePO.

[cdinet · Accepted solution]

Yea, you have to be careful removing extensions, as you can lose all your policies for that product.  Make sure in server settings, policy and task retention, that you have that enabled if you ever do have to remove an extension.  If you don't want to keep the policies, then temporarily disable that.  

Pull tasks only pull content updates, like dats, amcore, engines, etc.  To update software versions, that has to be done via the software catalog.  Once you update your software, then you would need to edit your deployment tasks and/or update tasks to push out the new software when you are ready to deploy.