Hi all,
Noticed some strange behaviour when creating some MSD policies recently, perhaps others can confirm the issue.
The time taken to load/save a Managed Software Delivery, or to add software elements to an MSD, appears to increase depending on the number of Service Pack and Update Tasks attached to the target software. So pronouced is this that the Console will throw timeout errors (HttpException) when accessing MSDs for particularly patch-heavy applications - such as, in our case, a policy which upgrades Office 2007 to Office 2010. I am not able to identify any related error messages in the NS Log. Our hardware is of a considerable standard and the ITMS install itself is only about 8 weeks old.
For comparison, I've measured the time taken to load an MSD in the Console. There was no other user activity when these tests were run.
- Symantec Endpoint Protection, 0 associated patches, loads instantaneously.
- Adobe Reader 10, 11 associated patches, loads in ~10 seconds
- Microsoft Office 2010 Standard, ~200 associated patches, loads in just under 120s
The policy I'm having trouble with is an Office 2007 --> Office 2010 upgrade policy, which lists approximately 450 associated patches combined, and exceeds the web application timeout. I was very lucky that the Console responded when I built the policy, but now, it's almost impossible to access it, rename it, enable it, or otherwise act on it.
Ultimately I'd like to see this problem fixed, but for now, is there a way to increase the timeout threshold for Console actions?
Thanks all.