Step 5: Agents

Configure the Monitoring Agents and Log Agents that the installation package deploys. You assign agents to servers in Step 4: Servers; here you enter the settings of each agent. The Portal writes them into the package that you download in Step 6.

Example of the Portal Agents step in the Environment wizard.

Open the Agents Tab

Example of the Agents tab before you make any agent selections for the installation package.

Select and expand agents first

Select the server, then expand each agent card that is part of the package.

Use this sequence:

1. Filter and find the agent.
2. Expand the agent card.
3. Enter the base values in the order shown: Server, Port, Service domain, Service account.
4. Continue with the optional sections shown for that agent.

Which sections appear depends on the agent's runtime and capabilities:

Diagram: every agent card starts with the same base fields; the agent's runtime decides whether you see the gMSA options or the Agent Database fields. The BizTalk Server, Windows Server, Dynamics CRM, and IBM DataPower agents (orange) run on .NET Framework 4.8; all other Monitoring Agents and Log Agents run on .NET 10.

.NET 10 agents with gMSA support

For .NET 10 agents that support gMSA, configure the base fields first, then review the identity options.

Fields to review:

• Server
• Port
• Service domain
• Service account
• Advanced identity
• Use preview version
• Use gMSA
• Auto-generate certificate

If Use gMSA is enabled, make sure that the account and domain prerequisites are met; see gMSA accounts. With gMSA, Auto-generate certificate doesn't apply: you manage the certificate externally and install it in LocalMachine as described in Install Certificates for gMSA.

Example of expanded agent cards where identity options, including gMSA-dependent settings, are available for selected agents.

.NET 10 agents without gMSA support

Some .NET 10 agents don't offer gMSA, but they can still need an agent database, for example the Azure Logic Apps agent.

Enter the settings in the order shown:

• Base fields: Server, Port, Service domain, Service account
• The optional identity section, if shown
• The database section, when available: Database type, the agent database connection string, and the option to prompt for the connection string during install

Use the prompt option when the connection string should be given at run time instead of stored in the Environment. Then pass it with --agent-connection-string, the NODINITE_AGENT_<TYPE>_CONNECTION_STRING environment variable, or the CLI prompt (Step 7: passing arguments).

For connection string formats, permissions, and deployment patterns, see Agent Database.

Example of the Azure Logic Apps agent configuration entry with agent-database fields, including database type and connection-string behavior.

.NET Framework 4.8 agents

The BizTalk Server, Windows Server, Dynamics CRM, and IBM DataPower agents run on .NET Framework 4.8; install .NET Framework 4.8 on their servers (Prerequisites). The same base pattern applies, but the gMSA and database options depend on the agent.

For each .NET Framework 4.8 agent card:

• Enter the base host and identity values first.
• Configure gMSA only when the card shows it.
• Configure database settings only when the card shows them.

When a database section is available, follow Agent Database for rights, SQL connectivity, and update behavior. When gMSA is available, follow gMSA accounts before you generate the package.

Example of the agent-card layout; each agent shows only the fields that it supports.

What to configure for all variations

• Select each required agent.
• Assign a unique port to every agent, and open it in the firewall for the Monitoring Service (Network and Firewall Overview).
• Provide only the settings shown for that agent.
• Keep the identities consistent with the service identity decisions in Step 4: Servers.

Important Notes

• The MCP Server is a Core Service, not an agent: from 7.4.0, every Environment includes it, and you set its port in Step 4: Servers.
• Monitoring Agents that the Monitoring Service can't reach directly, such as agents in another network, use Service Bus Relaying. The v7 relay connection string format differs from v6; the old SharedAccessKeyName=...;AuthenticationKey=... format is obsolete.
• Validate the gMSA and database prerequisites before you generate the package.
• More about agent installation: Installing Monitoring Agents and Installing Log Agents.

Next Steps

• Step 6: Review and Download
• Step 4: Servers

Related Topics

• Install Nodinite v7
• Installing Monitoring Agents
• Installing Log Agents
• Agent Database
• gMSA accounts
• Service Bus Relaying
• MCP Endpoint
• Why do Nodinite use port 8000 - IIS-hosted agent ports vs Windows Service agents