Credential-less Discovery — Which CMDB classes are created?Summary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Teams want to understand CMDB impact and class mapping when hosts are discovered without credentials. How it works: - When credential-based probes cannot authenticate, Discovery invokes Credential-less Discovery using Nmap from the MID Server. - Nmap collects basic identifiers (e.g., IP/hostname, sometimes MAC) and attempts an OS family fingerprint. - Based on the detected OS family, ServiceNow creates or updates one host CI and assigns the corresponding server class. - If the OS cannot be determined reliably, the CI is created/updated in the base hardware class. - When valid credentials become available later, a credentialed Discovery run updates the same CI (via IRE) rather than creating a duplicate. Resulting CMDB class (mapping by OS family) - Windows → cmdb_ci_win_server - Linux → cmdb_ci_linux_server - AIX → cmdb_ci_aix_server - HP-UX → cmdb_ci_hpux_server - Solaris → cmdb_ci_solaris_server - OS X / macOS → cmdb_ci_osx_server - Unknown / undetermined OS → cmdb_ci_hardware All of the above server classes inherit from the hardware lineage; if OS fingerprinting is inconclusive, Discovery uses the base hardware class. Controls & scope (what influences outcomes) - Credential-less Discovery must be enabled and Nmap available on the MID Server. - The ports Nmap scans (which affect OS fingerprinting quality) are governed by your IP Services configuration (cmdb_ip_service) used by Discovery’s port scanning model. - The class assignment strictly follows the OS family signal from Nmap; no credentialed probes = no deep hardware/software details at this stage. In Short: - Yes, Credential-less Discovery can create server-class CIs when the OS family is recognized (e.g., cmdb_ci_win_server, cmdb_ci_linux_server, etc.). - If OS cannot be determined, Discovery creates/updates the CI in cmdb_ci_hardware. - Later credentialed scans enrich and continue updating the same CI (no duplicates) once credentials succeed. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Credential-less host DiscoveryCredential-less Discovery with Nmap