• State Verified Answer
  • Locked Locked
  • Replies 17 replies
  • Subscribers 14 subscribers
  • Views 15872 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Deployment Manager: Last Event more than 3 weeks old

david.werner
over 6 years ago

InTrust: version 11.2

Collection comprised of only Domain controllers.

 

Collecting status is green, however, the Last Event collected is more than 3 weeks old for each Domain Controller. I opened repository Viewer and ran a query. Most current events showing are also more than 3 weeks old.

I deleted my collection and created a new collection. Same results, the Last Event is never updated.

Any suggestions?

 

David

Parents
  • 0 over 6 years ago
    Hi Chris,

    As mentioned, all servers are 'Collecting' and the Last event date is current. This is working fine in my DEV environment.

    In my PRODUCTION environment, all servers are 'Collecting', however, the Last event date for some servers is old, other servers it is up-to-date. This can also change. On an up-to-date server, if I reopen the Deployment Manager, it will no longer show an up-to-date value for the Last event date, instead it switches back to the older date. This is random for the servers that are collecting.

    I have performed the SQL Server actions on the InTrust_Cfg_DB database and have installed the hotfixes.

    Any other thoughts or options?

    david
Reply
  • 0 over 6 years ago
    Hi Chris,

    As mentioned, all servers are 'Collecting' and the Last event date is current. This is working fine in my DEV environment.

    In my PRODUCTION environment, all servers are 'Collecting', however, the Last event date for some servers is old, other servers it is up-to-date. This can also change. On an up-to-date server, if I reopen the Deployment Manager, it will no longer show an up-to-date value for the Last event date, instead it switches back to the older date. This is random for the servers that are collecting.

    I have performed the SQL Server actions on the InTrust_Cfg_DB database and have installed the hotfixes.

    Any other thoughts or options?

    david
Children
No Data