Missing Virtualized by::Virtualizes relationships between your Windows Server CIs and the corresponding VM Instance CIs.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: ; } } Missing Virtualized by::Virtualizes relationships between your Windows Server CIs and the corresponding VM Instance CIs.- where Windows server and VM instances have only a few relationships created for CIs- check the CI and its related list under 'Related items' - check examples of other CIs where where there is no link between Server and VM 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: ; } } all 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: ; } } While identifying the missing Virtualized by::Virtualizes relationships between your Windows Server CIs and the corresponding VM Instance CIs. - The Windows Discovery pattern includes a step (40.2 Windows - Azure) that runs ConfirmAzureVM.ps1 to confirm a server is an Azure virtual machine and write its Azure resource identifier (correlation_id) to the Windows Server CI - The correlation_id is what the platform uses to match the Windows Server CI to its VM Instance CI and create the relationship - For all affected CIs, this step is failing before it can execute - The failure is caused by the MID Server being unable to load a required PowerShell module (DiagnosticsUtil.psm1) into the remote WinRM session on the target host - Without correlation_id being populated, the relationship creation step has nothing to match against and no relationship is written to the configuration management database The exact error observed during investigation is: "Failed to put file C:\MID\agent\bin\sw_wmi\bin\ConfirmAzureVM.ps1 on host xx.xx.xx.xx. Detailed error: importModuleIntoSession : Could import module C:\ProdMID\agent\scripts\PowerShell\DiagnosticsUtil.psm1 into remote session (xx.xx.xx.xx). Original exception: The term 'New-Module' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." Why does this affect some CIs and not others?: - CIs first discovered before this issue began had their correlation_id populated at that time and their relationship was created then — it has not been updated since - CIs first discovered after the issue began never had correlation_id populated and therefore have no relationship There are two likely causes: - PowerShell execution policy restrictions on the MID Server host or target hosts are blocking custom module loading — this is the most common cause and the simplest to resolve - The WinRM Just Enough Administration constrained endpoint configured on MID Servers does not include New-Module in its list of permitted commands, preventing the MID Server from loading its required modules into remote sessions 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: ; } } 1. Check and update the PowerShell execution policy - Log on to the MID Server host machine directly (via Remote Desktop or console access) - Open PowerShell as Administrator - Run the following to check the current execution policy: powershell Get-ExecutionPolicy -List - If the policy at LocalMachine or MachinePolicy scope is set to Restricted or AllSigned, update it: powershell Set-ExecutionPolicy RemoteSigned -Scope LocalMachine - Re-run Discovery against one of the affected CIs and confirm whether correlation_id is now populated on the Windows Server CI and whether the relationship is created 2. If the issue persists, review the Just Enough Administration endpoint configuration If step 1 does not resolve the issue, please involve whoever manages the WinRM and Just Enough Administration configuration on your MID Server hosts and ask them to: - Log on to the MID Server host machine and open PowerShell as Administrator - Run the following to review the permitted commands in the Just Enough Administration endpoint: powershell Get-PSSessionConfiguration -Name "MID_jea_servicenow_disco" | Select-Object -Property * - Check whether New-Module is included in the permitted commands list - If it is not, add it to the allowed cmdlets in the Just Enough Administration session configuration file (.pssc) and reload the configuration Once the fix is applied:- Before re-running Discovery, confirm the fix has taken effect by running the following directly on the MID Server host machine in PowerShell as Administrator: powershell Import-Module "C:\ProdMID\agent\scripts\PowerShell\DiagnosticsUtil.psm1" - If the module loads without error, the fix is confirmed and Discovery can be re-run - If the module still fails to load, review the execution policy and Just Enough Administration configuration again before proceeding - Re-run the virtual machine schedule Discovery against all affected CIs - Confirm that correlation_id is populated on the Windows Server CI after the run - Confirm that the Virtualized by::Virtualizes relationship is created in the CI Relationships table - Note that existing affected CIs will require a Discovery re-run to trigger relationship creation — the fix alone will not back-populate existing records