ServiceNow CMDB Reviews

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.

It integrates with so many different things.

ServiceNow CMDB assisted us in streamlining multiple processes.

We do some of the programming for the queries and tables, and maybe some of that could be out of the box.

I wish we didn't have to pay for additional modules. For example, the vulnerability module is at an additional cost so that we can pull the Qualys scans and actually have automated tickets involved. If that workflow can also be part of that, it would be nice.

It would be good if there's a logic that we've already closed or for which we've mitigated the vulnerability that it would automatically close an incident ticket. We still have to put logic to and build some programming or code for this at present.

I've been using this solution for at least four to five years.

It's highly available, and we haven't had any issues with it.

We have an application team, a database team, that takes care of the maintenance and provides firmware updates, etc.

We're not really a large organization; we have approximately 1,500 employees. It's perfect for us.

ServiceNow CMDB is used extensively by our IT infrastructure teams.

We used ConnectWise before, but it was actually larger and was a pretty enterprise beefy solution.

It is good to have a solid coder or programmer who understands the database and knows how to set up these queries because once that's in place, there's just a phenomenal amount of information that you can use for data and for decision making and planning. I highly recommend that.

For what we use it for, ServiceNow CMDB really works out well, and I wouldn't recommend any other type of service solution.

I would rate it at nine on a scale from one to ten.

ServiceNow CMDB is used for incident management, request management, service mapping, and discovery.

ServiceNow CMDB is a single data model where we can capture attributes. We can have a tree structure with ServiceNow CMDB, which makes it very powerful. We can use ServiceNow CMDB to create more tables that can provide granular information.

ServiceNow CMDB may face performance issues if we try to make the solution too large by adding more CIs.

I have been using ServiceNow CMDB for more than five years.

ServiceNow CMDB is very stable.

I rate ServiceNow CMDB a nine out of ten for stability.

ServiceNow CMDB is enormously scalable. You can store millions of CIs (Configuration Items) in ServiceNow CMDB.

I rate ServiceNow CMDB a nine out of ten for scalability.

The solution’s initial setup is very simple.

I rate ServiceNow CMDB a nine out of ten for its ease of initial setup.

ServiceNow CMDB's deployment time depends on the data, but it doesn't take much time. It's quite fast.

ServiceNow CMDB is deployed on-cloud in our organization. I advise users to have a good conceptual understanding of CMDB (Configuration Management Database). First, you need to understand what your assets are, and on top of that, you can create your building.

It's quite easy to implement ServiceNow CMDB for any new project. The solution is quite easy to use and get reports from. It's quite easy to import data in ServiceNow CMDB.

Overall, I rate ServiceNow CMDB a nine out of ten.

I am an SME specialist, and we primarily work with government customers who use ServiceNow systems. When they require a CMDB specialist, I am assigned to those sites.

We have customers who deploy the solution on-premises, while others use the ServiceNow cloud.

The issue with UCMDB is that it lacks integration with other solutions, particularly with service management components. On the other hand, ServiceNow excels in integration and is considered the best tool in the market for this purpose. Although it may not be as proficient in discovery as some other tools, its actual integration capabilities surpass all others.

The discovery process and service mapping could be improved. I prefer a more comprehensive approach to discovery and simplified service modeling.

Technical support has room for improvement.

I have been using ServiceNow CMDB for one and a half years.

I would rate the stability a seven out of ten. The discovery process with ServiceNow occasionally fails, and it is quite challenging to identify the cause. There are no clear indications, but restarting the mid servers usually resolves the issue. This problem may stem from pro servers, mixed servers, or various applications.

I would rate the scalability as an eight out of ten. The only drawback is the performance issue we encounter when scaling up.

The technical support is not great.

Neutral

The initial setup is complicated, but compared to other solutions, it is not more difficult. I would rate the deployment an eight out of ten.

The deployment process typically takes around three to four hours. The solution includes a built-in wizard to assist with the deployment, with the only challenging step being the mid-server phase.

I would rate ServiceNow CMDB an eight out of ten. While it remains a strong product, there is still room for development in terms of discovery and service modeling to catch up to its competitors. Nonetheless, it is currently the best option available.

In some instances, our clients are medium-sized businesses, but the majority are at an enterprise level, with thousands of users.

Overall, ServiceNow CMDB is the best option in the market due to its seamless integration with other systems. However, it is not the best discovery tool. UCMDB is a superior discovery tool, but it lacks integration and does not work well with other parts.

ServiceNow CMDB is fully integrated and complete. ServiceNow has modules for everything an IT service company needs, and it's flexible. 

While ServiceNow CMDB is flexible and comprehensive, it's also difficult to implement and requires a lot of customization. 

In order to fully leverage ServiceNow CMDB, you need ServiceNow Discovery and some other ServiceNow solutions. It's expensive to purchase all of these. We're negotiating with ServiceNow, but we're thinking about replacing it with another CMDB solution. 

I have used ServiceNow CMDB for six years.

I rate ServiceNow CMDB five out of 10 for ease of setup. The installation was complex in our organization because we are providing services to many other companies. The plain vanilla implementation should be easy. If you need to customize the solution, you must have people who understand how to do that. ts.

One manager and four data analysts oversee ServiceNow. Their job is to do customizations. When we onboard new clients, we have to customize ServiceNow to meet their requirements. We set up separate workflows on various instances for each client. It requires little maintenance if you aren't customizing it. 

I rate ServiceNow CMDB two out of 10 for affordability.  The licensing model is complex. Due to contract restrictions, I'm unable to see how much we pay, but it's calculated based on the number of users, modules, and license types. 

I rate ServiceNow CMDB seven out of 10. It's a complete solution, and it's ideal if you have a complex environment. However, before implementing something as complicated and costly as ServiceNow, you should consider if you need it. 

A simpler, less expensive solution might work fine for you. If you only need basic CMDB features, such as registering incidents and changes, other tools are much simpler than ServiceNow. A large organization with complex requirements will get the most value out of ServiceNow. 

We use it for network and server discovery, and storage.

I like ServiceNow's credential-based discovery.

Integration is complicated and requires advance scripting and customization to complete it.

It would be good to have the ability to customize the UI.

I've been using ServiceNow CMDB for a year.

It is a stable solution.

I would rate ServiceNow's scalability at eight out of ten.

Technical support staff take two to three days to respond to queries. Therefore, I would give them a five out of ten.

Neutral

The initial setup is easy, and all functions are built-in. It took about a week to set up.

We chose ServiceNow because it has more functionalities. It takes at least one week to be trained on ServiceNow, and it is easy to learn.

There are multiple plugins and integrations available in ServiceNow CMDB, and we can build the environment that we want. Therefore, I would rate this solution at eight on a scale from one to ten.

I use ServiceNow for tracking infrastructure procurement and all the configuration items on a particular network. It tracks the maintenance and everything related to configuration management. We have about 20,000 employees and a team of personnel that works with ServiceNow.

Everything is now in one system. Employees submit service and change requests. It all goes through ServiceNow.

I deal mostly with asset management, and ServiceNow helps me do my job more effectively. 

I'm still learning about CMDB's capabilities, so I haven't seen anything that I want added yet. 

I've been working with ServiceNow since January.

ServiceNow is stable.

I don't have admin rights, so I can't do anything to affect a lot of change in the scalability. I only deal with the asset management part, and I haven't had any problems adding to the system. When assets come within my particular AO, my task is to add them to the configuration management database, and I haven't had any issues.

We previously used CyrusOne for configuration management. We switched to ServiceNow, the platform of choice for our client, and they want everyone to be on the same page. At the same time, ServiceNow does everything we want to do and has room for growth. 

Setting up ServiceNow was straightforward. We had a smooth onboarding process, and they provided training for the system admins as part of the package for this system and implementation.

I rate ServiceNow CMDB nine out of 10. I recommend ServiceNow because it meets all our configuration management needs. It gives us everything that we need to have based on our IT requirements.

I've used it for managing client inventories and infrastructure to ensure that the relationship among various CIs is managed. I've also used it to troubleshoot quickly and handle change.

It's not too difficult to configure with regard to the UI. My experience working with ServiceNow CMDB has been a very comfortable one.

Definitely, the price needs to be lower because there are clients that I work with who cannot afford ServiceNow. I have to end up proposing alternate solutions to fit their budget.

I've worked with this solution for about six years now.

It is mostly a cloud solution.

It is a stable solution.

It is scalable.

When we needed help, they've always been available. We've not had issues though.

You do need skilled people for the initial setup, but it's not too difficult to work with.

Typically, the deployment of ServiceNow for the various organizations that we have worked with has spanned between one to three months.

We are integrators ourselves and implemented it.

In comparison to the cost of other solutions, you get value for your money with ServiceNow CMDB. It could definitely be cheaper though.

ServiceNow is very intuitive and is a market leader. I used to use BMC Remedy before, which had a traditional type of deployment. ServiceNow is quick to start up because it's on the cloud. It has ready-to-use use cases available for deployment. So, the deployment is much faster than it used to be on Remedy. 

There's a whole lot of automation that comes with ServiceNow, so I'd definitely recommend it.

At present, I would rate ServiceNow at ten on a scale from one to ten.

ServiceNow CMDB is not being used that much in the company. It's being used by customers, and mostly 90% are enterprise customers. The tool is used by many for IT assets, for example, PCs, printers, and applications. It's not just used for trouble ticketing. ServiceNow CMDB is used to manage the entire IT asset.

As I work based on the IT governance framework, what I like best about ServiceNow CMDB is ITSM, so incident/service request management. I also like that it can be useful for project portfolio management.

An area for improvement in ServiceNow is the reporting because there are reporting features that would be better when done within the platform, rather than having to buy the performance analytics model. There is a greater difference between the dashboarding that you can do from the platform versus what's on the performance analytics model. Some of the features currently available within performance analytics would be good to have within the platform because sometimes, customers will say that the tool is okay, but it's not enough, so you'll need to go with the performance analytics model, and that's costly.

The problem is that paying extra for performance analytics costs too much for what it can give back. Customers don't need the entire functionality delivered by performance analytics, but the default functionalities within the platform are not enough. There is always a trade-off. Customers are not getting value for money paid for the performance analytics model because they don't use the whole set of functionalities, and that is the problem.

For the time being, there isn't an additional feature I'd like to see in the next release of the tool.

I've been using ServiceNow CMDB for six years now.

ServiceNow CMDB is a very stable solution.

Technical support for ServiceNow was perfect. They provided a very high level of support.

The market sees ServiceNow as the Ferrari in terms of pricing. It's at the very top, and its cost is very, very high. If a customer is considering an alternative platform due to pricing, so I looked at Jira. It's clear that ServiceNow provides much more, but sometimes, you need a trade-off between customer requirements and what's on the platform.

If customers were to switch from ServiceNow to Jira, it would be because of pricing. Feature-wise, the two are almost equivalent. Everything you find in Jira, you can find in ServiceNow, but not everything you find in ServiceNow is in Jira, especially in terms of flexibility. One of the key points of ServiceNow is that when you want to downscale and you belong in a smaller organization, it becomes too costly. Pricing may change more in ServiceNow and ManageEngine, for example, but not that much in Jira. Downscaling in ServiceNow for a smaller organization is too costly, so they need to create a shrink-wrapped package specifically for smaller organizations, rather than delivering too much and costing too much.

On a scale of one to five, with one being the worst pricing, and five being competitively priced, in particular, not cheap, but competitively priced, I'm scoring ServiceNow a two because it's very expensive in the marketplace. If they can make some changes to their pricing packages, it would be much better.

I use ServiceNow CMDB, but understand that I work in a delivery company, a service company. The company drafted a partnership with ServiceNow six years ago and is still a partner, particularly a premier partner.

I'm giving ServiceNow CMDB the best score, ten out of ten.

I'm looking at ServiceNow from the standpoint of things like technical services, business services, mapping, deployments, rolling up inventory to those mapped deployments, and doing application services, which takes your inventory and spreads it across all your instantiations.

We are more oriented toward cost control and multiple instantiations of the same product across multiple locations; basically, multiple data setting environments to thousands of deployments.

We'll deploy to our customers and host their equipment. Our customers subscribe to our equipment and we sell our software, but rarely do we sell our software. Basically, our customers pay us monthly to host their software and keep it updated. Our huge customers, companies like Bank of America and Wells Fargo kind of huge, get us to host their equipment. Otherwise, for smaller clients, run on our ASP configuration.

ServiceNow CMDB is just something that you could track everything on. For example, I can service a company with 50,000 employees with hundreds of thousands of servers.

ServiceNow was a platform that they wanted to sell as a development platform, but it didn't have a lot of traction there. So, they basically built a ticketing system because Remedy was a sad environment at the time and they built the next great Aon. ServiceNow is basically a go-to when it comes to Remedy and ticket management. The idea is that CMDB is to track all your assets, how you handle them, how you back them up, how you secure them, and which agents you have on them. To be able to do all that, keep it in the CMDB.

There are areas that could be improved, but that's a longer discussion. It all depends on what you are looking to do with it and then it becomes an issue of how do you configure the CMDB accordingly.  If I were to make one set of suggestions it would be how we defined deployments which would link back to instantiations.  Deployments would need to handle varying degrees of customization and granularity that integrate with Application Services and Business Applications.

I started dealing with ServiceNow back in the days of version D, which was seven years ago. I'm now on version P.

It is stable as hell, but it is always about what are you trying to do with your CMDB to make your company a quicker, faster, and more viable entity in your work or industry.

The initial setup can run anywhere from complex – meaning that you're doing contract management and looking for contract renewals and SLA achievement across contract structures – to just making sure your server has backup.

When I was a student, I worked on a prototype for an app, and my main tasks were directly in CMDB. I had done a synchronization implementation to retrieve inventories from Excel files and put them into CMDB with automation.

I also used it in my previous company. This company is a supplier of ServiceNow for several clients in Canada and the USA, and we did a lot of customization and configuration for the clients. We worked with all ServiceNow platforms and not only with CMDB. If you want ServiceNow within your company, you've got to find a supplier or go with ServiceNow directly. 

It was on-premises, but ServiceNow is cloud-based. It is software as a platform. 

It helped us to synchronize some of the files containing the inventory of assets. 

The most valuable feature of ServiceNow is the user interface because you can customize or configure it directly from the user interface by using the mouse. It is easy to use even for non-IT people.

You can also directly plug your ServiceNow instance within your Microsoft Active Directory and then retrieve all your users and groups. So, you can use the users and groups to put automation inside the application. When you have new hires, you can automate the group security and group attribution.

It is very good in terms of performance. Its performance is almost 100%. Once, it took less than two minutes to back up and run an instance. It has very good reliability.

They can improve the mobile application and the TGO tool, which is a built-in tool for development and implementation. As a developer, it is very frustrating to configure or customize the mobile app. In my opinion, this part of the application needs full rework and re-engineering.

I have been using this solution for three years.

It is stable with very good reliability. Its performance is almost 100%. ServiceNow has very high standards.

It is very scalable. You will be able to scale it irrespective of the size of the infrastructures. It should work with really big IT infrastructure. You can adapt it for every kind of infrastructure. You can work with Windows infrastructure as well as with Linux infrastructure. You can do pretty much what you want with it. However, you can't do any implementations that are not ITIL compliant.

In terms of users, you might have an IT project manager, user services people, supervisors, and contract managers. ServiceNow provides Service Catalog to add every user of your company. You will add them into CMDB as assets. The real users are only the IT people of the company who have a license to use the backend.

Its usage is growing, and it is being used more and more. When I worked with it for the first time, I was not aware that you can also manage contracts with it. For me, it was just an ITSM solution with CMDB workflow, etc. In the last year, I have seen clients saying that they would like to add the Contracts module to manage their contracts within the platform. It is being used more widely now because you can do contract management and service catalog. You can also do IT support within the platform. It can be used as a ticketing tool.

I have interacted with the technical support of ServiceNow only twice. It is very easy to contact them. You log into the client portal, and you can send them the query or request. In my previous job, I was kind of providing support for our customers, and the company I was working for was kind of an interface between ServiceNow and clients.

It has a big community, which is a very cool thing about the ServiceNow platform. There is a lot of community and developer information. You can open a ticket directly with ServiceNow to ask them for new features or new releases, and they do respond.

It is really easy to deploy and add features. There are two ways of adding features inside the platform. You can go via their own built-in tools for developments or via the repository store. Basically, when you first start making changes inside an instance, there will be a tool to capture the modifications. When you are done with the modification, you close the repository and deploy it to the next instance. For instance, you would have one development instance, one pre-production instance, and one live or production instance. After you make a change in the development instance, you close the development repository and upload it to the pre-production instance. After that, you can do quality assurance, and if all is good, you can just deploy it to the production instance. It is really easy to work with.

Once you have your license, you can deploy it in five minutes, but it also depends on whether you are moving from an existing system to ServiceNow. In such a case, you will have to move your assets from your old system to the new system. I don't really have the experience of doing this, but, from my point of view, for a company with 20K employees, it will take eight months to one year to plan it and achieve it. There is a lot of work that you need to do before deploying it.

For its deployment, you would need an ITIL expert because ServiceNow is built around ITIL. You would also need a ServiceNow administrator, and you might require a project manager depending on the size of the enterprise.

In terms of maintenance, you don't have to do anything because all updates are mandatory, and they are deployed by ServiceNow. When you purchase the ServiceNow license, you agree to them updating it. You can choose the date on which you want to update. They don't force you to update it at a fixed date unless there is a security failure or a big issue. They send an email to your ServiceNow administrator or a message on the portal. You can then choose a date. They take care of the update, and you don't have to do anything. However, if you're located in Quebec or Canada and you are dealing with both French and English UI, you may have to do some maintenance after each update. Every time I saw an update, I had to deal with a problem related to translation in French, but it happened only in Quebec. I did not see this in France, and I don't know why.

I'm not 100% certain. My boss, who was kind of a ServiceNow director, used to think that we were making a profit with the solution, but I don't think it was a direct financial profit. It was more in terms of becoming more efficient. For instance, the whole user service department worked better with this platform.

It is really expensive. I don't know actually how much it costs, but in 2016, when a client decided to move from an old solution to ServiceNow and had to choose a supplier for ServiceNow, I had heard that it could cost $10 per hour, which is really expensive. 

I am not aware of any additional fees to the standard licensing fees. There is no standard ServiceNow solution. When a company wants to acquire ServiceNow, they already know which module they will choose. In a basic package, you would have Service Catalog, Incident Management, and Change Management. These modules are usually required in an IT company.

I would advise others to go for it. I would also recommend having at least one ServiceNow administrator in the company who is certified. Its certification is not very difficult to get. If you have an IT degree, you can go for it very easily.

I would rate ServiceNow CMDB an eight out of ten in spite of the fact that it was a bit frustrating to work with as a developer.