Doing a manual uninstall of Lotus Notes 8.5.3

Disclaimer: I cannot be held responsible for the damage or loss of data resulting from this post. This post is provided for educational purposes.

The following link explains how to manually uninstall Lotus Notes. This is a last resort if you can't uninstall your client through add/remove or program and features.

Link

Below is quote of the instructions:


To clean a Notes or partial Notes install from your Microsoft^® Windows^® client, complete the following procedure:

1. Delete all folders in the Notes \ except the \data folder.
2. Back up the Notes \data folder and then delete all subdirectories in \data. Do not delete any root-level files from the Notes \data folder.
3. If Notes appears in your Add/Remove Program panel, run the Windows installer cleanup utility located at Microsoft Help and Support.

However it doesn't explain how to remove the Lotus Nodes Diagnostics and the new Lotus Notes Smart Upgrade service from your windows services.

This is where the sc command comes in handy. To remove the Lotus Notes Diagnostics service, first make sure the services are not running ( actually you need to make sure they are not running when you follow the steps in the link above ) Next open a command prompt and issue the command:

sc delete "Lotus Notes Diagnostics"

and you should get a response:

[SC] DeleteService SUCCESS

The double quotes are required. However when you do the same for the Lotus Notes Smart Upgrade Service

sc delete "Lotus Notes Smart Upgrade Service"

you get the error:

[SC] OpenService FAILED 1060:


The specified service does not exist as an installed service.

Even doing a

sc query

you can't find the service name but it shows in your services.
To fix this, right click on the Lotus Notes Smart Upgrade Service and go to properties. Take note of the service name. It says LNSUSvc. Now try:

sc delete LNSUSvc

and that works with [SC] DeleteService SUCCESS


That is it. Hope this helps someone out there!

Converting users from OOO agent to OOO service

Converting from Agent to Service Out Of Office ( OOO ) is pretty simple on the configuration side. A few things to remember before you change your mail server to Out of Office Service:

1. All mail users need to have Lotus Notes 8.x or above installed
2. All mail users need to have Lotus Notes 8.x or above mail templates
3. The Lotus Domino directory on the mail servers must have the new 8.x or above design template applied
4. All servers in a domino domain that are mail servers, included clustered servers, must have steps 2 and 3 complete
5. All servers in a domino domain that are mail servers, included clustered servers, must have their configuration documents setup for Out of Office Service. After this is configured, the server must be restarted for the OOO Service to work.


To setup the Out of Office Service on a server, open the server configuration document, go to Router/SMTP > Advanced > Controls. Under the Miscellaneous Controls heading and Out-of-Office type: change from Agent to Service

After this setting is configured, the server must be restarted for the Out of Office Service to work.

In one instance, after the server was configured and restarted, I had issues with existing OOO agents still running. I figured out that before the OOO Service was turned on, the users already enabled their OOO using the agent. Also, the users didn't have manager access to their mail files so when they enable and disable their OOO, an adminp request was generated. Here are the following steps I took to convert them to the OOO Service

First I opened the user's mail file ACL. I explicitly put my name in the ACL and gave myself manager access. Then I made myself the mail file owner through mail preferences. Close the mail file ( you might have to close all Lotus Notes windows ) and re-open

Next I opened the user's OOO preferences. I made a note of when they left and when they are coming back. This is important because we will disable their OOO and re-enable it.

Next I disabled the user's OOO.

Then using my admin client I opened the user's home server ( just so happens the user's home server is the administration server too ) and submitted a console command:
tell adminp process new

I waited a few minutes and went back to the user's mail file. Then I enabled their OOO using the dates I recorded before I disabled it.

Next I checked the admin client under Server > Status > Schedules > Agents, to see if the agent is still scheduled ( Also doing a tell amgr schedule to see the OOO schedule and see who is still running the agent OOO ). The status should show the OOO agent still running.

Next I disable that same user's OOO

Next I waited for agent to disappear from the Agents view in the admin client ( or from the amgr schedule )

Finally I enabled the user's OOO again. You can submit the command "tell router O" to display the active OOO users using the OOO Service. Verify that you see that user's OOO. At this point I changed the mail file owner back to the user, and removed myself from the ACL as manager of the mail file.


It might seem like a lot of disabling and enabling of the OOO but I had to do this for 12 people and this was the only process that worked for me.

References:

The IBM Lotus Notes and Domino Out of Office service: Best practices

Designating the Out of Office service type