Agents and accessing dates ran

HCL Domino Domino Forum
1

I’ve been tasked to find out when users have archived any of their mail.

Users have their mail local and on the server. Daily access is done through the local copy. If a User archives manually or allows the auto weekly agent to archive I know the agents record the date and time.

If the agents are run from the local PC does this date and time get replicated up to the server and update the agents there with the same values?

I know I can access the LastRan property via the NotesAgent class:

dateV = notesAgent.LastRun

If the values don’t update on the server how would you go about getting the dates & times the Users ran either of the two agents? I’m thinking I’ll need to send them a email with a button to click. When the button is clicked it would generate a hidden email with the values mailed into a database.

Anyone know of a way to access the data using LotusScript code on the local machine without the Users having to take action?

I thought about adding a scheduled agent to the mail template then having the AdminP put this agent into everyone’s mail file on the server. This would then replicate to everyone’s local mail file. The agent could check server being used then report back the LastRan properties for the two agents. But I don’t think my boss would like the idea of me adding an agent to the mail template. Your thoughts about this idea? Any problems with it?

2

Subject: RE: Agents and accessing dates ran

Hi Stu, seeing how no one has posted a response, I share my thoughts with you.

I’m not familiar with adminp being able to add agents, unless you’re thinking of modifying the standard mail template. We have created custom mail templates generated from the standard ones (in case we need to roll back, etc) , but, as you know, takes planning and MUCH testing to make sure enabled agents and private folders, views, script libraries, etc don’t get duplicated .

The archiveprofile will tell you where the archive is being run and the path of the archive database, and if logging is enabled the location of the archive log.

You would have to query all archiveagents on both the server and local copies to see when archiving last ran. Or you could modify each of the archive agents to send an email to a mail-in database with the user name, agent name and run date/time.

A well crafted script under a button could also check dates.times, but after the first few emails, I think you might find people will stop clicking the button.

Hope this helps…