To allow a MID Server to access servers using WinRM, the following configurations are required:

MID Servers need to be added to the WinRM Group policy on the Servers: This enables the servers to accept WinRM connections from the MID Servers and grant them the necessary permissions to execute commands and scripts 1 .

MID Server Parameters Add WinRM: This enables the MID Server to use WinRM as a protocol for Discovery and Orchestration and specify the WinRM port, authentication method, and encryption settings 2 .

The Credential Affinity table is a table that associates an IP address and a credential in Discovery 1 .  It is used to store the credential that was successfully used to access a device during Discovery 2 .  It can also be used to manually assign a credential to an IP address or a range of IP addresses 3 . The other options are not tables that associate an IP address and a credential in Discovery. The Service Affinity table is a table that associates a business service and a credential. The Service CI Association table is a table that associates a business service and a configuration item (CI). The Tags table is a table that stores tags that can be applied to records in any table.

The mid.discovery.max_pattern_payload_size property defines the maximum overall size for the returned payload that comes from patterns. This property is set on the MID Server and applies to all patterns that run on that MID Server. If the payload size exceeds this limit, the pattern execution fails and an error message is logged in the ECC queue.  The default value of this property is 10 MB 1 .

A horizontal discovery pattern is a series of operations that tell Discovery how to find and identify an application on a host 1 . To extract the build and version numbers from the config file, the pattern can use either of the following methods:

Parse File operation with Delimited Text parsing strategy: This operation reads the content of a file and splits it into fields based on a delimiter character.  The pattern can specify the delimiter as a space and the fields to extract as the second and fourth ones from the first line of the file 2 .

Parse File operation with Regular Expression parsing strategy: This operation reads the content of a file and matches it against a regular expression.  The pattern can specify the regular expression as  app build (\d+\.\d+\.\d+\.\d+) version (\d+\.\d+)  and the groups to extract as the first and second ones from the first line of the file 2 .

To launch any pattern, you need to specify the CI classification and the CI type. The CI classification determines the table where the discovered CI is stored in the CMDB, and the CI type defines the specific attributes and relationships of the CI. For example, if you want to discover a Windows server, you need to select the CI classification as  cmdb_ci_win_server  and the CI type as  Windows Server . These choices are mandatory for any pattern, as they enable Discovery to identify and classify the CIs correctly.

The CMDB contains records of configuration items (CIs) and their relationships. A CI is any component that needs to be managed in order to deliver an IT service, such as a server, an application, or a user. A relation type defines the nature of the connection between two CIs, such as depends on, uses, or contains. A model is a template for a CI that defines its attributes and default values. An asset is a tangible or intangible resource that is tracked and managed by the organization, such as a laptop, a license, or a contract.

In the ServiceNow Discovery module, under the Recommended Actions pane for an Automated Error Messages list within Discovery > Home, the possible options under ACTION ON ALL include "View instructions" and "Retry Discovery". "View instructions" allows users to see guidance on how to address the errors, while "Retry Discovery" enables users to reinitiate the discovery process for the affected devices. "Make Ranges" and "Ping IP Addresses" are not standard options in this context. References = ServiceNow Discovery documentation and user guides, particularly those discussing the management of automated error messages and recommended actions in Discovery.

In the context of ServiceNow Discovery patterns, the types of temporary variables include Scalar/List and Tabular/Table. Scalar/List variables are used to store single values or lists of values, while Tabular/Table variables are used to store structured data in a table format. Command and SQL statement are not types of temporary variables; rather, they are types of operations or steps that can be used within a pattern to execute commands or SQL queries. References = ServiceNow Discovery documentation, especially sections related to Discovery Patterns and the use of temporary variables within patterns.