No, the new installer should recognize a previous installation, remove it and install the new one.

No, HealthMonitor includes an internal reloader.

The "AppConfig.Config" file (in the HealthMonitor website directory) is modified during installation. Please check that this file can be modified by the Network Service account (IIS 6.0) or by the ASPNET account (IIS 5.0); if not, change their permissions as appropriate. Check also the "HMLogger\Configuration" subfolder: it must be writable too.

The activation keys are written in the The "AppConfig.Config" file (in the HealthMonitor website directory). Please check that this file can be written by the Network Service account (IIS 6.0) or by the ASPNET account (IIS 5.0); if not, change their permissions as appropriate.

You can install IIS from "Control Panel"-->"Add/Remove Programs". Please choose "Add/Remove Windows Components", select "Application Server" and click the "Details" button; select "Internet Information Services" and click "Details" again; make sure that the "World Wide Web Service" option is checked. Press "OK" and "Next" to complete installation.
You can download an example here.

This error may occur when the ASP.NET Extensions are missing or prohibited in Internet Information Server.

1) Please check that ASP.NET extensions are installed in IIS: open IIS Manager and reach the "Web Service Extensions" section: "ASP.NET v2.0.50727" should be listed here. If it is not listed, you can install it by issuing the command "aspnet_regiis.exe -i -enable" at the command prompt.
You can download an example here.

2) If ASP.NET extensions are installed, please check that they are enabled. You can do that in IIS Manager: reach the "Web Service Extensions" section, select "ASP.NET v2.0.50727" and click the "Enable" button.
You can download an example here.

This error occurs when the ASP.NET Extensions are prohibited in Internet Information Server.
You can enable them in IIS Manager: reach the "Web Service Extensions" section, select "ASP.NET v2.0.50727" and click the "Enable button".

This could occur if you didn't enable ASP.NET 2.0 within the HMWeb Virtual Directory.

Enable the .NET Extensions on IIS.

Check that appropriate permissions are set on the HealthMonitor Web Interface website directory (read permissions for the Internet Guest account)

HealthMonitor 5.0 and higher work on Vista. Version 4.0 works on Vista, but you need to right-click on Interface.exe and select "Run As Administrator".

This is due to the ASP.Net configuration. If you are using ASP.Net 2.0, make sure that the Windows account used for ASP.Net has permissions to access the metabase. The IIS Registration Tool in ASP.Net (%Systemroot%\Microsoft.NET\Framework\v2.0.xxxxx\aspnet_regiis.exe) with the ga option allows you to set this configuration. For example, the following command grants authorizations to the Windows user ASPNET in the IIS metabase:

aspnet_regiis –ga ASPNET

For a different solution, you can reconfigure ASP.Net like that:

aspnet_regiis –u (removes the ASPNET component in IIS)

aspnet_regiis –i (performs the ASPNET component installation in IIS)

You can meet this error when no ASP.NET version is selected in HMWeb Site/Virtual Directory (typically when the value is empty), please verify IIS configuration.
You also can try to reconfigure ASP.NET as explained in the previous FAQ.

To restrict access to the web interface, the easiest way is using the user and role management feature included in HealthMonitor. If you want to set restrictions independently of HealthMonitor, you can set the basic authentication on the "Config" subfolder in the HealthMonitor Web installation folder. You can do that in IIS: in IIS Manager, select the HealthMonitor website, select the "Config" directory, choose "Properties", "Directory security", disable anonymous access and enable basic authentication. You should do that on the "config" directory only, otherwise the clients won't be able to connect to the web interface.

Run the winmgmt /resyncperf command; it will reset the performance counter, and after that CheckTerminalServer should work properly.

Open the AppConfig.Config file in the HMWeb directory and look for the following line:

<add key="LoggingEnable" value="False" />

Please change "False" to "True" (you may have to restart IIS for that to take effect) and try installing again the HealthMonitor Client. HealthMonitor will generate a log file (\hmlogger\configuration\temp\log.txt), it may include useful information which can help you solve the problem you met.

This problem is explained in the Microsoft Support article MS 821268.
We suggest that you edit the "machine.config" file as described there.

Yes, but before installing HealthMonitor, make sure that the following components are installed:

1) IIS 6.0 Compatibility Pack
2) Crystal Reports 2008 (CRRedist2008_x86.msi) - required for HealthMonitor 6.2 and lower only.

HealthMonitor requires using the Classic .NET Application Pool. You have to change the settings in IIS Manager: select the HealthMonitor website, right-click, select "Manage Application"-->"Advanced settings" and change the Application Pool setting to "Classic .NET AppPool".

HealthMonitor Ticketer requires Windows Authentication, please check in IIS that it is enabled.

Please install Crystal Reports manually: you can download the installer here. to run correctly.
Crystal Reports is not required for HealthMonitor 6.5.

This is a Crystal Report issue. If Crystal Reports was installed by the HealthMonitor setup, please install the Crystal Report hotfix you can find at: ftp://ftp1.businessobjects.com/outgoing/CHF/crnet20win32x86_en_chf.zip

The space provided for the company logo in the reports is 45x45 px. Please check that your logo is not larger than that, otherwise it will be cropped.