Parsing issue on "Windows OS - Servers" OOB pattern, step "40.2.3 Run the script" while the MID Server name have spaces Issue While the Discovery executes Windows OS Server Pattern with a MID server having spaces in the name, would cause parsing issues on the Steps below Put script checking if this server is running on AzureRun the Script Example Step: 40.2.2. Put script checking if this server is running on Azure 2023-05-10 02:14:20: Attempting to Put file on Windows host xx.xx.xx.xx filePath: C:\Program Files\<Target_Folder>\agent\bin\sw_wmi\bin\ConfirmAzureVM.ps12023-05-10 02:14:23: Put file on Windows host xx.xx.xx.xx sucess, file location is c:\temp\<Instance Name>\<Target Folder>\ConfirmAzureVM.ps12023-05-10 02:14:23: setAttribute(scriptPath,c:\temp\<Instance Name>\<Target Folder>\ConfirmAzureVM.ps1)2023-05-10 02:14:23: Execution time: 2282 ms The above step will place the "ConfirmAzureVM.ps1" file to a temp location on the MID Server for execution, the "Target Folder" is named exactly as MID Server,Like, example the MID Server name as "MID_Server", then the location placed would be c:\temp\<Instance Name>\MID_Server\ConfirmAzureVM.ps1 Example the MID Server name as "MID Server", then the location placed would be c:\temp\<Instance Name>\MID Server\ConfirmAzureVM.ps1 Looking at the above examples, the second example have the MID Server name with spaces Step: 40.2.3. Run the Script If the Script executed with MID Server with name have no spaces, it would execute successfully Script executed successfuly2023-06-14 00:16:13: Executing WMI command on host: xx.xx.xx.xx, command: powershell.exe -ExecutionPolicy Bypass -File "c:\temp\<Instance_name>\MID_Server\ConfirmAzureVM.ps1"2023-06-14 00:16:20: Command result: True2023-06-14 00:16:20: setAttribute(isAzure,True)2023-06-14 00:16:20: Execution time: 7184 ms If the Script executed with MID Server with name have spaces, it would fail with below error 2023-05-10 02:14:23: Executing WMI command on host: xx.xx.xx.xx, command: powershell.exe -ExecutionPolicy Bypass c:\temp\<Instance_Name>\MID Server\ConfirmAzureVM.ps12023-05-10 02:14:31: Command result:c:\temp\<Instance_Name>\MID: The term 'c:\temp\<Instance_Name>\MID' 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 andtry again.At line:1 char:1+ c:\temp\<Instance_Name>\MID Server\GITDIR_svc-SNOW-Dscry\ConfirmAzur ...+ ~~~~~~~~~~~~~~~~~~~+ CategoryInfo : ObjectNotFound: (c:\temp\<Instance Name>\MID:String) [], CommandNotFoundException+ FullyQualifiedErrorId : CommandNotFoundException If we notice, the error c:\temp\<Instance_Name>\MID: The term 'c:\temp\<Instance_Name>\MID' is not recognized as the name of a cmdlet, function, script file, The actual file path should be c:\temp\<Instance_Name>\MID Server\ConfirmAzureVM.ps1 But the script is taking 'c:\temp\<Instance_Name>\MID' The issue is because the MID Server name have spaces and the script can only execute until the first space of the MID nameReleaseIssue observed in Sandiego and Tokyo releases CauseThe cause of the issue is that the Step: 40.2.3. The script path in the Run the script is not parsing the below command while execution Set Command Details value: "powershell.exe -ExecutionPolicy Bypass " + $scriptPath ResolutionIssue fixed in Utah release in OOB As workaround for San Diego and Tokyo releases, edit the 40.2.3. in "Windows OS Pattern" From Set Command Details value: "powershell.exe -ExecutionPolicy Bypass " + $scriptPathTo Set Command Details value: "powershell.exe -ExecutionPolicy Bypass -File " + "\"" + $scriptPath + "\""