In order to get the new baseline changes machines need to run a machine policy retrieval and eval. Generally this is set to run once an hour, I believe.
Login into a machine that you know is targeted, run a policy update, then check the Configurations tab to manually run and see if it has the new baseline. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Miriyala, Vasu Sent: Wednesday, September 02, 2015 12:10 PM To: [email protected] Subject: [mssms] RE: script execution timeout Thanks Ratlif, I did separate them single chunks/CI to make it easy for clients to throw results in lesser time. Well I meant still no luck, problem is Site control file shows its modified, but clients aren't picking this change. I checked in relevant WMI classes of client to see its still 60 sec which is default/ How do I find where is it stuck from server to client Cheers, Vasu From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, September 01, 2015 5:00 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: script execution timeout How are your CIs setup? One single script to check all these things? If so, break them up into different CIs and have each evaluate separately. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miriyala, Vasu Sent: Tuesday, September 01, 2015 7:26 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: script execution timeout It is for compliance settings only, I used both Powershell and VB, which does check some services status of our LOB application lets us know. Similarly few other needs to check if program exits of sorts Thanks, Vasu From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, September 01, 2015 12:05 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: script execution timeout What kind of scripts are you running that you expect them to run more than 60 seconds. To be clear, this timeout is for scripts run via compliance settings only (which includes application detection methods). It is not for anything run for a deployment type or program though. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miriyala, Vasu Sent: Thursday, August 27, 2015 3:05 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] script execution timeout Hi Champs, Did any of you tried to increase the script time out execution for CM2012 clients thru site control file, so to help easing default setting of 60 sec which isn't suffice for most of program we deploy (application or script to check some settings in compliance etc) I tried a vb script available from reliable source, which has made changes in site control file, but client don't reflect the changes, where and what to check ? Thanks, Vasu This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
