Our company has historically used the solution for IT infrastructure. We started deploying the solution in 2017 and have moved through nine versions since then. We are partners with ServiceNow and have a very good relationship with them.

Recently, we established a complete platform that will allow us to do IT infrastructure software and OT assets for manufacturing. We have planned a very long journey with ITSM and Discovery. 

We are working on a new deployment in Asia that includes the new Discovery version on Orchestration and the Automation Engine in Tokyo. We will soon be onboarding HRSD, Legal Service Delivery, OT for manufacturing, and ESG. We have a developed a very complete roadmap.

Our company deploys for enterprise businesses ranging from 10,000 to 1.5 million employees. 

We're running Discovery on several IP ranges to discover objects in the network. We can run Discovery on-prem through APIs or use it with cloud environments like AWS and GCP and Azure. 

The primary use case for ServiceNow Discovery involves collecting software and hardware data from devices, enabling comprehensive mapping of services and applications, including SLAs and KPIs.

We just have some use cases of discovering some products from the hotels that we support. For example, basic configuration items, assets, importing them, the servers, the data centers, and all that information to be stored in our system, building the CI relationship, etcetera. So, the basic needs of any organization.

We used the product to manage our desktop assets. We were expanding it to use the rest of the technology assets. The technology assets would be populated from Tanium. It is an incredibly valuable tool for what we need.

You can use it for network resources, servers, databases, and network gear. I've also used it in the past for asset management to discover desktop equipment, laptops, and peripherals.

I believe the tool itself isn't solely about identifying assets, as many tools can perform IP-based and port-based discovery. That's not the most challenging aspect; it's a well-established practice. The real value lies in how it integrates into a system that everyone can utilize, and it does so rapidly. I've been using it for quite some time, and it's not just about the tools; it's about the people, organizational processes, and how they contribute to the success of these tools.

Primarily, we use Discovery to discover and maintain our CIs (Configuration Items). It also has the potential for subscription management, but we're not currently using it for that.

One of our key use cases is tracking laptops assigned to employees within our organization. We need to monitor their usage patterns and performance. We start by using Discovery to populate a database with details about computers, servers, and SNMPs. 

Then, we integrate with a third-party tool for monitoring. If issues arise, they raise a ticket in ServiceNow, allowing us to proactively address problems.

ServiceNow offers many other features with Discovery, but it takes time to learn and implement them effectively. We've started with out-of-the-box solutions, customized them to our needs, and are gradually upgrading our processes.

So, it does take some time for someone to learn Discovery, or any other ServiceNow product.

I also primarily work with ITSM modules like incident, problem, and change management. I also use IT Operations Management (ITOM) products like Discovery, Service Mapping, and Operations Management.

We use Discovery and Operations Management to manage our CIs. Additionally, we use incident, problem, change, and knowledge management for ITSM (IT Service Management). It's like a ticketing service.

My company tries to get information from the client network to populate CMDB more effectively with ServiceNow Discovery. ServiceNow Discovery is a much more reliable software or process that helps our company get more information about our network components.

ServiceNow Discovery is useful for discovering the servers, like the servers of Windows and Linux, from the client network.

Discovery is predominantly used for predictive monitoring and auto self-healing to reduce manual work and automate remediation of IT incidents, problems, and changes. 

Discovery is foundational for knowing your infrastructure and application components and is key to building a foundation for achieving a target state.

We use this solution to populate the CMDB and to track changes in our environment.

Our company uses the solution's to discover infrastructures. The ServiceNow instance is in the cloud and the Discovery servers are on-premises. 

We have five licensed configuration management practitioners and 3,000 end users. 

We use it to gather information from cloud environments such as Azure and GCP. The aim is to conduct scans for various assets, including laptops, desktops, servers, and software. This process extends to retrieving details from the client's database within their cloud infrastructure.

I use the tool for IT change management. 

Our primary use case for the solution is compliance, understanding our assets, and mapping it against our business for services.

ServiceNow helps us keep our CMDB updated and populated with all the necessary information. 

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

This is a part of ITOM. We use the product to identify servers and network equipment in our data centers.

I can't discuss the use cases related to the product since I don't have many projects to deal with in my company that need the use of ServiceNow Discovery.

Primarily for discovering and managing organizational assets and tools. We maintain the hierarchy of all the assets, and if there are any issues, we can remotely configure them without any problems. So, it's useful for that purpose and a high-level overview.

The solution is for all of our infra components.

We use ServiceNow Discovery to update our CMDB and to discover the used software assets. In one flow, we can run all the scripts necessary for ITOM for the CMDB and software asset management.

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

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.

My role right now in present projects is to deploy ServiceNow Discovery both on AWS cloud an on-premises. ServiceNow Discovery is populated directly into ServiceNow CMDB, so its use cases include managing CMDB identification and reconciliation, as well as creating dashboard reports and other types of reports.

We use ServiceNow Discovery to look at assets, processes, and some process mining. On the other hand, we use ServiceNow ITSM to capture tickets and move away from Remedy. We also use ServiceNow ITSM APIs for contract management, focusing on change, configuration, release, incidents, and problems.

I am a consultant. We implement solutions for our clients.

The primary use case of this solution is to automate inventory management, asset management, and discovery. It also used to integrate with other monitoring tools for instant management change.

Mainly, the primary use case would be the automatic management of inventory.

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

When my team starting any project or learning a new environment, we always implement ServiceNow Discovery which can be used along with other products. We are able to extract details on the environment to help transition services.

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.

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.

I am a consultant and I work with IT service management solutions such as ServiceNow Discovery.

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.