https://www-secure.symantec.com/connect/forums/last-configuration-request-date-incorrect
If that does not work then check to make sure that table is being logged. Check settings, notification server, resource data class and association history, software delivery summary. Enable those 3 and see if that does it.
Finally, go to settings, notification server, purging maintenance. On the Resource Event Data Purge Settings tab increase the max table rows to 1 million.">I ran into something similar before. Try this... https://www-secure.symantec.com/connect/forums/last-configuration-request-date-incorrect
If that does not work then check to make sure that table is being logged. Check settings, notification server, resource data class and association history, software delivery summary. Enable those 3 and see if that does it.
Check Settings, Agents/plug-ins, Symantec Management Agent, Settings, Symantec Management Agent Settings - Global. on the Events tab make sure all the boxes are checked that you want to report on.
https://www-secure.symantec.com/connect/forums/last-configuration-request-date-incorrect
If that does not work then check to make sure that table is being logged. Check settings, notification server, resource data class and association history, software delivery summary. Enable those 3 and see if that does it.
Finally, go to settings, notification server, purging maintenance. On the Resource Event Data Purge Settings tab increase the max table rows to 1 million.">Finally, go to settings, notification server, purging maintenance. On the Resource Event Data Purge Settings tab increase the max table rows to 1 million.