26.8.2 ‘Voyager’ released
Changes compared to 26.8.1
New Features
Added a Custom code section to the Branding page of the Comet Management Console (COMET-1637)
A top-level administrator can now inject custom JavaScript and CSS into the web interface. Code can be supplied inline or loaded from an external URL, placed in the document head or at the end of the document body, and is applied to the login page and to the web interface of all tenants. The page Content-Security-Policy is extended automatically to permit only the specific code that was configured.


26.8.1 ‘Voyager’ released
Changes compared to 26.8.0
New Features
Added an allowlist of PKCS#11 driver module file paths permitted during Authenticode codesigning in the Comet Server admin settings (COMET-59771)
When Comet Server Authenticode-codesigns the Backup Agent installers it generates for download, the signing key can be accessed through a PKCS#11 driver module. A top-level administrator can now maintain an allowlist of the driver module file paths permitted for this codesigning. Only modules whose file path appears on the allowlist may be used; a path outside the allowlist causes installer downloads to fail. When upgrading, any PKCS#11 module paths already in use are seeded into the allowlist automatically.

Added ConnectWise Manage PSA integration which raises job failure tickets (COMET-59932)
ConnectWise Manage joins Comet's existing PSA integrations. Once configured, Comet Server automatically raises a ConnectWise Manage ticket when a backup job fails or a scheduled backup is missed, matched to the affected client, device, and Protected Item, with a severity mapped from the failure type. Repeated failures on the same device and Protected Item add a note to the existing ticket and escalate its severity instead of opening duplicates. The integration is configured under the PSA settings in the Comet Management Console, where you provide the Site URL, Company ID, public and private API keys, Client ID, and an optional Service Board and fallback ticket company.






Improved Microsoft 365 account selection with a new rule-based editor and exclude rules (COMET-59120)
The account selection for Microsoft 365 Protected Items has been redesigned around an ordered list of include/exclude rules in both the Comet Management Console and the Comet Backup desktop app. You can now exclude specific users, groups, teams, or sites — for example, backing up an entire organization except a few accounts — with an "All accounts" rule automatically protecting users added to the organization later. Rules require Comet Backup 26.8.1 or later on the device.






26.7.1 Janus released
Changes compared to 26.7.0
Enhancements
- Improved the reliability of Proxmox VM restores to RBD/Ceph-backed storage. When restoring a disk, Comet now checks for an existing RBD/Ceph volume of the same name and automatically picks a non-conflicting name. RBD/Ceph images were previously excluded from this collision check because they do not live on the node's filesystem, so a restore could clash with an existing volume; Comet now probes for these images directly (COMET-59072)
- Improved the reliability of backup jobs using OpenStack Swift or FTP Storage Vaults by retrying transient network errors (such as a dropped connection or timeout) when first connecting to the storage location. Definitive server responses such as authentication failures are not retried and continue to fail immediately (COMET-60150)
26.8.0 Voyager released
Changes compared to 26.5.4
New Features
Automatically start a Bulk Update Campaign when the Comet Management Console restarts
Keeping every device on the latest Backup Agent usually means an administrator remembering to launch a Bulk Update Campaign by hand after each server upgrade. A new Automatic Upgrade Campaign option now does this for you: when enabled, Comet Server starts a fresh Bulk Update Campaign automatically each time the Comet Management Console restarts, rolling the update out across your device fleet with no manual step.
To avoid redundant campaigns caused by quick or repeated restarts, a new campaign is only started if it has been more than 24 hours since the last bulk upgrade campaign.
The option is configured by a top-level administrator under the Backup Agent Downloads settings. Turn on the Enabled toggle, then use Configure upgrade campaign to pre-set exactly how the automatic campaign should behave — whether to upgrade older versions and/or downgrade newer ones, whether to wait for running backup jobs to finish or interrupt them, and whether to target all devices or a filtered subset.



Added support for NinjaOne RMM integration
NinjaOne is a unified IT management platform combining RMM, endpoint management, and ticketing. Comet's new NinjaOne integration surfaces backup status directly inside NinjaOne, so you can monitor your customers' backups alongside the rest of their endpoint data instead of switching between tools.
Once configured, Comet writes the outcome of each backup to custom fields on the matching NinjaOne device — Last Backup Status, Last Backup Time, Last Backup Destination, Last Backup Total Size, and the Comet Job ID — refreshed automatically after every job.

Optionally, you can also enable automatic ticketing. When a backup fails, Comet opens a NinjaOne ticket against the affected device, with a link back to the Comet job log and a summary of the run. Repeated failures on the same device and Protected Item add a comment to the existing ticket and escalate its severity rather than creating duplicates, and when the next backup succeeds Comet resolves the ticket automatically with a resolution comment.


The integration is configured under Settings → Integrations in the Comet Management Console and requires the NinjaOne Agent on each device. For full setup instructions, see the NinjaOne integration guide.

26.7.0 Janus released
Janus is the latest entry in our quarterly rollup series. It branches off from our main rolling Voyager development into a fixed target for our partners to qualify and build upon.
This Quarterly release is named after Saturn's moon Janus. Fun fact: Janus takes its name from the Roman god of gates, doorways, beginnings, and endings — fitting for a moon caught in one of the Solar System's strangest orbital arrangements. This small, potato-shaped, heavily cratered moon shares its orbit with a sister moon, Epimetheus, and about every four years the two moons drift close enough that they swap orbits with each other — a co-orbital dance found nowhere else in the Solar System. Keep an eye out for Epimetheus; that name may sound familiar again later this year.
Comet 26.7.0 Janus focuses on smarter administration and faster performance across the platform. Highlights include Model Context Protocol (MCP) support for agent-based workflows, Comet Server webhook notifications that render natively as Slack messages, saved job searches in the Comet Management Console, and a new Storage Template option to prevent end-user edits of template-provisioned Storage Vaults. This release also delivers performance improvements across our Comet Management Console, the Comet Backup desktop app, and Office 365 Protected Items.
As always for a new quarterly release, there are two changelogs for 26.7.0 depending on whether you are coming from the previous quarterly release or the previous Voyager release:
Changes compared to 26.4.5 (Phoebe)