Running Domino as Windows Service - reasons why?

HCL Domino Domino Forum
1

We have 5 Windows2000 servers all running Domino, and have been customers since release 3. I was asked today why we’re not running Domino as a service under Windows2000. I didn’t have a good answer other than: I like to see the server console on the screen, we’re never had a reason to change, and it seems like running Domino as a service is just something else to go wrong. Also, there may be times when I reboot the server that I don’t want Domino to automatically start.

Could you experienced Domino admins chime in please. What’s the real benefit of running Domino as a service?

This all came up because one of our new admins used Windows Terminal Services to reboot one of the servers, and of course (from his machine) didn’t see that Domino was running.

2

Subject: Running Domino as Windows Server - reasons why?

Good question… you can still see the Domino console when Domino runs as a Windows service. It provides OS-level management versus manually launching. e.g. you can force account logins when launching a server (or use default systems account), enable recovery options, debugging options, and more. It just integrates the Domino server (and all "n"tasks) into the OS-level management features. You can also run custom programs. If Domino was installed with default options, it is ready to start as a service now. “Lotus Domino…” shows up in the services list. Just change the start option to Automatic to start each time OS is started.

3

Subject: RE: Running Domino as Windows Server - reasons why?

As Michael said, the default for running as an NT Service is to use the “System Account” which allows “Allow service to interact with Desktop”. This makes the normal server console available.If you use a different login account then you will lose it.

There is no reason to use a different login unless your server needs to access network drives using UNC instead of mapped drives.

4

Subject: RE: Running Domino as Windows Server - reasons why?

If you need the server to recognize printer configuration, what do you need to do to start this service? When we launch an Excel Application (CreateObject) the application does not recognize any printers. Hope you can help! Thanks,Dana

5

Subject: Running Domino as Windows Service - reasons why?

Running as a service allows a little more control on disaster recovery.

You can configure the service to restart on an error, then reboot on a second occurance.

Also, Domino defaults to interacting with the desktop when running as a service, so you can see the console any time you’d like.

6

Subject: RE: Running Domino as Windows Service - reasons why?

Domino includes this feature: Automatically Restart Server After Fault/Crash

What’s the recommended setting on the Windows Service for “Recovery”, when combined with the Domino restart feature?

  1. Take No Action

  2. Take No Action

  3. Reboot the Computer

7

Subject: RE: Running Domino as Windows Service - reasons why?

This is an interesting question. The Service recovery option is only engaged if the service fails, but that’s not exactly what normally happens. When you run Domino as a service, the Domino Service Manager program (nservice.exe) is started. This program then launches Domino and waits for it to exit. I see 3 possible conditions:

  1. Domino exits normally: Service manager terminates normally.

  2. Domino crashes, fault recovery disabled: Domino server is terminated, and Service manager terminates normally

  3. Domino crashes, fault recovery enabled: Service manager restarts Domino and waits for it to exit. If it crashes again, repeat. If Domino crash rate exceeds the Crash Limits, do not restart Domino but terminate the Service Manager normally.

So I don’t see any way that Windows Service Recovery can be useful for Domino crashes, only if the Service Manager itself is having difficulties loading.