Our Linux fleet has grown quite a bit, and we’re starting to see configuration drift across devices. Small changes add up over time, and manual fixes don’t really hold. Curious how others are dealing with this without constant manual intervention?
31 Views
Replies (5)
Marked SolutionPending Review
Participant
3 days ago
Feb 10, 2026
Marked SolutionPending Review
Yeah, same story here. We fix something, it looks fine for a bit, and then a few weeks later it’s out of sync again.
Marked SolutionPending Review
Participant
3 days ago
Feb 10, 2026
Marked SolutionPending Review
Exactly. We’ve got scripts, but unless someone remembers to rerun them, things slowly drift back.
Marked SolutionPending Review
Hexnode Expert
3 days ago
Feb 10, 2026
Marked SolutionPending Review
Hi all!
What usually works is stopping one-off fixes and making them repeatable.
With Hexnode, teams typically:
- Push Bash scripts using Execute Custom Script instead of running commands manually.
- Set up Hexnode Automate so those scripts re-run when devices check in or fall out of compliance.
- Use Action History and Action Reports to confirm what ran and where, without logging into devices.
That way, if a Linux device drifts, it just gets corrected automatically the next time it connects.
Best Regards,
Isabel Lora
Hexnode UEM
Marked SolutionPending Review
Participant
2 days ago
Feb 11, 2026
Marked SolutionPending Review
That actually clicks. We’re scripting, but we’re not enforcing anything.
Marked SolutionPending Review
Participant
2 days ago
Feb 11, 2026
Marked SolutionPending Review
Yep, same mistake we made early on. Once we let automation handle it, drift stopped being a daily headache.
Save
