SQL Server edition not consistently identified during discovery Issue <!-- /*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: ; } } During discovery, the SQL Server edition is not always being picked up, with some instances showing the edition information successfully retrieved while others do not. The issue was observed in specific SQL Server instances where the 'edition' field remained empty in the CMDB despite the discovery process executing the command successfully when run manually with the correct credentials. Symptoms<!-- /*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: ; } } Commands to fetch edition details is giving blank results during pattern execution/Debug. 4 get edition2026-07-05 00:04:11: Executing WMI command on host: x.x.x.x, command: "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\sqlservr" -v -sMSSQLSERVER2026-07-05 00:04:11: Command result:2026-07-05 00:04:11: Execution time: 317 ms 5 get edition 22026-07-05 00:04:11: Executing WMI command on host: x.x.x.x, command: "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\sqlservr" -v -sMSSQLSERVER2026-07-05 00:04:11: Command result:2026-07-05 00:04:11: Execution time: 259 ms7 set edition2026-07-05 00:04:11: Step condition is false. step not executed. False Condition(s): [(${edition} : value=) IS NOT EMPTY ]2026-07-05 00:04:11: Execution time: 0 ms --------->Expected is something like below: 4 get edition2026-07-06 20:28:58: Executing WMI command on host: x.x.x.x, command: "C:\Program Files\Microsoft SQL Server\MSSQL13.xxxxx_TEST\MSSQL\Binn\sqlservr" -v -xxxxx_TEST2026-07-06 20:29:00: Command result:2026-07-06 20:28:59.96 Server Logging to event log is disabled. Startup option '-v' is supplied, either from the registry or the command prompt.2026-07-06 20:28:59.99 Server Microsoft SQL Server 2016 (SP3-CU1) (KB5014242) - 13.0.7000.253 (X64)May 7 2022 03:06:40Copyright (c) Microsoft CorporationDeveloper Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor) Facts<!-- /*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: ; } } The below command is executed with respect to target device from mid server with same discovery credentials. "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" -v -sMSSQLSERVER When executed directly in target it gives us result.so to determine actual cause enable "mid.log.level=debug ". We fetch the edition details from applicative credentials.if those are not configured the pattern tries to check if discovery user has "Admin$" privileges or having Read /Write access to temp folder and registry path.if that does not exist it fails and which can be seen in mid server logs. Release<!-- /*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: ; } } Zurich Cause<!-- /*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: ; } } 1. The MID Server failed to identify a valid temporary directory on the target server due to access denied errors when reading the Windows registry (HKEY_CURRENT_USER\ENVIRONMENT\TMP). The C$ admin share was not accessible from the MID Server, preventing the staging of temporary scripts required for executing SQL commands. The discovery process could not proceed due to these issues, resulting in missing edition details in the CMDB. Resolution<!-- /*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: ; } } In the attached screenshot we found network path not found error.In mid server logs we see access denied error with registry path// Access denied when reading HKEY_CURRENT_USER\ENVIRONMENT\TMP -->In that case please ask customer to check with you windows admin team.During discovery, the MID Server attempts to stage a temporary PowerShell script on the target machine to execute SQL queries.To do this, it needs a writable temporary directory on the target. It tried the following in order:Read temp path from Windows registry — FAILED// Access denied when reading HKEY_CURRENT_USER\ENVIRONMENT\TMP// Log: "Could not get user temp dir using registry. Error: Access denied"Query WMI Win32_BootConfiguration for temp directory — SKIPPED// Found a system32-based path, intentionally avoided for security// Log: "We cannot use system32 based dir found in Win32_BootConfiguration\TempDirectory, will not use"Defaulted to C:\temp via admin share — FAILED// C$ admin share is not reachable from the MID Server// Log: "Test-Path : The network path was not found"// Log: "Attempting to create unsecure temp folder \\x.x.x.x\c$\temp\As a result, the discovery pattern could not proceed, and no SQL Server data was collected.Solution:1.Advise customer to engage their windows admin team to resolve the registry access issue ("Access denied when reading HKEY_CURRENT_USER\ENVIRONMENT\TMP") or ensure the C$ admin share is accessible from the MID Server.2.Ensure the C$ admin share is enabled and accessible from the MID Server using the discovery credentials. 3.Retry the discovery process after addressing the above issues to ensure the SQL Server edition is correctly populated in the CMDB.