We’re excited to announce our upcoming major release ITarian Platform, and agent updates! 
This release will be deployed over two days, with each rollout lasting approximately 4 hours . No downtime is expected , but please reach out if you experience any issues following the update.
Release Schedule
Platform Updates
- US Region Portals: September 16, 2026 – 03:00 AM (EST)
- EU & IN Region Portals: September 17, 2026 – 08:00 AM (GMT) / 01:30 PM (IST)
Agent Updates (All Regions)
- September 17, 2026 – 01:00 AM (EST) / 06:00 AM (GMT) / 11:30 AM (IST)
ITarian Platform
What’s in This Release
WHAT’S NEW
Policy Management
► New Policy Management Experience for Centralized Endpoint Policy Control
What you can see: A redesigned Policy Management screen gives you an at-a-glance overview of all your endpoint policies, with summary cards showing Total Policies, Total Recommendations, and Associated Devices, plus filters by Status, Recommendations, and OS.
What you can do: Create policies for any platform — Windows, macOS, Linux, Android, or iOS — import existing configurations, and manage all policies from a single list view. Within each policy, a structured left navigation lets you configure Security Operations and IT Operations settings in one place, with options to clone, set as default, export, or delete.
Why it matters: Managing endpoint security policies across a mixed-OS fleet is now faster and more organized — administrators have full visibility into policy health and gaps across their entire estate from a single, consistent interface.
Access Control
► IP-Based Login Restriction Now Available for Enhanced Account Security
What you can see: A new IP Access Control section is now available under Account Management, allowing you to define a list of approved IPv4 addresses permitted to log in to the platform. Per-role enforcement is configurable under Role Management.
What you can do: Upload a CSV of approved IP addresses or add them manually, then enable IP restriction on a per-role basis. Users in roles with restriction enabled can only log in from the approved addresses — anyone attempting access from an unlisted IP sees a clear message to contact their admin.
Why it matters: For organizations that need stronger access controls beyond two-factor authentication, IP-based login restriction adds a critical layer of security by ensuring platform access is only possible from known, approved network locations.
Client Security
► Centralized Control for Firewall Driver Detection in Profile Settings
What you can see: A new “Detect disabled firewall driver in network adapter settings” checkbox is now available on the Firewall Settings tab within profile configuration.
What you can do: Administrators can enable or disable this firewall driver detection setting centrally via profiles and push it across all associated Windows endpoints — no more per-device manual configuration.
Why it matters: For teams managing large endpoint fleets, this provides consistent, scalable enforcement of firewall driver monitoring behavior without requiring individual endpoint-level intervention.
EXDR
► Bulk Installation Now Supports EXDR Agent Deployment
What you can see: The Bulk Installation Package now includes a Comodo EXDR Client option under the Windows tab, allowing the EXDR agent to be bundled alongside other components in a bulk install package.
What you can do: Select the EXDR Client in your bulk installation package to automatically deploy the configured default version to endpoints. Where version flexibility is enabled, you can also select a specific EXDR version for deployment. Reboot options are presented when the selected version requires driver updates.
Why it matters: Deploying the EXDR agent across large numbers of endpoints is now significantly faster and easier — bulk EXDR deployments are fully tracked in audit logs for visibility and compliance.
► EXDR Agent Auto-Update Now Configurable in Profile Settings
What you can see: A new EXDR Client tab is now available under the Updates section of profile configuration, with options to enable automatic EXDR agent updates and set an update schedule.
What you can do: Enable auto-updating for the EXDR agent within a profile and define how frequently endpoints should check for and apply updates — daily, weekly, monthly, or on a custom schedule. Where version flexibility is enabled, you can also specify which EXDR version endpoints should update to.
Why it matters: Keeping the EXDR agent up to date across your endpoint fleet is now fully automated and manageable through standard profile configuration, with no manual intervention required per device.
MDM
► Geo-Tracking Now Available for Android Devices in MDM Policies
What you can see: A new Geotracking section is now available within Android device policy configuration, and a Location History tab has been added to the Android device detail page showing device movement on an interactive map.
What you can do: Configure how frequently Android device locations are tracked — by time interval or by movement distance — and set how long location history is retained Once a Geotracking-enabled profile is assigned to a device, tracking starts automatically. On the device detail page, view the full location trail for the last 24 hours, 7 days, or 30 days, with per-point details including timestamp, coordinates, and accuracy.
Why it matters: Administrators managing Android device fleets can now enforce and monitor device location centrally through policy, with a full visual history of device movement and automatic cleanup of data beyond the configured retention window.
Scripting
► RMM Custom Script Monitoring Now Available for Mac Devices
What you can see: Mac devices are now supported in the RMM monitoring engine with a Custom Script monitor type.
What you can do: Create and deploy custom script-based monitors on Mac endpoints, giving you flexible, script-driven monitoring capability for your Mac fleet.
Why it matters: Administrators managing mixed-OS environments can now apply consistent RMM monitoring coverage to Mac devices alongside Windows and Linux endpoints.
► RMM Performance Monitoring Now Available for Linux Devices
What you can see: Linux devices are now supported in the RMM monitoring engine with CPU Usage/Performance and HDD Usage/Performance monitors.
What you can do: Set up CPU and disk performance monitors on Red Hat, Ubuntu, and Debian Linux endpoints directly within the platform.
Why it matters: Teams managing Linux infrastructure can now monitor device health and performance through the same RMM framework used for other platforms, improving visibility across mixed-OS environments.
► Shell and Bash Scripting Now Supported for Linux Endpoints
What you can see: Shell and Bash script types are now available when creating procedures targeting Linux endpoints.
What you can do: Write, edit, and execute Shell and Bash scripts on Linux devices directly from the platform — the same way PowerShell and batch scripts are used for Windows.
Why it matters: Linux endpoint automation is now a first-class capability on the platform, enabling administrators to run maintenance tasks, configurations, and custom workflows on Linux devices at scale.
File Group Variable
► Create File Group Variables Directly from Global Software Inventory
What you can see: A new “Create File Group Variable” button is now available on the Global Software Inventory page, activated when one or more applications are selected.
What you can do: Select any installed applications from your Global Software Inventory and instantly create a named File Group Variable containing their full file paths — without navigating away or manually entering paths. The new variable appears immediately under Settings > System Templates > File Group Variables.
Why it matters: Building application-based rules is now faster and more accurate — administrators can group applications directly from their live software inventory, eliminating manual path entry and reducing the risk of errors when configuring policies.
Reporting
► Third-Party App Reports Now Clearly Identified by App Name
What you can see: Exported third-party application reports now include the app name as the file name, sheet name, and a dedicated column within the report.
What you can do: Instantly identify which application a report belongs to from the file name alone, without needing to open it — and navigate multi-sheet exports with clearly labelled tabs.
Why it matters: When working with reports across multiple third-party applications, each export is now self-identifying, reducing confusion and saving time when managing or sharing report data.
Service Desk
► Ticket Submitter Identity Now Accurately Shown in the Inbox
What you can see: The ticket inbox now displays a Submitted By column that correctly identifies the logged-in user who submitted the ticket — whether submitted via the Communication Client or the web portal.
What you can do: Technicians can now identify the true submitter of any ticket directly from the inbox view without opening each ticket individually. The ticket detail view also shows both the submitter and the associated device as separate, clearly labelled fields.
Why it matters: In environments where multiple users share devices or device ownership differs from the active session user, ticket routing, accountability, and triage accuracy are now significantly improved.
macOS GUI
What you can see: The macOS GUI has been updated to provide a user experience and interface more closely aligned with the Windows GUI, making the navigation and overall experience more consistent across both platforms.
BUG FIXES
► Network Discovery and OID Display Enhancements
Fixed an issue where the device count in discovery logs did not match the actual number of devices listed. Also resolved an issue where managed devices were not displaying OID information — OID data is now correctly shown for managed devices.
► Linux Device Online Status Now Accurately Reflected
Fixed an issue where Linux devices were incorrectly displayed as Offline on the platform even though the endpoints and their agent services were fully operational. Device status now correctly reflects the actual running state of Linux endpoints.
► XCS Update via Torrent Now Completes Successfully
Resolved an issue where the XCS/XCSW update job would trigger but fail to perform the update when torrent-based delivery was in use. Updates now complete as expected when torrent is the configured delivery method.
APPENDIX
NEW PORTAL VERSIONS
- ITarian Platform: XX.X
NEW AGENT VERSIONS
- Client Security for macOS (XCS macOS): 3.0
- Communication Client for macOS (XCC macOS):11.2S
- Communication Client for Linux (XCC Linux):11.2
- Communication Client for Android: 11.2