Can someone talk about their practices for employee off boarding?Solved

That’s a solid theory, if you don’t have a plan, it’s chaos.

To answer your question, offboarding isn’t just one “Wipe” button; it’s a workflow. I can help you with a brief list of things you could look upon with Hexnode: It is going to be a huge yet simple process, let me give you an AI summarization:

Phase 1: Trigger & Identification: Don’t rely on automation here. Hexnode doesn’t “guess” if someone quit. You need a manual trigger (like an HR exit confirmation) to start the process.

Phase 2: Data Preservation (The Scripting trick): Before you wipe anything, check if you need the data. We use Custom Scripts in Hexnode to target specific directories, compress the files, and upload them to our secure cloud storage. It’s a lifesaver for roles where you need to archive work.

Phase 3: The “Ghost” App Cleanup: A standard wipe handles managed apps, but what about the stuff they installed manually? Run an Application Inventory Report first. If you see unmanaged software, push a removal script to clean that up specifically before the final nuke.

Phase 4: Platform-Specific Sanitization: This is key.

• macOS: usage of “Erase All Content and Settings” for cryptographic key destruction.
• Windows/Mobile: Decide between a Corporate Wipe (just work data) or a Complete Device Wipe (factory reset) depending on if the device is BYOD or Corp-owned.

If you divide and conquer the workload, it becomes easier. Hope that helps!

Thanks, man! That breakdown is super helpful, especially the scripting part for data backup. I hadn’t thought about doing that before the wipe command.

But here is another question: What if we can’t wipe the device immediately?

Sometimes Legal or HR tells us to put a freeze on a device because of an internal investigation or a dispute. If I can’t wipe it, but I also can’t let the (now ex-)employee access it, how do I handle that “Limbo” state using Hexnode?

That scenario is exactly why full automation is dangerous in offboarding!

In technical terms, you are looking at a “Legal Hold” or Governance Constraint strategy. Since you can’t destroy the data (evidence), you have to lock the perimeter.

Here is the technique for that:

Instead of hitting “Disenroll” or “Wipe,” you keep the device enrolled but tighten the policies.

• Revoke Access: Push a policy that strips Wi-Fi/VPN configurations so the device goes offline relative to your intranet.
• Lockdown: Apply a strict Kiosk mode or a policy that disables USB file transfer and copy-paste functions.
• Audit Trails: This is the most critical part. Ensure you are exporting the necessary Logs. If there is a dispute later, you need proof of exactly what actions IT took and when. Hexnode acts as your “System of Record” here to prove you didn’t tamper with the device during the hold period.

Hope that helps you survive the next “Refresh Cycle”!