Deployment Command Timeout Seconds

All management servers in a management group, this helps with deployment of heavy handed scripts that are applied during version upgrades and cumulative updates. Customers often see blocking on the DW database for creating indexes, and this causes the script not to be able to deployed in the default of 3 hours (10800 seconds). Setting this value to allow for one full day to deploy the script resolves most customer issues. Setting this to a longer value helps reduce the 31552 events you might see with standard database maintenance after a version upgrade or UR deployment. This is a very common issue in large environments are very large warehouse databases.

This policy create registry key: "HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse\" and REG_DWORD Decimal Value: "Deployment Command Timeout Seconds".
SCOM 2012 existing registry value: not preset (must create "Data Warehouse" key and value).
To delete REG_DWORD value from registry, disable this policy.

Default in code value = 10800 seconds (3 hours).
Minimum value (in this group policy template) = 10800
Maximum value (in this group policy template) = 86400 seconds (1 day)
Recomended value for large environments: 86400

Supported on: System Center 2012 Operations Manager


Registry HiveHKEY_LOCAL_MACHINE
Registry PathSOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse\
Value NameDeployment Command Timeout Seconds
Value TypeREG_DWORD
Default Value
Min Value10800
Max Value86400

opsmgrservertweaking.admx