How to increase script execution timeout for compliance settings scripts
Hello,
I have few scripts that I configured in compliance settings CI, both VB and PowerShell that do some checks on clients to revert info back to me if they are compliant according to my organization rules or not. Unfortunately they take more than 60 seconds to execute and result out and they show failed in reports due to default 60 second limit. How to increase this time to say 120 second or 180 or so
I tried a method shown here, but the change reflects in sitecontrol file and I can check that thru SELECT SiteControl FROM vSMS_SC_SiteControlXML  also, but client doesn't honor and still show old defalt values of 60 seconds. How do I fix this ?
http://blogs.msdn.com/b/fei_xias_blog/archive/2013/10/21/system-center-2012-configmgr-using-vbs-to-extend-the-dcm-script-execution-timeout-value.aspx
 
Th
September 5th, 2015 10:26am

Hi,

Please make sure you client gets the new policy.

"To verify the new value applied on client, you can run wbemtest, and connect to the namespace "root\ccm\policy\machine\actualconfig" then run query: "Select ScriptExecutionTimeout from CCM_ConfigurationManagementClientConfig" to see if value has been changed."

Free Windows Admin Tool Kit Click here and download it now
September 7th, 2015 4:45am

Many days and client do receive policies well, I tried to see the value remain same as 60 sec, thru wbemtest. on SQL DB IN Sitecontrol XML it show new value I tried.
September 9th, 2015 12:40pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics