johnnyq
24c902f0e2
Add RMM device actions: a provider's Edit has a Device actions switch, off for every provider until an admin turns it on, and with it technicians with Modify on Support can reboot a device, install its patches on Windows, turn its maintenance mode on and off, and run one of the RMM's scripts on it, from the Actions menu on the device's card on its asset or the lightning button beside the asset on a ticket; reboot and patches ask first and say who is signed in; Run a script lists the RMM's scripts for the device's platform with favorites first, starts with the script's own arguments and timeout, shows the output in the window and notes it on the ticket picked, or leaves it in the RMM's history when not waiting; each action goes in the asset history, the audit log and, when done from a ticket, on it as an internal note by the person; a Tactical 403 says which role permission the key needs; Tactical actions use POST agents reboot, POST winupdate install, PUT agents with maintenance_mode, GET scripts and POST agents runscript; rmmHttp accepts text answers, reads text error bodies and sends an empty object for an empty body; new agent/post/rmm.php handlers and agent/modals/rmm/rmm_script.php window, with their request keys in the demo locks; database 3.6.9 adds rmm_providers.rmm_provider_actions; 26.11.9 changelog entries
2026-11-14 00:25:16 -05:00
..
Add RMM Providers under Admin > Integrations to bring devices in from an RMM as assets, with Tactical RMM as the first kind: a providers list (search, sort, add, edit, test, sync now, turn off and on, delete), a Clients page per provider to link its clients to ITFlow clients with same-name suggestions, devices matched to existing assets by serial or unique name or made as new ones, each asset field following the RMM until it is edited in ITFlow, removed devices marked and returned ones picked up, deleted assets left out until Bring back, a card per RMM device on the asset page with online state, last seen, signed-in user, reboot, patches and failing checks, Take Control and dashboard links, the state on the quick look, a status dot and RMM filter on the assets list, and the RMM Sync cron job every 15 minutes across every provider that is on; shared engine in functions/rmm.php and the Tactical adapter in functions/rmm_tactical.php so another RMM is one file and one registry line; database 3.6.7 adds rmm_providers, rmm_clients and rmm_devices; demo mode locks the new pages and handlers; 26.11.9 changelog entries
2026-11-13 18:13:58 -05:00
Add RMM Providers under Admin > Integrations to bring devices in from an RMM as assets, with Tactical RMM as the first kind: a providers list (search, sort, add, edit, test, sync now, turn off and on, delete), a Clients page per provider to link its clients to ITFlow clients with same-name suggestions, devices matched to existing assets by serial or unique name or made as new ones, each asset field following the RMM until it is edited in ITFlow, removed devices marked and returned ones picked up, deleted assets left out until Bring back, a card per RMM device on the asset page with online state, last seen, signed-in user, reboot, patches and failing checks, Take Control and dashboard links, the state on the quick look, a status dot and RMM filter on the assets list, and the RMM Sync cron job every 15 minutes across every provider that is on; shared engine in functions/rmm.php and the Tactical adapter in functions/rmm_tactical.php so another RMM is one file and one registry line; database 3.6.7 adds rmm_providers, rmm_clients and rmm_devices; demo mode locks the new pages and handlers; 26.11.9 changelog entries
2026-11-13 18:13:58 -05:00
Add RMM device actions: a provider's Edit has a Device actions switch, off for every provider until an admin turns it on, and with it technicians with Modify on Support can reboot a device, install its patches on Windows, turn its maintenance mode on and off, and run one of the RMM's scripts on it, from the Actions menu on the device's card on its asset or the lightning button beside the asset on a ticket; reboot and patches ask first and say who is signed in; Run a script lists the RMM's scripts for the device's platform with favorites first, starts with the script's own arguments and timeout, shows the output in the window and notes it on the ticket picked, or leaves it in the RMM's history when not waiting; each action goes in the asset history, the audit log and, when done from a ticket, on it as an internal note by the person; a Tactical 403 says which role permission the key needs; Tactical actions use POST agents reboot, POST winupdate install, PUT agents with maintenance_mode, GET scripts and POST agents runscript; rmmHttp accepts text answers, reads text error bodies and sends an empty object for an empty body; new agent/post/rmm.php handlers and agent/modals/rmm/rmm_script.php window, with their request keys in the demo locks; database 3.6.9 adds rmm_providers.rmm_provider_actions; 26.11.9 changelog entries
2026-11-14 00:25:16 -05:00