How to set up GroupWise Monitor 2012 to start with the computer on Windows Server 2008 R2
By Bruce Perrin
GroupWise monitor 2012 cannot be run as a service (as of this writing). The work around for this is to use Windows Task Scheduler to start the application when the machine starts up.
Install GroupWise monitor on a Windows server in accordance with the instructions in the GroupWise 2012 installation guide. Once GWMonitor has been installed and tested, set up Windows task scheduler to run the program at startup.
- Open Windows task scheduler
- Under the action menu, select create task
- Give the task a name (I called mine Start GWMonitor)
- Give the task a description (optional)
- Click on "Run whether user is logged is logged on or not"
- Click on the "Triggers" tab, click on "new"
- In the "Begin the task" box select "At startup", click "OK"
- Click on the "Actions" tab, click on "new"
- Make sure the "Action" box says "Start a program"
- Next to the "Program/script" box click the "Browse" button
- Browse to the location of the GWMonitor executable (example "C:\Program Files (x86)\Novell\GroupWise Server\Monitor\gwmon.exe")
- Click "OK"
- Click on the "Conditions" tab
- Unclick the "Stop if the computer switches to battery power" box, click "OK"
- Click on the "Settings" tab
- Check the "Allow task to be run on demand", "Run task as soon as possible after a scheduled start is missed", "If the task fails, restart every (set an interval)", and the "if the running task does not end when requested, force it to stop" boxes.
- Click "OK"
- You will be prompted for local credentials. We gave the task the credentials of an administrative user.
- When the task scheduler shows the list of tasks, right click your newly built task, and click "Run".
Verify the task was successful by highlighting the task and then selecting the "History" tab.
You should now be able to browse to the GWMonitor web page.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.