Updating the Microsoft Dynamics 365 Logging and Monitoring agent
Keep your integration environment secure and efficient by updating the Nodinite Microsoft Dynamics 365 Logging and Monitoring agent. This guide walks you through a seamless update process, highlights compatibility tips, and ensures you benefit from the latest features and fixes.
This guide teaches you how to update the Microsoft Dynamics 365 Logging and Monitoring agent.
Release Notes
Stay informed about the latest improvements! Visit the release notes for the Microsoft Dynamics 365 Logging and Monitoring agent for details on new features, enhancements, and bug fixes.
Running Version
You can check the installed version in the 'Version' text box.
The version is displayed in the README.txt file.
Alternatively, view the file details property on the local installation:
File version property in Windows.
PreReq: Ensure you have already installed the Microsoft Dynamics 365 Logging and Monitoring agent before updating. The service account must have Logon as Service Right. See prerequisites for Microsoft Dynamics 365 Logging and Monitoring agent for more information.
Note
You must be a local administrator to install or update Windows Services.
Compatibility and Versioning Issues
- For major upgrades (4.X → 5.X), review Updating from V4 to V5 for important compatibility notes.
Update Guide
Follow these steps to update the Microsoft Dynamics 365 Logging and Monitoring agent.
Step 1: Start the Installer
Double-click on the MSI file to start the update process of the Nodinite Microsoft Dynamics 365 Logging and Monitoring agent.
Double-click the MSI file to begin.
Step 2: Welcome Screen
Upon successful execution of the MSI file, a Welcome screen is presented.
Welcome screen of the installer.
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Step 3: Custom Setup
Select features and the location to update.
Choose the components and installation path.
Default settings are recommended
Note
If you change the location, your old configuration will be lost
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Step 4: Service Account Information
Enter the credentials for the Account to run Nodinite Microsoft Dynamics 365 Logging and Monitoring agent.
Domain: The name of the Domain the Server belongs to. If a local account is being used, use the name of the server or a . (dot) as Domain
User: The name of the account
Password: The password for the account
Enter the service account details.
Note
The account must have 'Log on as Service Right'
Click the 'Next' button to continue with the update process or click the 'Cancel' button to quit the installer.
Insufficient Privileges
Error message when account information does not meet Prerequisites.
Insufficient privileges error message.
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 5: Ready to Install
Now all preparations are performed, Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Review your settings and click Next to install.
Step 6: Completed Setup
The last step of the update process gives either a success or a premature exit.
Successful update example.
Click the 'Finish' button to Exit and quit the installer (update process).
When the setup has finished your default text editor will open a text file named the 'README.txt'. The README.txt file holds the information that you need to setup and manage the agent as a Monitoring Agents for Nodinite.
The README.txt file opens automatically.
Instructions on how to add the Microsoft Dynamics 365 Logging and Monitoring agent as a Monitoring Agents is detailed in a shared article, click on the link below to learn more:
Troubleshooting
A failed update will render a premature exit.
Failed update example.
Support
Contact our Support for additional guidance if you fail to resolve the update problem.
Note
Additional information to aid the troubleshooting may exist in the Windows Event Logs.
Next Step
Configure
Add or manage a Monitoring Agent Configuration