Installing the Nodinite Windows Server Monitoring Agent
Easily deploy the Nodinite Windows Server Monitoring Agent to unlock robust, real-time monitoring for your entire Windows Server landscape. This guide provides step-by-step instructions, highlights key prerequisites, and offers troubleshooting tips to ensure a seamless installation experience.
✅ Fast, guided installation with clear visuals and expert tips
✅ Ensure compliance and security with credential and privilege checks
✅ Troubleshoot common issues with actionable guidance and support links
Note
You must be a local administrator to install Windows Services.
Before you begin
Make sure you comply with the prerequisites.
Step 1: Start the installer
Double-click the MSI file to start the installation of the Nodinite Windows Server Monitoring Agent.
Start the installation by running the MSI file.
Step 2: Welcome screen
On successful execution of the MSI file, a Welcome screen is presented.
The Welcome screen confirms the installer has started.
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 3: Accept End User License Agreement
The Licensee is responsible for ensuring Nodinite products are used according to the End User License Agreement. Confirm you have the formal rights to install and modify the target environment before proceeding.
You must accept the terms in the License Agreement to continue.
Step 4: Custom setup
Select the components to install and choose the destination path for the installation.
Choose components and destination path. Default settings are recommended.
Click the 'Next' button to continue or 'Cancel' to quit the installer.
Step 5: Service Account Information
Enter the credentials for the Account to run the Nodinite Windows Server Monitoring Agent.
Depending on your connection string settings, this account will be used to log on.
Enter credentials:
- Domain: The name of the Domain the Server belongs to. If using a local account, use the server name or a dot (.) as Domain.
- User: The name of the account.
- Password: The password for the account.
Insufficient Privileges
If the account information does not meet prerequisites, you will see an error message:
Error message for insufficient privileges or incorrect account.
Click 'Next' to continue or 'Cancel' to quit the installer.
Insufficient privileges
Error message when provided account information does not meet the prerequisites.
Account is not allowed to run as a service or is not a local Administrator.
If you get this message, the most common reason is that the account is not allowed to run as a service or is not a local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure to enter valid credentials!
Tip
Check the local event log if there are errors (both System and Application).
Step 6: Ready to install
Once all preparations are complete, click 'Next' to continue or 'Cancel' to quit the installer.
Here's an example of the Ready to install dialog.
Step 7: Completed setup
The last step of the installation gives either a success or a premature exit.
Successful installation example
Installation completed successfully.
Failed installation example: A failed installation will render a premature exit.
Premature exit indicates a failed installation.
Click the Finish button to exit and quit the installer.
Step 8: Add Agent as a new Monitoring Agent Configuration
When the setup completes successfully, your default text editor will open a text file named 'README.txt'. This file contains additional information to help you add the agent as a [Monitoring Agent][]. The file is [re]generated on each successful start.
README.txt provides post-installation instructions.
Instructions on how to add the Windows Server Monitoring Agent as a [Monitoring Agent][] are detailed in a shared article. Click the link below to learn more:
Support
Contact our Support for additional guidance if you fail to resolve the installation problem.
Note
Additional troubleshooting information may exist in the Windows Event Logs.
Next Step
Configuration of the agent
Update
Related Topics
Add or manage a Monitoring Agent Configuration
Monitoring Agents
Prerequisites for Windows Server Monitoring Agent
Uninstall