Skip to main content

Updating Agents from the Console

Overview​

This article describes how to download, upload, and deploy Netwrix Change Tracker agent updates from the Hub console. When a new agent version is released, you can deploy it automatically from the console. The article also covers best practices for phased rollouts and troubleshooting common issues.

NOTE: For the most current agent update procedures and screenshots, refer to the official documentation: Agent Updates

IMPORTANT: Gen 7 Agent v7.0.0 reached End of Support on October 1, 2024.

Ensure all agents are upgraded to Gen 7 Agent v7.1 or later for continued support and security updates.

Prerequisites​

Before updating agents, ensure you have:

  • Downloaded the agent update files from the Netwrix customer portal:

    • Path: Netwrix > Members > Member Downloads > Latest Versions of Software and Support Information for Existing Customers > 01. Netwrix Change Tracker Gen 7 > Hub and Agent Downloads

  • Required files:

    • Netwrix Change Tracker Gen 7 Windows Agent Only Installer (.zip)
    • Netwrix Change Tracker Gen 7 Windows Agent Control File for Auto Updates (.upd file)

    IMPORTANT: Do not extract the zip files. Upload them to the Change Tracker console as zip archives.

  • Permissions: Administrator access to the Change Tracker console and IIS (for troubleshooting)

  • Linux agents only: The at command must be installed on Linux devices for automatic agent updates to function.

Security Considerations​

  • Update Integrity: The .upd control file cryptographically signs the update to prevent tampering.
  • HTTPS Communication: HTTPS encrypts all agent-to-Hub communication.
  • Scheduled Updates: Consider deploying during maintenance windows to minimize disruption.
  • Network Security: Ensure only authorized agents can access the Hub (use IP restrictions or VPN if needed).
  • Credential Protection: Change Tracker encrypts agent credentials in HubDetails.xml.

Instructions​

Step 1 β€” Upload Agent Update Files​

  1. Log in to the Change Tracker console through a web browser.

  2. Navigate to Settings > Agent Updates.

  3. Click the Actions button and select Upload an Agent Update.

  4. In the upload dialog, select both files:

    • The agent installer .zip file
    • The agent control .upd file

  5. Click Open, then click Upload files.

  6. Verify that both files appear in the Agent Updates list.

Step 2 β€” Create or Select a Device Group​

For organized deployments, use device groups to control which agents receive updates and when.

  1. Navigate to Settings > Groups.

  2. Then, either select an existing group for the update, or click + Add to create a new group.

    NOTE: If creating a new group, provide a descriptive name that indicates the update phase or target devices (e.g., "Agent Update - Pilot").

Step 3 β€” Configure the Update Schedule​

  1. Navigate to the group you created or selected.

  2. Click the Agent Updates tab.

  3. Click + Define the update schedule.

  4. Configure the deployment:

    • Agent version: Select the uploaded agent version from the dropdown.
    • Schedule: Choose when the update should deploy:
      • Update Start: Specify when the change window should start i.e. from what time agents can start to update.
      • Update End: Specify when the change window should end i.e. from what time agents can no longer update.
    • Upgrade to .NET Core: Select this option if you are upgrading your agent(s) from Gen7 to Gen7NetCore. If this option is not selected for that type of upgrade, the upgrade will fail.

  5. Click Save to save the schedule.

Step 4 β€” Assign Agents to the Update Group​

  1. Navigate to Settings > Agents & Devices.

  2. Locate the device(s) you want to update.

  3. Click the Edit button for each device.

  4. In the Groups field, add the update group you configured (e.g., "Agent Update - Pilot").

  5. Click Save to save the changes.

The assigned agents receive the update according to the defined schedule.

NOTE: Linux devices require the at command to be installed for automatic updates to function. See at Command βΈ± Red Hat πŸ‘₯ for installation instructions.

Step 5 β€” Verify Update Deployment​

  1. Navigate to Settings > Groups.

  2. Navigate to the group you created. Review the Devices tab to monitor update progress.

  3. Verify that agents in the group show the new version number under the Agent Version column.

  4. Check that agents remain online and are communicating with the Hub.

NOTE: Agents temporarily disconnecting during the upgrade is expected, as the agent service will need to restart as part of the upgrade process.

Deployment Best Practices​

Phased Rollout Strategy​

For production environments, implement a phased rollout to minimize risk:

Phase 1: Initial Pilot​

  • Select 3-5 test devices representing different OS versions and configurations.
  • Create a group: "Agent Update - Pilot".
  • Deploy updates immediately.
  • Monitor agent status and logs before proceeding.

Phase 2: Early Adopters​

  • Select 10-20% of production devices.
  • Create a group: "Agent Update - Early Adopters".
  • Schedule updates during a maintenance window.
  • Monitor for issues before broader deployment.

Phase 3: Staged Production Deployment​

  • Deploy to remaining devices in batches.
  • Create multiple groups by department, location, or criticality.
  • Stagger deployments to manage risk.

Phase 4: Post-Deployment Verification​

  • Confirm all agents are updated.
  • Review agent logs for issues.
  • Document lessons learned.

Testing Checklist​

Before deploying to production, verify:

  • Agent update files uploaded successfully
  • Update schedule configured correctly
  • Test devices assigned to pilot group
  • Pilot devices updated successfully
  • Updated agents communicate with Hub
  • Policy templates apply correctly
  • Compliance reports generate successfully
  • Baseline data intact after update
  • Event collection functioning normally
  • Rolling logs show no errors

Rollback Plan​

If issues occur during deployment:

  1. Halt Deployment:

    • Remove devices from update groups.
    • Delete or modify the update schedule.

  2. Assess Impact:

    • Check affected agent rolling-log.txt.
    • Review Hub server logs.
    • Identify common failure patterns.

  3. Manual Intervention:

    • Uninstall problematic agent version.
    • Reinstall previous stable version.
    • Reconfigure HubDetails.xml if needed.

  4. Contact Support:

    • Gather rolling logs from affected agents.
    • Document error messages.
    • Open a support ticket with Netwrix Support.

Troubleshooting​

Upload Fails with "System Error / An Unknown Error Occurred"​

Symptom:

  • Upload fails with error: System Error: An unknown error occurred
  • Message indicates: "X File(s) failed to upload"

Cause: The default IIS maxAllowedContentLength is too low for agent update files.

Resolution:

  1. Stop IIS services:

    iisreset /stop

  2. Open the Web.config file:

    C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) Hub\Web.config

  3. Modify the <requestFiltering> node:

    <requestFiltering>
        <requestLimits maxAllowedContentLength="250000000" />
    </requestFiltering>

  4. Save the file and restart IIS:

    iisreset /start

  5. Retry the upload in the Change Tracker console.

Agents Not Receiving Updates​

Check:

  • Agent is assigned to the correct group
  • Update schedule is active and not expired
  • Agent can communicate with Hub (check agent status)
  • Agent has sufficient disk space for update
  • Review agent rolling-log.txt for errors

Verify:

  • Hub server has outbound connectivity (if agents are remote)
  • Firewall rules allow agent-to-Hub communication (port 443 by default)
  • Agent service is running on target devices

Update Fails on Specific Agents​

Common causes:

  • Insufficient disk space on agent system
  • Antivirus blocking update installation
  • Conflicting software or services
  • OS version incompatibility

Actions:

  1. Check agent rolling-log.txt for specific error messages.
  2. Verify OS compatibility with new agent version.
  3. Add Netwrix agent paths to antivirus exclusions.
  4. Free up disk space (minimum 500MB recommended).

Agent Goes Offline After Update​

Immediate steps:

  1. Check if agent service is running.
  2. Review rolling-log.txt for startup errors.
  3. Verify HubDetails.xml configuration is intact.
  4. Test network connectivity to Hub.
  5. Check Windows Event Viewer for service errors.

If agent will not start:

  • Reinstall previous agent version.
  • Verify .NET dependencies are installed.
  • Check for conflicting software.

Version Compatibility​

Agent VersionHub VersionRelease DateSupport Status
v7.1.xv8.0, v8.1Jan 2024+βœ… Supported
v7.0.0.xv7.x, v8.02017-2019❌ EOS Oct 1, 2024
v6.5.xv6.5, v7.xPre-2017❌ End of Life

IMPORTANT: Always verify compatibility in the release notes before deploying updates.

FAQ​

Q: How often should you update agents? A: Update agents when new versions address security vulnerabilities or critical bugs. Review release notes for each version.

Q: Can you schedule updates for specific times? A: Yes, use the schedule feature in the Agent Updates tab to specify deployment date and time.

Q: What happens if an agent is offline during the scheduled update? A: The agent will not receive the update. The agent needs to be online during the scheduled update time.

Q: Do agents need to reboot after updating? A: Typically no, the agent service restarts automatically. However, some updates may require a system reboot (check release notes).

Q: Can you cancel an in-progress update? A: Once an agent begins installing an update, you cannot cancel it. However, you can remove devices from the update group to prevent additional deployments.

Q: Where can you see the current agent version? A: Navigate to Settings > Agents & Devices. The Devices tab displays the version for each agent.