Customer Requests

We have a requirement regarding the reboot process after critical Windows updates. Our requirement is as follows: When critical Windows updates are installed, the endpoint should notify the user that a restart is required. If the user postpones the restart on the first day, the endpoint should generate another restart notification on the following day. The second notification should not provide the user with an option to postpone the restart. The device should be forcefully restarted after a defined grace period. This is required because some critical Windows updates require a restart to complete firmware/BIOS-related updates and other pending components. Could you please confirm whether this workflow can be configured in Xcitium? If possible, please advise us on the recommended configuration/procedure to achieve the following: Day 1: Notification → User can postpone once Day 2: Mandatory notification → No postpone option → Force reboot Our requirement can be structured like this: Day 1 – Windows update Install all the Windows updates once its completed. Notify the user that a restart is required. Give a short grace period, e.g. 30 minutes. After the grace period, force the reboot. If you specifically need a “user can postpone once” workflow First notification: allow postponement. Record/check whether the endpoint is still in Reboot Pending status. On the following day, run a forced reboot procedure against devices still pending restart. The second notification should use Xcitium's Force the reboot option, rather than the postpone option. Please also let us know if this can be configured through a Patch Management Procedure, Restart Control, or any other Xcitium policy/procedure.

Our clients want to know when a device was registered in the console and when it was deleted; this information is important to prove that the device was indeed registered and deleted.

Currently, "Delete Device" in Endpoint Manager only uninstalls CC and XCS, leaving the EXDR agent running on the endpoint. Please have Delete Device also detect and remove EXDR, so decommissioned devices don't leave orphaned EDR processes and inaccurate license counts behind.

In the various SIG reports, an option for 'All' vs selectable company.

this si a fraud Abity for all users not been able to deply or install msi package on both new acc which is xcitium and itarian yet you people keep dedecutiong funds on cards linked to account this is so sad i believe ya'll already losing so much customers

There is a 50 MB file size limit if we want to transfer to & from between the workstation and the management server. This limit also applies to the Remote Control App. This needs to be increased to at least 1 GB. We have really large log files upto 1GB and we are not able to transfer it because of this.

Dear Xcitium team, I am writing to request the to add feature in Xcitium admin web console to Endpoint Devices data wipe option

I would like to submit a feature enhancement request based on our real-world use of Xcitium Service Desk 2 in a managed services environment. Currently, the minimum SLA grace period available in Service Desk 2 is 6 hours. While this may be sufficient for standard support requests, it does not adequately address several critical ticket categories that require immediate attention. Examples include: • Employee Termination Requests • Security Incident Reports • Suspected Account Compromise • Malware or Ransomware Events • Unauthorized Access Reports In these situations, a response target of 6 hours is far too long and does not reflect industry expectations or operational realities. Many MSPs and security providers require acknowledgment and action within 1–2 hours, and in some cases even sooner. We would like to request the addition of the following SLA options: • 1 Hour • 2 Hours • 4 Hours These additional SLA intervals would provide significantly greater flexibility and allow service providers to align Service Desk 2 with contractual response commitments and security best practices. Additionally, it would be extremely helpful if SLA Plans could automatically influence ticket priority. For example: • 1 Hour SLA → Automatically set Priority = Critical • 2 Hour SLA → Automatically set Priority = High • 4 Hour SLA → Automatically set Priority = High • 24 Hour SLA → Automatically set Priority = Normal This functionality would simplify administration, reduce workflow complexity, and help ensure that high-priority requests are properly classified without requiring additional workflow rules. As an MSP supporting multiple clients, we rely heavily on Help Topics and SLA Plans to drive ticket routing and urgency. Short-duration SLAs combined with automatic priority mapping would greatly improve the usability and effectiveness of Service Desk 2. Thank you for your consideration. We appreciate the continued development of the Xcitium platform and would welcome the opportunity to provide additional feedback or participate in testing of these enhancements. Sincerely, Yuri Kasan

"invisible filters" in the device list; when clicking numbers on the dashboard audit tab, filters are applied without a clear visual indicator in the URL or interface, which is confusing untill we reset the filter on the device list.