VMware Management Pack registry settings
The Windows registry keys that control the VMware Management Pack collector, their defaults and how to change them.
Applies to: OpsLogix VMware Management Pack (all versions) · SCOM 2019, 2022, 2025
Last updated: October 2026 · Reading time: 3 minutes
Change these settings only when OpsLogix support asks you to, or when you know what effect the change has. Make the same change on every management server that runs the OpsLogix VMware Collector, then restart the Microsoft Monitoring Agent and OpsLogix VMware Collector Service.
Where the settings are
| Scope | Registry key |
| All management pack modules | HKLM\SOFTWARE\OpsLogix\VMware |
| One workflow | HKLM\SOFTWARE\OpsLogix\VMware\Client Modules\<ACTION>\<TYPE> |
| OpsLogix VMware Collector | HKLM\SOFTWARE\OpsLogix\VMware\Collector |
| VMware MP Configuration dashboard (console computer) | HKLM\SOFTWARE\OpsLogix\VMware\ui |
For module settings, a value under the workflow key wins. If there's none, the value under HKLM\SOFTWARE\OpsLogix\VMware is used, and otherwise the built-in default. Exception: UseCaching is only read from HKLM\SOFTWARE\OpsLogix\VMware. A UseCaching value under a workflow key has no effect (known issue).
<ACTION> is DISCOVERY, MONITORING or PERFORMANCE. <TYPE> is the kind of data, for example GENERIC, RESOURCEPOOL, VIRTUALMACHINE, VIRTUALMACHINESNAPSHOT, HOSTSERVICE, DATASTORE, HARDWARE, VSAN, VSANSKYLINE, APPLIANCE, ALARM, GUEST, COMMITMENT or RANSOMWARE. Example: Client Modules\DISCOVERY\VIRTUALMACHINE. To find the ACTION and TYPE of a workflow, set DebugMode to 5: every run then logs Starting new workflow.'ACTION:TYPE' in the Operations Manager event log.
Module settings
| Value name | Type | Default | What it does |
| DebugMode | REG_DWORD | 3 | Logging level: 0 = nothing, 1 = critical, 2 = errors, 3 = warnings, 4 = information, 5 = trace. See Enable debug logging. |
| TimeOutSec | REG_DWORD | 1800 (discoveries), 360 (monitoring) | How long, in seconds, a module waits while sending its data to SCOM. |
| PBPageSize | REG_DWORD | 0 (discoveries, no batching), 350 (monitoring) | How many property bags a module sends to SCOM in one batch. |
| UseCaching | REG_SZ: true or false, or REG_DWORD: 1 or 0 (1 or 0 from version 26.10.4540.0) | false (discoveries), true (monitoring) | Only send data to SCOM when it has changed. Unchanged data is sent again after CacheTtlSec. Guest disk data is never cached. |
| CacheTtlSec | REG_DWORD | 1800 | How long, in seconds, cached data is kept before it's sent again. |
| IsBatchLogicalSet | REG_SZ: true or false, or REG_DWORD: 1 or 0 (1 or 0 from version 26.10.4540.0) | false | Send each batch as one logical set. Only change this when OpsLogix support asks you to. |
Collector settings
| Value name | Type | Default | What it does |
| DebugMode | REG_DWORD | not set (uses the collector's own configuration) | Logging level of the collector, same values as above. |
| EmulationMode | REG_SZ: true or false, or REG_DWORD: 1 or 0 (1 or 0 from version 26.10.4540.0) | false | For OpsLogix support only. Don't set this on a production system. |
Note: from version 26.10.4540.0, the settings that take true or false also accept 1 or 0, as REG_DWORD or REG_SZ. Earlier versions only accept the string values (REG_SZ) true and false, and ignore a REG_DWORD value.
Caching: with UseCaching on, a monitoring workflow doesn't send an object's data again while it hasn't changed, until CacheTtlSec has passed. SCOM keeps the last health state, so monitors are not affected. Before version 26.10.4540.0, caching only worked for workflows that send more than 350 objects, and a UseCaching value under a workflow key was ignored. Both work from version 26.10.4540.0.
The settings CacheClearCount, Parallelism and MOBPageSize from older articles are no longer used.
Warning: at trace level (5 or higher), the management pack modules also log their workflow configuration. That includes the encrypted vCenter password and the license key. Turn trace logging off as soon as you're done, and share the event log only with OpsLogix support.
Note: to remove the dashboard setting, delete the whole HKLM\SOFTWARE\OpsLogix\VMware\ui key, not only the DebugMode value. If the ui key exists without a DebugMode value, the VMware MP Configuration dashboard doesn't load.
Examples
rem Trace logging for the virtual machine discovery only
reg add "HKLM\SOFTWARE\OpsLogix\VMware\Client Modules\DISCOVERY\VIRTUALMACHINE" /v DebugMode /t REG_DWORD /d 5 /f
rem Give all discoveries 45 minutes to send their data
reg add "HKLM\SOFTWARE\OpsLogix\VMware" /v TimeOutSec /t REG_DWORD /d 2700 /f
rem Turn caching off for virtual machine monitoring only (26.10.4540.0 and later)
reg add "HKLM\SOFTWARE\OpsLogix\VMware\Client Modules\MONITORING\VIRTUALMACHINE" /v UseCaching /t REG_DWORD /d 0 /f
Run these commands as administrator. Note that TimeOutSec under HKLM\SOFTWARE\OpsLogix\VMware applies to monitoring workflows too.