How to receive notification when users enable 'Full Access Administration' mode

Problem

You would like to receive a notification when Administrators enable "Full Access Administration" mode. How can this be done?

Solution

You can accomplish this by creating an Event Notification in the Monitoring Configuration database (EVENTS4.NSF), following the steps below: 1. Open the Monitoring Configuration database, expand the "Event Handlers" folder, and select the "By Server" view. 2. Click "New Event Handler". 3. On the Basics tab, select the server to monitor, and specify the notification trigger "Any event that matches a criteria". 4. On the Events tab, specify the "Criteria to match" options as follows: Select "Event can be any type", Select "Events can be any severity", and Select "Events must have this text in event message" and specify the text "full administrator access", without the quotes. 5. On the Action tab, specify a notification method. For example, select "Mail" and enter the email address to which emails should be sent when administrators enable "Full Access Administration" mode. 6. On the Action tab, select "Enable this notification". 7. Click "Save & Close". Notifications will also be generated if users are denied access when they attempt to enable "Full Access Administration" mode.

Renaming Users with the Administration Process (AdminP)

IBM - Frequently Asked Questions - Renaming Users with the Administration Process (AdminP): "Can you change the default 21-day limit to something else? Sure. A complete description of how to accomplish that is documented in the Domino Administrator Help, but in the 'Rename Selected Notes People' dialog box, the number of days you want to honor the old name is listed. The default is 21 days, however, you can change that setting to any number between 14 and 60."

Renaming Users with the Administration Process (AdminP)

IBM - Frequently Asked Questions - Renaming Users with the Administration Process (AdminP):
"What happens if the user never logs in during the 21 day time period? Prior to Domino 6.5.4, the name will revert back to the original name if the user does not log in, or if the process fails to complete for some reason. Starting in Domino 6.5.4, however, a Domino administrator must approve name change reversions, so this reversion will no longer occur without an administrator's knowledge."

What is Lotus' recommended Upgrade Path for lotus 8?

In all cases, it is important that you follow the upgrade guidelines to ensure minimum feature loss with Mail and Calendaring & Scheduling.

1. Upgrade the Notes clients that administrators will use to edit and operate on the Domino Directory.
2. Upgrade the Domino Directory first (this is done by upgrading the Domino server that is the Administration Server of the Domino Directory to Domino 8.0 first).
3. Replicate the Domino Directory to the other servers.
4. Upgrade the Hub servers.
5. Upgrade the Mail servers.
6. Upgrade the SMTP servers.
7. Upgrade the Web servers.
8. Upgrade the Application servers.
9. Any third-party/companion product server (check for Notes/Domino Release 8.0 readiness).
10. Upgrade the general population of clients to Notes 8.0.
11. Replace the design of any databases/mail files with any new Notes/Domino Release 8.0 design changes last. For mail files, the Convert task should be used on the server to change the design of the mail file.

Incomplete NSD after a Domino server crash

Question

Your Domino® server crashes and the NSD file is incomplete. The NSD will stop after running some time without any error message. When run manually. NSD does run to completion successfully.

Cause

In the Server document -> Basics tab -> Cleanup Script / NSD Maximum Execution Time field is set to 600. Even though the faulty recovery is not enabled, the Cleanup Script /NSD Maximum Execution Time does apply to automatic NSD. In this case, nsd ran for 600 seconds and is being terminated, resulting in NSD terminating prematurely. In Domino server 6.5.5, the auto nsd did finish in about 1 minute, even with the Cleanup Script/NSD Maximum Execution Time set to 30. (Faulty recovery not enabled) This feature is to prevent nsd from running for too long to hinder Domino server restart. However, for some busy servers, it takes more than the default 5 minutes to finish. NSD needs to complete in order to troubleshoot the issue.

Answer

Increase Cleanup Script /NSD Maximum Execution Time from 600 to 1800. This field range is from 30 to 1800. This will increase the time the Domino server is down from 600 seconds to 1800 seconds. In most cases, a complete nsd is required to determine the root cause of the issue.