Troubleshooting step when installation of Windows server monitoring agent is blocked/failed in Windows 2003
For security reasons, we currently use SHA2 certification in the agent's msi. Since Windows 2003 does not support this, the user needs to
install the related service pack.
Also, since we have updated our Site24x7 servers to higher cipher suite (AES), the server monitoring agents on Windows 2003 will not be able to communicate with our data center.
This issue can be resolved by
applying a hotfix, before migrating to AES. After installation of the service pack, try adding the server monitoring agent again.
For further assistance, contact support@site24x7.com
Related Articles
Error 2503 during Windows server monitoring agent installation
Issue Facing the error 2503 during the installation of the Windows server monitoring agent. Cause During installation, the installer package files have to be written to the "C:\Windows\Temp" folder. When Windows is unable to write these files to this ...
How to uninstall the Site24x7 Windows Server Monitoring Agent
Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...
Prerequisites for Java agent installation
For a smooth Java agent installation, ensure that you've fulfilled the following prerequisites. The environment should have Java version 8 or above installed. The application user should have full permissions over the agent directory. The server ...
List of log files generated and maintained by the Site24x7 server monitoring agent
Here is the list of log files generated by the Linux and Windows server monitoring agent. The log files are stored in the same directory where the agent source file is installed. By default they are at: For Linux : ...
Prerequisites for Node.js agent installation
For a smooth Node.js agent installation, ensure that you've fulfilled the following prerequisites. The environment should have node version 16.20.2 or above installed. The application user should have full permission to access the agent directory. ...