MSSql DB On Windows Pattern Execution via ACC AgentThe MSSql DB On Windows pattern runs on the ACC agent to discover and populate CMDB CIs including cmdb_ci_db_mssql_instance, cmdb_ci_db_mssql_database, and related tables. The following are known issues observed during ACC-based execution of this pattern. Issue 1: wmic returning literal command string instead of data PRB number: PRB2054638Affected section: Collect MSSQL Components Info — "get all sql components" and "get all sql service info" Description:The pattern uses wmic /NAMESPACE:\\root\Microsoft\SqlServer\... to query SQL service properties. On ACC agent execution, these commands return the literal command string as output rather than actual WMI data. This is distinct from an allow list block — the command is allowed but produces no usable output. Root cause: The pattern uses wmic, which is deprecated and removed by default on Windows Server 2025. On other Windows Server versions, the command falls into a legacy branch — the existing code only routes to Get-CimInstance for Windows 10/11, so all Server versions take the wmic path. Fix requires replacing wmic calls with Get-CimInstance/Get-CimClass equivalents. Impact: mssql_components_info and mssql_sqlservice_info not populated; SQL component and service data missing from CMDB CI. Issue 2: split-path allow list block — pipe operator broken by cmd evaluation PRB number: PRB2085977Affected section: Collect MSSQL Components Info — "delete generated report after parsing" Description:The pattern command uses a PowerShell pipe:powershell "<setup.exe path>" | split-path -parent | split-path -parent When executed via ACC's executeCommand, the command is wrapped and delegated to cmd /c. Because cmd does not treat single quotes as quoting characters, it interprets the | as a shell pipe, splits the string into pipeline stages, and attempts to resolve split-path as a standalone executable on PATH. The command fails with: 'split-path' is not recognized as an internal or external command, operable program or batch file. This cannot be fixed by escaping at the pattern level — the quoting is stripped before cmd parses. Impact: Report cleanup after parsing fails; downstream steps that depend on the resolved path receive null, causing further failures.