ServiceNow CMDB Reviews

We use ServiceNow CMDB to manage assets and automate related tasks that were previously performed manually. We've integrated CMDB with our EDR solutions to discover assets, allowing us to use ServiceNow to support incident management. 

About 15 people use CMDB to manage assets throughout the business, but it is also used by incident and request managers. The change management team is part of that. In total, we have around 75 to 100 people directly interacting with the CMDB. 

We were previously using spreadsheets to keep track of everything. ServiceNow CMDB has enabled us to consolidate all this information into one place, which helps with audits and reporting. It also improves visibility. 

CMTB is an excellent configuration management tool that helps keep track of all configuration items across departments and organizations. The solution is also integrated with ServiceNow, making it easy to raise incidents, changes, and problems.

The most valuable feature of ServiceNow CMDB is that it provides transparency and tracking of CI usage across multiple process owners or service owners. This allows for change deployments and problem tickets to be tracked on a single dashboard.

We use it to support change management.

The CMDB for us is fed by our discovery tools, and it lets us be able to track the changes that we make to any incidents or escalation points that we have associated with a CI.

We use ServiceNow CMDB mainly for all the CIs. For example, we have to show assets for desktops. We actually can get the last logged-in instance through our SCCM product from Microsoft. We can run that actual report against all asset inventories, and that provides us with information on who the last user is and which device is actually in use.
That's been one of our audit control measures just through referencing all our CIs. Also, if we have any change tickets, any incidents, we can register that against the CI. Then, we can see the profile, how many tickets have been in place with regard to different environments, and the different hardware components.

It has improved our organization by bringing about quite a bit of automation so that we don't have to manually take inventory.

We can also quickly filter a query along different avenues to find out how many models we have in place.

We use that also against our Qualys vulnerability scans and patching scans, where the tool has really assisted us in streamlining multiple processes.

We use the ServiceNow CMDB to keep track of users and assets.

We use it for ticketing. We use it for quite a few things. We have a Knowledge base. We do incidents, we do requests. The CMDB looks at assets — what's tracked if those assets are terminated in use? It pretty much does all of our backend processes. For instance, if there's a request for software on a machine, It looks at the CMDB, checks if that machine is real, and checks what assets are tied to it. Most importantly, it checks what buffer instances and asset tracking is tied to it.

Every user in our company has access to it, and it's a global company. If I had to estimate, I'd say there are roughly 80,000 to 100,000 users.

A lot of our users use it for simple tasks, like submitting incidents or creating requests. Since we outsourced the help desk, the help desk uses it for initial triage, escalation, etc. I use it for reporting asset tracking. Everyone has various uses for it.

There's a lot of automation capabilities. There are process flows in ServiceNow that Edge didn't have. It has a great system for queries. Currently, everyone needs to be on the right version of Windows 10. Being able to look at assets and see which ones are in use and which ones are using an incorrect version. It's easy to cross-check SCCM with what's in ServiceNow to see who that device is tied to, if it's in use or if it's retired because the CMDB keeps checking that.

Implemented into DWP to manage all technical towers including the EUC tower that manages 120,000 x users. 

The biggest benefactors are the financial team in delivering financial controls and transparency of asset transactions. The finance team can actually manage the asset, and the depreciation of the asset from cradle to grave. 

The Operational delivery teams benefit too from understanding what stock assets they have ready to support live operations - i.e. Assets operationally ready (Goldstock), assets under repair, assets under staging (Build Image install & Asset tag) & Assets under Disposal, Goods-in & RTB. Operational teams with viability of their Stock Management can deliver demand management, meet Service Request SLA targets (joiners and Leavers & Refresh) & Incident SLA targets (B&F Swap)

My main use cases for ServiceNow CMDB involve effectively managing CIs in an organization's IT landscape, which can span a wide array of assets, from end-user computers to telecommunications systems. Essentially, it serves as a centralized repository for capturing and monitoring all the assets utilized within a typical office setup, encompassing servers, network equipment, and more. This repository is where all this crucial information is stored.

One of the most valuable aspects of ServiceNow CMDB is its user-friendly interface and high degree of customization at the user level.

We primarily use ServiceNow for asset management. We feed our on-prem and cloud inventory into ServiceNow CMDB. We also use it for event management together with Micro Focus Operations Bridge Manager. 

One important element is automation. We can back up and manage multiple configurations. It also enables password self-service.