If you want a Notes client to stop operating, I guess the easiest way to do this would be to write an agent in the address book template that checks to see if the creation date (maybe of a profile document, created upon database open) is more than 90 days old. If the profile date is more than 90 days old, then close the Notes client with
You won't, of course, be able to stop a "power" user from reconfiguring the Notes client to get around this.
A more effective way to do this and a way that may provide a better option for you and your clients might be the following option, which just locks down your demo databases.
- Set the ACL of the database to have default "Manager" access.
- Remove all other ACL entries (LDS, LDS, ODS, etc.).
- Create a generic profile form in the database with a "CheckDate" field.
- Write a database script, which in the initialize event of the DB checks to see whether a corresponding profile document exists; if it doesn't, create it and write to the CheckDate.
- Once you have a handle on the profile document, check the "CheckDate."
- If the "CheckDate" is more than 90 days old, change all the ACL entries to "Reader" (in case the demo tester has modified the ACL).
- Hide the design of the database.
Dig Deeper on Lotus Notes Domino Administration Tools
Related Q&A from Mathew Newman
SearchDomino.com Sametime administration expert Mathew Newman explains-step-by-step how to enable communication between multiple Lotus Sametime ... Continue Reading
If Lotus Sametime users on different "home" servers cannot see each other online, you may need to change your Sametime server awareness by creating ... Continue Reading
SearchDomino.com's Sametime administration expert Mathew Newman offers advice to a Lotus Notes administrator looking for resources for deploying ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.