Novell Home

Running GroupWise Monitor as a Windows Service

Novell Cool Solutions: Tip
By Tim Malloy

Digg This - Slashdot This

Posted: 21 Feb 2006
 

There are a couple of factors to consider in running GroupWise Monitor as a Windows Service. Follow the section that works for your case, depending on whether GW Monitor is already installed.

Note: You will need a Windows OS and the Resource Kit from Windows install CD. You can download rktools.exe from Microsoft's website, which has the necessary files for creating this service.

One caveat to this created service: If Monitor is set to interact with the desktop and you close the window, Monitor will stop running. You will then have to stop and restart the service to get it running again. I only set it to interact with the desktop when I want to change a setting.

GW Monitor Not Installed

If GW Monitor is not installed, follow these steps.

1. Set up a secondary domain local to the Windows PC that you are running Monitor on. This must be a machine that is always running, so that domains can communicate. You can follow TID 10007559 - although it is for GroupWise 5.5 and 6.0, the process is the same. Make sure to use a drive as your path to domain that your Windows box has file access to when not logged in (e.g., C:\ drive).

2. Once the domain is running and connected to the rest of your GroupWise system, Install GroupWise Monitor using your local secondary domain as the domain that Monitor will connect to.

3. Make sure Monitor is set up and configured (thresholds, alert email addresses, etc.) the way you want it to run before moving to the next step.

4. Follow the instructions in the Microsoft KB article q137890 at: http://support.microsoft.com/kb/q137890/

This will set up GroupWise Monitor as a service on the NT/2000/XP machine. If you need to get to the Monitor console, just go into your service that you created and under the Log On tab make sure "Local System Account" is checked. Then check "Allow service to interact with desktop". This will also work with the domain service created when the secondary was created, so you can see the domain console.

GW Monitor is Already Installed

GroupWise Monitor is already installed and running, follow the steps below.

1. Set up a secondary domain local to the Windows PC that you are running Monitor on. This must be a machine that is always running, so that domains can communicate. You can follow TID 10007559 - although it is for GW 5.5 and GW6.0, the process is the same. Make sure to use a drive as your path to domain that your Windows box has file access to when not logged in (e.g., C:\ drive).

2. Once the domain is running and connected to the rest of your GroupWise system, edit the file in your monitor directory Monitor.xml. Change the local secondary domain as the domain that Monitor will connect to. In my case it was c:\gwmon\Monitor.xml. Edit this file with Notepad or your favorite text editor changing the line from <Home_Path Home="Path to current domain" /> to <Home_Path Home="Path to domain created in step 1 of this section" />

3. Follow the instructions in the Microsoft KB article q137890 at http://support.microsoft.com/kb/q137890/

This will set up GroupWise Monitor as a service on the NT/2000/XP machine. If you need to get to the Monitor console, just go into your service that you created and under the Log On tab make sure "Local System Account" is checked. Then check "Allow service to interact with desktop". This will also work with the domain service created when the secondary was created, so you can see the domain console.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell