Prerequisites for the Nodinite Dynamics 365 Monitoring Agent
This page describes the prerequisites for successfully installing and running the Nodinite Dynamics 365 Monitoring Agent.
Instances of this agent should be installed close to Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)
The Nodinite Dynamics 365 Monitoring Agent is a Windows Service and is usually installed on the Nodinite application server.
Windows 2012 R2
|.NET Framework||.NET Framework 4.5.2 or later|
Cloud technologies are evolving fast and Microsoft deprecates older versions of their APIs and SDKs every now and then. Nodinite will always support the APIs SDKs supported by Microsoft. This means you need to update Nodinite and our Dynamics 365 Monitoring Agent from time to time.
Make sure to subscribe to our Release Notes
See the list of SDK/API calls
The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.
- Local named account or domain account (preferred).
- Access and run-time rights
- Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.
The Nodinite Dynamics 365 Monitoring Agent has both inbound and outbound communication:
- Between the Monitoring Service and the Dynamics 365 Monitoring Agent
- Between the Dynamics 365 Monitoring Agent and Dynamics 365 API (using the SDK)
- Between the Dynamics 365 Monitoring Agent and the Monitoring Database
The following ports must be allowed on the Windows server where the agent is installed and running:
|53||DNS||The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file)|
And further with local network installation (if you install on local machine then no traffic is outside the machine):
|8000||RPC||Communication is initiated by the Monitoring Service|
|443||HTTPS||Secure outbound traffic with the Dynamic 365 APIs using the SDK|
The Monitoring agent requires outbound ports to be opened. Since Nodinite is highly configurable, the actual ports in use may differ from what's being exampled here.
|53||DNS||The Agent needs to know where your other servers/services are (can sometimes optionally be solved with user-defined entries in the
|88||Kerberos||Review 'Microsoft Kerberos' user guide|
|135||DTC/RPC||This port is shared between many Windows Services|
|1433/...||SQL Server instance ports (multiple)||Depends on policies and settings on target environment. Please review the How to configure RPC dynamic port allocation to work with firewalls user guide|
The service account running the Dynamics 365 Monitoring Agent must have the following rights assigned:
- db_owner (required to apply DACPAC updates)
|RetrieveOrganizationsRequest||System User account||Registered users and logon history|
|QueryExpression - Audit.EntityLogicalName, Columns: objectid, createdon, operation, action, userid||Audit|
|QueryExpression - Workflow.EntityLogicalName, Columns: createdon, name, description, statecode, category, workflowid, activeworkflowid||Workflow|
|QueryExpression - Solution.EntityLogicalName, Columns: solutionid, uniquename||Solution|
|QueryExpression - SdkMessageProcessingStep.EntityLogicalName, Columns: createdon, name, description, statecode, introducedversion, mode||Processing step|