Which of the below choices are needed for Quick Discovery? (Choose two.)
Quick Discovery is a wizard that helps you get up and running with Discovery quickly. It discovers both physical and logical components, including virtual machines, servers, storage, databases, applications, and more. To use Quick Discovery, you need to have a MID Server installed and configured, and provide a target IP range or subnet to scan. You do not need to create a Discovery Schedule or a PID for Quick Discovery.
One method for deleting specific CIs not discovered in 30 days is:
One method for deleting specific CIs not discovered in 30 days is to use a scheduled job that runs a script to query the CMDB for CIs that have not been updated by Discovery for a certain period of time, and then delete them or mark them as retired. This method can help you keep your CMDB clean and accurate, and avoid having stale or obsolete CIs. You can configure the scheduled job to run at a specific frequency and time, and specify the criteria for selecting the CIs to delete.
How do you create relationships between Cis in a horizontal pattern?
In ServiceNow Discovery, relationships between Configuration Items (CIs) in a horizontal pattern are created using the 'Create Relation/Reference' operation. This operation allows the pattern to define and establish relationships or references between discovered CIs, based on the information gathered during the discovery process. Options B and C are incorrect as relationships are not automatically created nor is it true that they cannot be created via patterns. Option D, 'Create Connections,' is not a standard operation in this context. Reference = ServiceNow Discovery documentation, specifically the sections on creating and managing horizontal discovery patterns.
When installing a MID Server on a Windows platform, which right must be associated when creating a Service Account?
The Service Account for the MID Server must have the Log on as service right on the Windows platform. This right allows the MID Server to run as a Windows service and communicate with the ServiceNow instance. The Service Account does not need to have local or domain admin rights, as these are not required for the MID Server functionality. The MID Server User Role is a role on the ServiceNow instance, not on the Windows platform, and it is used to control the access and permissions of the MID Server on the instance.
Correcting MID Server Windows service account user and permissions
What is a ServiceNow MID Server and how does it work?
Configure Windows MID Server service credentials
Nathan Nelson
5 days agoAmanda Rivera
28 days agoEdward Williams
1 month agoWilliam Peterson
2 months agoJoseph White
2 months agoBetty Robinson
2 months agoNathan Parker
2 months agoAshley Bailey
2 months agoAdam Gonzalez
2 months agoRichard Ramirez
2 months agoArdella
3 months agoBernardo
3 months agoLaurel
3 months agoMartina
4 months agoJennifer
4 months agoVerona
4 months agoClarinda
5 months agoFrance
5 months agoRegenia
5 months agoGladys
5 months agoRosalind
6 months agoGolda
6 months agoOliva
6 months agoKenny
6 months agoGeorgiana
7 months agoRodrigo
7 months agoTijuana
7 months agoThomasena
7 months agoGraciela
8 months agoWeldon
8 months agoQuentin
8 months agoNathalie
8 months agoNoah
9 months agoArgelia
9 months agoRupert
9 months agoFelix
9 months agoTeresita
10 months agoKirk
10 months agoAmie
12 months agoClare
1 year agoTiera
1 year agoKimberlie
1 year agoAmie
1 year agoErinn
1 year agoAlbert
1 year agoShantay
2 years agoCaprice
2 years agoPatria
2 years agoMozell
2 years agoDominga
2 years agoDevora
2 years agoLenna
2 years agoIlona
2 years agoSunny
2 years agoEna
2 years agoGoldie
2 years agoClarinda
2 years agoIra
2 years agoGrover
2 years agoSabrina
2 years agoMeaghan
2 years agoBarney
2 years agoBilly
2 years ago