We run Host Monitor as a service. Multiple users often want to log in and through the GUI check status of tests or edit tests. The web interface does not offer as much functionality as we would like for editing or viewing tests as yet so this is not currently an option (I'm sure this would change, HM is a great tool). We would also like to avoid stopping and starting the service since if we open the GUI with the default install a monitor going bad would send duplicate alerts.
So the question is if I create a second copy of the .exe folder (I've tried this and it works) with the hostmon.ini variable set to Start=0 while pointing to the same .hml file that the service is using, is this a clean way to allow users to check tests and to update them (recognizing that the service would need to be restarted to pick up changes)? If not what suggestions would you have?
Multiple Users
Its not good solution. If you start second instance of HostMonitor, make changes in HML file and then restart service, you will keep all settings but lose some statistical information.So the question is if I create a second copy of the .exe folder (I've tried this and it works) with the hostmon.ini variable set to Start=0 while pointing to the same .hml file that the service is using, is this a clean way to allow users to check tests and to update them (recognizing that the service would need to be restarted to pick up changes)? If not what suggestions would you have?
Better solutions:
- if users log in locally or users access HostMonitor's system using tools like PC Anywere, they should see HostMonitor's icon in system tray (if service configured properly). Click on icon and make any changes you want.
- if users connects to remote system using MS Terminal Service, you should stop service, start HostMonitor in application mode and start service when changes saved.
You may create simple BAT file that will stop service, start HostMonitor in application mode and (after you change settings and terminate application) start service again.
Code: Select all
net stop hostmonservice
"c:\program files\hostmon\hostmon.exe"
net start hostmonservice If you stop service before you start application and application is started under account with necessary rights (e.g. the same account you are using for the servcie), a monitor will not "goind bad" and will not send any alerts.We would also like to avoid stopping and starting the service since if we open the GUI with the default install a monitor going bad would send duplicate alerts.
Regards
Alex
Use Remote Desktop to Manage Hostmonitor Remotely (console)
Note: This only works if hostmonitor is running on Windows Server 2003
Another option (the one we currently use) is to use remote desktop and connect to the console (shadow the console session). This only allows one person to connect at a time but it does not cause any conflicts with hostmonitor. Just make sure each person IS connecting to the console and not just the standard way. Either use the Remote Desktops plug-in for the MMC and check the "connect to console" option or execute the following from the command line.
mstsc -v:servername /F -console
See the microsoft article below for more information.
http://support.microsoft.com/default.as ... -us;278845
Another option (the one we currently use) is to use remote desktop and connect to the console (shadow the console session). This only allows one person to connect at a time but it does not cause any conflicts with hostmonitor. Just make sure each person IS connecting to the console and not just the standard way. Either use the Remote Desktops plug-in for the MMC and check the "connect to console" option or execute the following from the command line.
mstsc -v:servername /F -console
See the microsoft article below for more information.
http://support.microsoft.com/default.as ... -us;278845