Hello All,
I created 2 Custom Agent Tasks to be run from the console. I increased the necessary timeout to 600 seconds however it would appear to still be timing out. I noticed in the Ops Console when you choose a server and launch the task you can override the timeout value to something greater than 600 seconds. Does this value hold true or are we still limitted to 600 seconds?
A little background - The task itself will launch an executable on the target server, once launched the .exe will do a scan for missing security updates, patches, etc. If any are detected missing it will then attempt to install referencing a .cab file on the local machine. as you can imagine the time for this all to ocurr is always greater than the max SCOM timeout.
There are 2 problems, 1 - exceeding the alotted timeout , 2 - once the timeout is exceeded SCOM kills the .exe on the machine and stops the installing of patches.
is there either a way to increase the alotted timeout greater than 600 seconds or trick SCOM and have it NOT kill the .exe once the timeout occurs.
hope this somewhat makes sense.
thanks in advance,
Matt