Trying to run a VBscript in Low priority. "start /low wscript.exe vbscript.vbs" appears to work, and child processes of the script appear to inherit this low priority.

One of the child processes is "msinfo32.exe" (System Information). It too runs in low priority. But when System Information makes WMI calls (wmiprvse.exe), they are not inheriting this Low priority, and instead, are running in Normal priority. Need to know how to ensure that any and all WMI calls from the script only use Low priority [including objWMIService.ExecQuery("SELECT * FROM xxxx_Process") if I need to use it]

Thanks,

David