Summary: This post highlights the critical importance of an accurate Configuration Management Database (CMDB) and automated discovery tools in IT service management. Through a cautionary anecdote about manually troubleshooting a rogue, network-slowing CPU across a six-floor building without a CMDB, it illustrates the pitfalls of relying on outdated spreadsheets. It introduces Xurrent ITAM—featuring agentless discovery, scheduled WMI, SSH, and SNMP scans, and integration with tools like Intune and Jamf—as a modern solution to keep CMDBs automatically updated and prevent widespread productivity loss.
Table of contents
Remember the dark ages?
I’m writing this the day after the big Microsoft Outlook Outage of November 2026. It brought up old memories of a dark time in my help desk career.
In the ancient past – this would have been maybe 1993? 1994? – I was managing an outsourced help desk; we were located at our customer’s site, but our home office was in another state. To paraphrase the TV Show “Fargo” – “This is a true story. At the request of the survivors, the names have been changed. Out of respect for the dead, the rest has been told exactly as it occurred.”
Ok, we were traumatized; we didn’t die. But it was a dark day.
Gather close, and listen, my young ones, to how the world used to be.
It was a day like any other. Phones ringing, tickets getting created and solved, people happy, people unhappy. And then – a computer started beaconing on the network.
Now this wasn’t the modern-day version of beaconing, where malware intentionally sends a signal over and over to basically create a denial-of-service attack. This was just a malfunctioning CPU sending out a ping at such a rate that it overwhelmed the network. Everyone’s machines slowed to a crawl because of this one CPU.
No problem – we were on it! We had the logs! We had the IP address! All we had to do was turn off the box. That’s all. Just… turn it off.
But we didn’t have a CMDB (configuration management database). We didn’t know what computer the IP address was connected to. We didn’t know where it was.
The good news was – it was in the building. The bad news was – it was a six-floor building.
Yes, my enthralled audience, we did it. We went floor by floor. We had everyone on the floor shut down their PCs. If the beaconing continued (and oh yes, it did continue) they could boot back up, and we would move to the next floor. Six floors. How much productivity wasted? It’s ok – we were on the hunt!
But after six floors, we hadn’t found it. Our customer liaison was – less than happy. We were frazzled. We sat in the server room wondering what to do next. And then – one of the techs had an idea. He looked at some paperwork and said something like “Um – I think it’s this server.” Yes, the malfunctioning unit was a server. In the server room. And we didn’t know it. Because we didn’t even have a rudimentary CMDB. We shut the server down. Beaconing stopped. Customer liaison came in and heard the story. He looked at us. He looked at the server. He looked at us. He turned and left.
Not my proudest moment. (The story of crashing a front-end processor will need to wait for another day…)
We needed a CMDB – and Discovery to keep it up to date
If we had had a CMDB and Discovery in place (instead of manually created, inadequately updated spreadsheets) – we would have known which computer was linked to which IP address. Not to hammer in the point too much – when the beaconing started, we would have gone to the server, shut it down, dealt with the problem, instead of making SIX FLOORS of people shut down their PCs.
If only we had Xurrent back then, with their new ITAM functionality – I might have kept that job longer. The outsourcing company wouldn’t have had egg on their face. A lot might be different. All for lack of a CMDB and a discovery tool to keep it updated. (It was a lousy job. Maybe it was for the best. Except for all those people whose productivity crashed that day.)
Xurrent ITAM
Xurrent has always had a CMDB; but with ITAM, Xurrent now adds an agentless discovery tool that scans your data center and soon will scan your cloud (and there are more features to come). Do you already run tools like Intune or Jamf? Bring in their data too! Now your service desk will be working from an accurate CMDB, updated regularly, because Xurrent lets you set up scheduled WMI, SSH, and SNMP scans to find your servers, network devices, and endpoints.
And finding a beaconing CPU? You won’t have to shut down six floors of boxes ever again.
Learn more about Xurrent’s ITAM solution here: https://www.xurrent.com/itam
And contact [email protected] for more information or a demo.