running as a service
I seem to be having an issue with HM running as a service. I have set it up on a w2k server with SP2 and created a specific service account. I also set it up as a service. When I access it through Terminal server it starts and runs and I get alerts sent to me through pager and email. This is telling me that the service copy on the server is not running and or alerting. What do I do so that it will run on its own when the server is not logged in?
I am not quite sure I understand the problem. Do you mean HM does not do anything until you login to the system? And it starts send e-mail only after login?
Its strange because if you start HM as a service, it doesn't know anythink about user session and must work independently of user session. May be I understand you wrong?
Regards
Alex
Its strange because if you start HM as a service, it doesn't know anythink about user session and must work independently of user session. May be I understand you wrong?
Regards
Alex
>But when I log in again and start HM
Why do you start HM again? Was HM installed as a Win32 service? Or you start HM as regular application? If you start HM as regular application (or if you start HM from Startup group), Windows will unload the program every time you logged off. To install HM as service, use command line parameter "/InstallService". HostMonitor will display message like "service installed" and you will see "Advanced Host Monitor" item in the list of services installed on your system.
Regards
Alex
Why do you start HM again? Was HM installed as a Win32 service? Or you start HM as regular application? If you start HM as regular application (or if you start HM from Startup group), Windows will unload the program every time you logged off. To install HM as service, use command line parameter "/InstallService". HostMonitor will display message like "service installed" and you will see "Advanced Host Monitor" item in the list of services installed on your system.
Regards
Alex
-
- Posts: 3
- Joined: Mon Nov 18, 2002 6:00 pm
- Contact:
-
- Posts: 3
- Joined: Mon Nov 18, 2002 6:00 pm
- Contact:
I have HM running under W2K as a service without problem. Before running HM as a service, I have done the following:
1. Created the user account for HM to start as a service (give it the 'logon as a service' and 'act as part of the operating system' privileges).
2. Log on as that same user to create the user profile.
3. Start HM (while running under the above user profile) and make sure it works fine.
4. Install HM with the /InstallService switch
5. Start the service.
HM will run fine, even odbc logging will work correctly (HM uses user dsn, which is not available for the system account). When you want to make modifications to HM, logon as the HM account and stop the SERVICE, start the APPLICATION and make your modifications. After saving, stop the APPLICATION and start the SERVICE. Then you can close your terminal service session and the service will continue to run.
For the last part I created two cmd scripts which will do it automatically for me and which I can start, using a shortcut on my desktop.
1. Created the user account for HM to start as a service (give it the 'logon as a service' and 'act as part of the operating system' privileges).
2. Log on as that same user to create the user profile.
3. Start HM (while running under the above user profile) and make sure it works fine.
4. Install HM with the /InstallService switch
5. Start the service.
HM will run fine, even odbc logging will work correctly (HM uses user dsn, which is not available for the system account). When you want to make modifications to HM, logon as the HM account and stop the SERVICE, start the APPLICATION and make your modifications. After saving, stop the APPLICATION and start the SERVICE. Then you can close your terminal service session and the service will continue to run.
For the last part I created two cmd scripts which will do it automatically for me and which I can start, using a shortcut on my desktop.
-
- Posts: 3
- Joined: Mon Nov 18, 2002 6:00 pm
- Contact:
If you use the same account for the service and for running the application, you will not loose any changes made by a terminal service session.
Don't forget that if you log on to the console, make changes and then use terminal services to stop the services, all changes will be lost unless you saved them while running on the console!
Don't forget that if you log on to the console, make changes and then use terminal services to stop the services, all changes will be lost unless you saved them while running on the console!
Normally, you do not have control over de console. That's why you use TS.
In that case NOT saving changes with the service, gives you full control over the application. So you know you're the one in control. In that case it is even usefull to turn of the system tray icon to prevent console users to start the service interface.
In that case NOT saving changes with the service, gives you full control over the application. So you know you're the one in control. In that case it is even usefull to turn of the system tray icon to prevent console users to start the service interface.