KS-Soft

How to move software to another system

Update check

1a) if you plan to update software, please check if your registration codes valid for latest version (HostMonitor menu Help->Update check)
1b) order license update if necessary

Prepare new system:

2a) if you are using RCC (Remote Control Console) and/or Active RMA agents, open TCP ports on new system firewall so RCC and agents will be able connect to new HostMonitor (please check settings on old systems using Options dialog - you could set any TCP ports for such services, e.g. 5054 for RCC and 5056 for Active RMA)
2b) if you are using ODBC Query tests or ODBC logging you should setup the same ODBC source on new system. Note: use 32-bit ODBC Data Source Administrator (e.g. C:\WINDOWS\SysWOW64\odbcad32.exe).
2c) install HostMonitor on new system
2d) stop HostMonitor on old system

3a) start new HostMonitor
3b) apply registration codes using menu Help->License->Register Now
3c) stop new HostMonitors;

4a) copy ALL config files at once - copy all *.HML, *.LST, *.INI files from old system to new one;
(see list and notes below)

4b) if you set new path to config files different from old one, use any text editor to find&replace paths in INI files;
4c) if you are using some custom scripts or 3rd party tools for External tests or Shell Script tests, copy these scripts to new system as well

Notes:
- usually config files stored in C:\ProgramData\HostMonitor\ (%ProgramData%\HostMonitor\) folder unless you set different folder during installation;
- its not a good idea to use C:\Program Files\ folder for config files on modern Windows systems, so you may use default installation options (%ProgramFiles%\HostMonitor folder for .exe modules and %ProgramData%\HostMonitor folder for config files); or you can use single folder like C:\HostMonitor\ for exe and config files)

5) start new HostMonitor
6) if new path to config files is different from old one, check your settings using Options dialog, Report Manager, Action Profiles (check path to external header/footers for reports, path to sound files, path to reports and attachments)
7) use Auditing Tool (menu View), it may detect various system and configuration related problems
8.) make sure HostMonitor works correctly, loads profiles and test list, accepts Active RMA and RCC connections (if you are using such components)
9) then you may install HostMonitor as service (hostmon.exe /InstallService)

External programs setup

9) if you are using Passive RMA agents on remote systems, you may need to adjust firewall settings on remote systems where RMA is running (allow connections from new HostMonitor IP); and may be RMA settings (agent may filter incoming IP addresses as well)

10) if you are using Active RMA, you will need to change IP address of HostMonitor and RMA Manager on agents side; also check IP address filter used by Active RMA Server on HostMonitor side (Options dialog)

Note: RMA Manager allows to setup settings for many RMA agents at once.

11) Also, you may need to start Telnet Service and Web Service applications (or install services; if you are using such services on old system).


Problems?

If you did not read this instructions, copied some files from old system but missed other files and started new HostMonitor used mixed config files (some from default installation, some from your old system), then please start everything over from step #3c
3c) stop new HostMonitors;
4a) copy ALL config files at once - copy ALL *.HML, *.LST, *.INI files from old system to new one. Yes, copy ALL config files again (including files you copied before)
- ...

you should copy files like
*.HML file(s) with tests
hostmon.ini
logsman.ini
logvisualizer.ini
rcc.ini
rma_mgr.ini
telnetservice.ini
actions.lst
agents.lst
connlist.lst
deftemplates.lst
holidays.lst
hostinfo.lst
hostname.lst
larep.lst
macdb.lst
MailList.lst
mibdata.lst
mibtree.lst
odbclogs.lst
Palettes.lst
pglist.lst
prbypass.lst
proxies.lst
RepPList.lst
rsyslog.lst
schedule.lst
services.lst
snmpacc.lst
snmpacc2.lst
sscripts.lst
ttemplates.lst
udvmacro.lst
users.lst
WebService\webservice.ini
WebService\wcolors.lst
WebService\wsuserprof.lst
..
Optionally you may copy *.SDR files, log and report files.

Notes:
- some files could be missed if you are using old version of HostMonitor;
- some files could be missed if you are using limited version of HostMonitor (e.g. Starter or Professional package)


Backup/Restore

You may copy files to new system using Backup folder. Please make sure your have up to date backup copy or create one using "Backup right now" option, copy files to new system into Backup folder, use Restore option on new system
https://www.ks-soft.net/hostmon.eng/mfr ... htm#backup

How to move software from Windows 2000/XP/2003 to Windows 7 or Windows Server 2008

If you move software from Windows 2000/XP/2003 to Windows 7/2008, there is one problem - old versions of HostMonitor stored configuration files in %ProgramFiles% folder.
Now its not a good idea to use c:\program files\ or c:\program files (x86)\ folder for data files (especially when Windows UAC is enabled) because Windows offers new options for better security. But there is sideeffect - to keep legacy applications running, Windows Vista+ lets them pretend to write to their familiar file locations but when you go to look for those files, you won't find them! Vista actually stores the files in a "Virtual Store" under the AppData store in your user folder.
Please check the following post for additional notes.

Its better use c:\programdata\HostMonitor\ or any other folder that is not affected by Windows data redirection (e.g. C:\HostMonitorConfig\).
Default installation path for data files %programdata%\HostMonitor\ (usually this is C:\programdata\HostMonitor\ folder)

This means you may need to check your settings and change some paths: path to log file, path to reports, path to external report headers (if you are using any).

The following notes relate to Advanced Host Monitor version 9 on Windows Vista or newer Windows system

If you are using Windows Vista or newer Windows system, UAC is enabled and you setup software using separate application/data folders then most applications disable virtualization.
In addition to HostMonitor and RMA Manager (these applications disable virtualization since version 7), the following modules were modified:
- MIB Browser
- Log Analyzer
- Log Visualizer
- Web Service
- Telnet Service
- WatchDog
- ProcessMeter
- WMI Explorer
- HML Manager

If you install/update software using single destination folder, software will work as before. This way existing installations of the software will not change behavior.

RMA for Windows modules were modified as well but work differently:
- if you install new copy of RMA using setup program, it will disable virtualization;
- if you update existing old RMA installation using setup program or RMA Manager, it will keep current settings (in such case rma.ini file can be virtualized depending on UAC settings and installation folder location).
Note: you may enable/disable virtualization for RMA agent using the following registry key:
- on 32bit Windows: HKLM\Software\KS-Soft\HostMonitor\RMAVirtualizationOff
- on 64bit Windows: HKLM\ Software\Wow6432Node\KS-Soft\HostMonitor\RMAVirtualizationOff