How Discovery updates the install status for server class CIsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Install Status during pattern-based discovery of server class CIs During a successful pattern-based discovery, the Install Status field (install_status) is updated for server class configuration items (CI) to indicate that if the server is up and discoverable, it must not be in a terminated state. Only computer and server CIs discovered through the Discovery feature and using pattern-based discovery use this logic. Other features that populate the CMDB and Discovery patterns for other hardware classes do not. The responsible script runs for the following Discovery patterns: AIX Server > AIX Server [cmdb_ci_aix_server]HP-UX Server > HPUX Server [cmdb_ci_hpux_server]Hyper-V Server > Hyper-V Server [cmdb_ci_hyper_v_server]IBM zOS Server > IBM zOS server [cmdb_ci_ibm_zos_server]Linux Server > Linux Server [cmdb_ci_linux_server]Solaris Server > Solaris Server [cmdb_ci_solaris_server]Windows OS - Desktops > Computer [cmdb_ci_computer]Windows OS - Servers > Windows Server [cmdb_ci_win_server] In the latest versions of Visibility Content, this is present in the Update Server Status Fields script, but previously it was in the OSs - Pre Sensor script. These scripts are visible in the sa_pattern_prepost_script table. The following logic has been used to determine Install, Operational, and Hardware status of server class CIs: 1) Set Install Status to Installed only if the install status of the server is Absent, Retired, or Stolen. 2) Set Operational Status to Operational if both the following are true: glide.discovery.patterns.server_update_operational_status system property is true. The default system property is false. Current operational status of the server is Retired. 3) Set the Hardware Status to Installed if both the following are true: glide.discovery.patterns.server_update_hardware_status system property is true. The default system property is false.Current hardware status of the server is Retired or Stolen Install Status during VMware vCenter Discovery During vCenter ESX host discovery, you can determine if a target ESX server is in maintenance mode, therefore the install_status is set during the probe execution. The install_status is calculated using the following EXS probe script: /nav_to.do?uri=ecc_agent_script_include.do?sys_id=7c6ff0ef93c31200c2fe705bb47ffb32%26sysparm_view=discovery The responsible line is: host.install_status = runtime.maintenance ? '3' : '1';// Maintenance = 3, Installed = 1 For ESX server CIs, the logic is summarized as follows: Set Install Status to Maintenance if the vCenter describes the ESX Server as presently being in Maintenance mode, otherwise set Install Status to Installed. This can result in an ESX server set to Install Status of Installed, overwriting any manual changes. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Note: This applies to changes of install_status during discovery of the server class CI. Other changes to install status may occur as a result of Cascade Business Rules designed to update child CI statuses in response to changes on parent CIs. For example, the deletion strategy used for a cloud discovery pattern identifies that a particular VM instance is now retired. It may cascade this retired install status to the Windows server virtualized by the VM instance. The following knowledge article describes this scenario. KB0863733 - Install status (install_status) of windows servers(cmdb_ci_server) is being set to "retired"