Currently, Immybot runs inventory scripts and other activities on all computers in the platform, even when machines are excluded from maintenance and deployments. There is no way to completely stop all Immy activity on a machine, which can cause issues in the following scenarios:
- Troubleshooting interference - When investigating machine issues, Immy’s normal operation (including event log entries) can cloud diagnostic efforts and lead to false conclusions that Immy is causing problems
- Third-party machines - When ScreenConnect is installed on computers that aren’t managed by us we don’t want additional programs running that could generate unnecessary event log entries or warnings
Requested Solution: Add the ability to completely disable Immybot activity on specific computers with granular control options:
- Complete exclusion option - A setting to make Immy completely ignore a computer (no inventory, no scripts, no activity whatsoever)
- Agent-specific limitations - The ability to restrict which agents Immy can use to run commands on a machine:
- Disable Immy agent execution
- Disable RMM (Automate) integration for specific machines
- Disable ScreenConnect execution
- Allow users to select which communication methods are permitted per machine
Use Cases:
- Temporarily disabling all Immy activity during troubleshooting without removing the machine from the platform
- Managing third-party computers where minimal external software activity is desired
- Reducing event log noise on sensitive systems
- Maintaining compliance requirements for certain machines while keeping them visible in the platform
Expected Outcome: When these exclusions are enabled, the selected machines should have zero Immybot activity while remaining visible in the platform for management and future re-enablement.