ServiceNow Discovery Reviews

We primarily use the solution for consolidating all the CIs and to make sure we've discovered all the network devices, servers, etc. It helps us maintain what we have and actually pulls all the information together horizontally and vertically in order to create a data model. We throw it into the CMDB where we can import the information and assign CIs for optimal IT operations. We use that probably twice a year, depending upon how much the changes are happening on the data center.

From the ideal perspective, IT operations actually enhance your operational functionality and give you insights into the health and visibility of your IT platforms on a daily basis. You can pull reports in 24-hour increments to take a look at physical instances and capacity issues. 

In ServiceNow this is ITSM and there's ITIL. So far, we've found that ITSM is the most popular. 

The ability to pull reports to check the health of the IT platforms is quite useful. You can pull reports daily to look at everything from capacity issues to physical instances.

The service mapping is excellent.

The maturity of the solution is very good. We're driving our customers to obtain that level of maturity in their own IT space.

The process involving the original setup of the solution is excellent.

The solution needs to improve the cost of the solution. There are a few different solutions and they do act the same and have the same types of capabilities, however, the cost is quite high.

I've been using the solution for three and a half years now.

The solution has very good stability. I don't recall witnessing many bugs or glitches on the product. It doesn't crash. It's reliable overall.

The solution is very scalable. A company wouldn't have any problems expanding if it needed to.

We have about 96,000 people in our organization.

I am a solutions consultant and a Discovery certified professional, so I could troubleshoot any issues myself if I needed to. With that being the case, I don't really need to reach out to technical support, so I can't speak to the quality of service.

I've worked on EMC extensively as well. We have used other tools. However, we use Discovery extensively.

Service Now has a great drag and drop functionality, which makes it easier to use, than, say EMC. It's dedicated itself to designing an easy to use tool for IT defense. I understand EMC is coming out with a new tool that rivals Service Now, however, in general, Service Now's tool gives users better leverage.

The initial setup is pretty good. It's what differentiates it from the competition.

The solution is quite expensive.

We have evaluated other services in the past, including EMC.

We're partners with the solution.

I would recommend the solution to other organizations. If you are already using Service Now products, Discover makes for a good complimenting solution. 

I'd rate the solution nine out of ten.

My company uses ServiceNow Discovery to discover multiple CIs, servers, network devices, computers, etc.

In our company, importing and scanning IP addresses with ServiceNow Discovery is a straightforward and easy process.

Whenever you try to discover something with the solution, you get errors that are not descriptive enough. The aforementioned area can be considered for improvement in the solution.

The licensing cost of the solution is an area where ServiceNow can improve.

I have been using ServiceNow Discovery for more than three years.

It is a stable solution.

It is a scalable solution.

My company deals with multiple clients who prefer ServiceNow Discovery. I was involved with the implementation phase of the product for my company's clients.

The initial setup of the product is straightforward.

It doesn't take more than a week to implement the product.

As a part of the deployment process, you first need to understand the infrastructure of ServiceNow Discovery. Once you understand ServiceNow Discovery, you will be in a better position to use your data with the existing data in ServiceNow.

My company has a six-member team to take care of the product's implementation process.

There is a need to make payments every quarter of a year towards the licensing costs of the solution. ServiceNow Discovery is an expensive tool.

I rate the overall solution an eight out of ten.

I like ServiceNow Discovery's overall structure and the way data comes in without creating a different dashboard or interface. 

ServiceNow has a constant development environment. Hence they get constant bugs which result in incorrect performance. It should also improve customer service. 

I have been using the solution for quite some time. 

I would rate the solution's stability a ten out of ten. 

I would rate ServiceNow Discovery's scalability a ten out of ten. One of my current customers has over 10,000 users for the product. 

The product's setup is straightforward. 

The product is not cheap. 

I would rate ServiceNow Discovery a ten out of ten. You would need to go on training before using the solution. 

We are using ServiceNow Discovery for integration and we are populating the CMDB to use it for our ITSM.

The most valuable feature of ServiceNow Discovery is its performance.

ServiceNow Discovery could improve the interface. The navigation bar could improve. It would be helpful to have a landing page to go to find all the elements in one place.

I have been using ServiceNow Discovery for approximately three years.

ServiceNow Discovery is a stable solution.

I rate the scalability of ServiceNow Discovery an eight out of ten.

The scalability of ServiceNow Discovery is good.

We have approximately 5,000. We use the solution continuously in our enterprise-sized organization.

I rate the scalability of ServiceNow Discovery an eight out of ten.

The support from the vendor could improve. When we have an issue we speak to the agent in circles causing delays. There are a lot of unnecessary questions being asked.

I rate the support of ServiceNow Discovery a six out of ten.

Neutral

We did not use another solution prior to ServiceNow Discovery. We were doing everything manually.

The initial setup of ServiceNow Discovery is easy.

I rate the initial setup of ServiceNow Discovery an eight out of ten.

We have seen an ROI using this solution.

ServiceNow Discovery is expensive, but the company has a monopoly and we need to use the solution. We use it because we do not have a choice.

The solution does not require a lot of maintenance. Once the setup is done with schedules it operates well.

I would advise others to test the solution.

I rate ServiceNow Discovery an eight out of ten.

We are trying to discover the laptops, machines, network devices, and cloud inventory in our organization by using ServiceNow Discovery. We wanted to have a cross-check between the SCCM and Discovery, and are trying to decide which could be a better choice.

Basically, when we're talking about ServiceNow Discovery, we have our own instances, and we would be giving IP subnets into it. These IP subnets would contain the range of all the CI's, which are available in the network. Then, once we start the Discovery schedules, it can scan the network and fill in the data, whichever is available on the network. 

The initial setup is pretty easy.

The solution is fairly stable.

The security is very good. We have encryption supported from ServiceNow and therefore I haven't found any issues surrounding safety concerns. 

The solution lacks the capability of discovering the devices which are not in the network. That is an area where they could improve upon. In the next release, we are actually looking for a solution for the devices which don't come into the network. Nowadays, because of this pandemic, most of the users are logging in from home, and we don't have any way to discover those assets. We are looking for a solution that can help us to discover those kinds of user devices.

During the initial setup, we get some errors and the solution doesn't exactly understand what they mean or how to fix them. They need to have more of an explanation so that we can accurately go about fixing the errors as they arise.

Technical support has not been helpful when we have come across problems. They take too long to respond and then don't provide helpful information.

I've been using the solution for more than three years at this point.

The stability overall has been very good. It doesn't crash or freeze. There are no bugs and glitches. It's good.

We have been increasing pretty extensively. The users are running on a daily basis, and it is becoming one of the major sources for updating all the CI's that exist in the network.

We have an IT team of about 30 or more individuals that are on the solution.

We've had to reach out to technical support in relation to the errors we get during setup. They have not been very helpful overall. In most cases, when you raise a ticket, even when it is critical, they take two to three days to respond. Even then, the response really doesn't help us address the issue. We're not very satisfied with their level of support at this time.

It is not complex when setting up Discovery. It's pretty straightforward. That said, what happens is that after you set up the Discovery, there are different errors that you might get when you actually run the product, and that is something that needs to be improved. We get some errors and the solution doesn't give us the full information about what is causing the issue.

In terms of deployment times,  it has taken four months for the implementation of ServiceNow Discovery. The strategy was very straightforward. We just we activated the ServiceNow Discovery plugin and then we analyzed the data and started filling in the Discovery details.

We are implementing ServiceNow Discovery for our clients.

I do not know the exact cost, however, I do know that there is one particular subscription charge for the number of the CI spots we use.

We're also looking at SCCM and comparing the two solutions to see which would fit our organization better. The difference between the two, for the most part, is that ServiceNow is agentless, whereas, with SCCM, you need an agent.

We are an implementor. We implement this product for our clients.

We are using the latest version of the solution.

We use different deployment models - both on-premises and on the cloud.

This is one of the best tools for organizations looking for a tool with agentless applications. You do not need to install an agent in any of the CI's. However, if you go for the other solution like SCCM, that is an agent-based solution, where you need to install the agent on all your end-user computers. Therefore, if an organization is looking for an agentless solution, then probably ServiceNow Discovery is a great good option.

Users should have a thorough understanding of how CMDB data tables are structured, and they should also know how Discovery works. You should also have an idea whether you would be integrating asset management along with ServiceNow Discovery or not. If you are going with a flat ServiceNow Discovery, then later on, if you want to implement asset management, then it could be quite difficult. 

Overall, I would rate the solution at a seven out of ten. I would rate it higher, however, they aren't transparent when it comes to the meanings of errors we sometimes get during setup.

We primarily use this solution for three things: hardware asset management, software asset management, and IT service management.

Within our organization, there are 500 employees using this solution. We definitely plan to continue using this solution.

I find that the Discovery and scripting features are the most useful.

On the Software Asset Management part of it, I expect additional reconciliation and Discovery features there.

I have been using this solution for a year and a half.

ServiceNow Discovery is definitely stable. 

ServiceNow Discovery is easy to scale. It's got different bolt-ons, so you can scale up or scale down, as you require.

I have raised tickets with them. I've not had to deal with them that much, but I've raised a few tickets when dealing with them, and they're quite good.

The is no installation process. There are plugins, but most of the product is in the cloud. That's the attraction. It's a SaaS product, so a lot of it's in the cloud.

There is a subscription for ServiceNow Discovery. It's expensive, but I think it's one of the best solutions on the market, so it's worth it.

I would absolutely recommend ServiceNow Discovery to others. Overall, on a scale from one to ten, I would give this solution a rating of seven.

Primary use cases are below:

1. Infrastructure Discovery 

2. Perfect CMDB

3. Application Dependency 

4. More clarity on running software in the environment

5. Reduce the cost

Used this product for all environments

Based on discovered infrastructure, we made stable CMDB in customer environment and usage during change request.

• The security is a major part of the solution. Customers look for the best security.
• Console
• They provide the ability to see whatever customer wants to see into the Discovery tools . They offer the best tool view. 

In terms of improvement, I would like for it to be possible to use without coding. I would like dropdown ootion so that every customer can modify easily as per requirements and can understand it. They shouldn't need to learn Java or another scripting.

More than five years

It is very stable. It's very good. It's also scalable. Our clients are small, medium, and large size enterprises. 

Scalability is perfect.

The response time should be reduced for tickets. 

The initial setup is very straightforward. We need to provide some security information and that's it. It takes around one week to deploy all of the configurations, max. It depends on how customers move ahead with the process. 

Yes, we evaluated bmc, hp etc

I would recommend for ServiceNow. It's very good and straightforward.

I would rate it a nine out of ten. 

The dashboard should be more clear so that I can clearly see the errors. It should be a single console. I want it to be categorized by which specific issues everything is facing. 

We are primarily using Discovery to make sure that we have a single record in the CI, or a primary source of truth. Most of our customers are buying ServiceNow from the CMDB perspective as well as Discovery. Very few have moved on to the next level, which is the service mapping. Our primary use case is definitely in terms of the CMDB because they have all the processes working in silos including the SS or the CIs, it's all managed in silos. That is our biggest problem. Everybody has access to the CMDB so anybody can actually update the records. 

The other thing is that we wanted to make sure that they capture the CI, the relationship between the CIs. That is our other main objective and focus.

We are an elite partner of ServiceNow and I'm the solution architect for IT operations management.

The advantage of the solution is that it's a single system of record and it captures the relationship. I need to be able to enable the plugin for DRCOG data certification.

The patterns are the biggest area where improvement could be made. If there's no pattern for application X, then you can't discover that particular application. That is a drawback of the product. ServiceNow gives the URL or specifies an application they can discover and devices they can discover. But if the customer has something else, then it's a challenge. One of my customers had an NAS device and it couldn't discover it. If you don't have the back end of ServiceNow, then unfortunately it doesn't work.

None of this applies to iPhones. ServiceNow claims it can discover iPhones but the data is very limited. It's really not applicable.

I've been using Discovery for more than six years. 

I haven't had any issues with stability. 

I think the initial setup is more complex than it initially appears. 

Our client uses Qualys so I was comparing that with ServiceNow. The client already has Qualys in their infrastructure. They were hoping to continue using Qualys and ingesting the data into ServiceNow. That is not a helpful integration but I wanted to evaluate it so I will suggest they use ServiceNow separately. 

The advantage of ServiceNow is that it's a single system of record which allows you to build other modules on top of it. That's the advantage of ServiceNow, 

I would rate this product an eight out of 10.