Seeking Advice: Technical Strategies to Automate CMDB Governance: Query 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi everyone,
Continuing my journey to automate our CMDB health without chasing down field service teams, I'd like to get your advice on handling Stale CIs and Leaver Assets:
1. Staleness Logic: Our 60-day Staleness rule flags records purely based on sys_updated_on age—even if the CI is active and healthy without physical changes. How do you distinguish between active CIs that simply haven't changed vs. CIs that stopped scanning or were decommissioned?
2. Leaver Hardware Deregistration: When an employee leaves, their handheld/computing device remains assigned to them in the CMDB until field teams update it. Can we automate device deregistration (or transition state to In Stock / Unassigned) as soon as HR/IAM marks the user as inactive (sys_user.active = false)?
3. Reassigned Assets & Intune Sync: If Intune shows an active state but ServiceNow shows non-live, can Intune sync via IRE to automatically reassign primary users and update operational states?
What native workflows or background rules do you recommend for these lifecycle issues?