Tuesday, February 24, 2009

Domino Configuration Tuner

Friday, February 20, 2009

New option: How to apply this setting in Lotus Domino 8 Policies

Domino 8 introduces a new How to apply this setting option, which is available for all desktop,mail, productivity tools, and activities policy settings. This standardizes the method that administrators can use to set and lock down policy settings. It replaces various controlmethods introduced in earlier Domino versions, such as the “Allow user to change settings on this tab” and “Apply this setting” (Don’t change, Always, Initially) options introduced in Domino 7. The new How to apply this setting option is a per-field setting. Possible value for this setting are:
Don’t set value.
Allow users to set their own value for the preference.
Set initial value.
Set an initial value for the preference, but then allow users to change and keep any newvalue they choose.
Set value whenever modified.
Set an initial value, allow users to change it, but then change the value back to the initialvalue whenever the user re-authenticates (usually after Notes client restart).
Set value and prevent changes.
Set a value and do not allow it to be changed by the user.

Wednesday, January 21, 2009

3 duplicate PUIDs found while initializing Domino Domain Monitoring

The server runs a special check on the Events4.nsf database to detect seplication conflicts or duplicate Event documents in Events4.nsf. This check is performed because any conflict or duplicate documents could cause problems with Domino domain monitoring. Additionally, there is a check performed to detect documents with duplicate PUIDs.
What is PUID?
Every probe document in DDM.nsf has an associated PUID (probe unique ID) and duplicate PUIDs could cause problems with Domino domain monitoring. If duplicate PUIDs are found, an event report document with the text X duplicate PUIDs found is generated and the console command to resolve the duplicates is provided. If any conflicts or duplicates are found, an Event report document is created in DDM.nsf, which by default provides a console command that can be used to resolve the problem:

"tell event delduppuids"

After dropping this command on the server you see the following response:

"Cleaning of duplicate DDM.NSF reports has completed. 3 documents were deleted."

You can also try to set Delete_Duplicate_Puid_Notes=1 in the notes.ini from your server.