Follow

Work Around: KAV Definition Date Does Not Match Endpoint And Incorrectly Reports Out of Date

Problem:

KAV Definition Date on VSA Does Not Match Endpoint And Incorrectly Reports Out of Date

 

Resolution:

This is a known issue being investigated by our engineering team. For the meantime, I have written the following work-around in order for you to be able to confirm which machines are ACTUALLY out-of-date and which are just reporting falsely:

 

1. Create A Custom Field called KavDatabaseOutOfDate in Audit>View individual Data>Machine Summary (You only need to do this on one agent, it will create it across all agents):

12-4-2015_2-33-07_PM.png

 

2. Create a custom view that will check this custom field for the value "Yes":

12-4-2015_2-34-41_PM.png

12-4-2015_2-35-12_PM.png

12-4-2015_2-35-27_PM.png

 

4. Import the attached agent procedure.xml to your VSA:

12-4-2015_2-56-39_PM.png

 

5. Select the procedure in question and select the desired agent(s) you will be running this on and schedule/run now:

12-4-2015_2-58-19_PM.png

 

6. You will be prompted for a date, this is the date that you will check your agents against, typically you would want to check against the last time your machines should have updated definitions. Note: Please make sure to honor the format specified:

12-4-2015_2-51-16_PM.png

 

If the database date is LESS than what inputted here, it will report as out of date. 

The view you created will show you machines that are truly out of date:

12-4-2015_3-00-54_PM.png

 

If you are curious what is going on in the script, I recommend you navigate to Agent>Machine Status>Agent Logs. Select the agent(s) in question and select the Agent Procedure Log in the drop-down menu:

This is how an up-to-date machine will look:

12-4-2015_3-02-34_PM.png

 

This is how an out-of-date machine looks like:

12-4-2015_3-03-18_PM.png

 

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.