Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Configuration Management System (CMS)2018.05

Use > Data Flow Management > Universal Discovery > Introduction to Universal Discovery > Script-based vs Scanner-based Discovery

Script-based vs Scanner-based Discovery

Universal Discovery performs inventory discovery using the following discovery methods.

Note

Selecting a discovery method depends on your organization's policy and business goals.
More than one discovery method can be used.

Script-based discovery

This type of discovery was originally implemented in DDMA.

Script-based discovery is often called "agentless" because it is typically implemented without agents installed on remote nodes. However, it is possible to run these jobs with a Universal Discovery Agent installed.

This type of discovery is best suited for organizations where deployment effort must be minimal, footprints on remote nodes are a primary concern, and information about running software is critical.

Scanner-based discovery

This type of discovery was originally implemented in DDMI.

Scanner-based discovery uses a software component called the Scanner- an executable file that runs on the remote node. The Scanner is deployed to remote machines and runs according to a schedule that you configure. It can run automatically using Activities, or run manually.

Scanner-based discovery is best suited for organizations where a high degree of details about installed software and hardware is needed.

Script-based vs Scanner-based Discovery Comparative Matrix

Attribute/Discovery Method	Script	Scanner
Deployment Component	None	Executable file
Connection Method	Agent or Agentless	Agent or Agentless
Execution Methods	Automatic (Activities) or Manual	Automatic (Activities) or Manual
Discovery Method	APIs	Executable file (Scanner)
Scan Type	Specific data sets	Entire file system
Information Collected	Running software	Installed software, Hardware
Information Detail	Moderate	High
Performance Impact on Node	None	Minimal
Scalability	High. Discovery job quickly triggers subsequent jobs.	Minimal. Scanning job must wait to finish before triggering subsequent jobs.
Footprint on Node	None	Minimal

For details on Universal Discovery Agents, see (Suite Only) Universal Discovery Agent Overview.

For details on Scanners, see Inventory Discovery Scanners.

Related Information

Send Help Center feedback