KS-Soft

Posted: **Tue Dec 16, 2003 3:30 pm**

Due to some techical problems you cannot check HostMonitor that installed as service on remote system using Terminal Service (services cannot display information on remote system because Terminal Service provides handle of the remote desktop to applications that started AFTER terminal service session was open).

If you need to configure HostMonitor on remote server using Terminal Service, we would recommend to 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

Posted: **Sun Jun 27, 2004 10:35 am**

Posted by mpriess (http://www.ks-soft.net/cgi-bin/phpBB/pr ... ofile&u=94)

Another option (works if hostmonitor is running on Windows Server 2003) 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

Posted: **Wed Sep 28, 2005 1:03 pm**

Since version 5.60 Advanced Host Monitor provides another solution - Remote Control Console (RCC).
http://www.ks-soft.net/hostmon.eng/rcc/index.htm
With RCC you don't need to use Terminal Service at all.

Regards
Alex

KS-Soft

HostMonitor as service and Terminal Service

HostMonitor as service and Terminal Service