Ever since we updated to 7.0 at the end of last year, machines are taking a ridiculous amount of time to run detect jobs in our environment.  I have bumped the detect timeout up to the max of 5 hours and machines still time out or come back with errors after a job has run.  It is becoming impossible to run detect/deploy jobs as the machines never get to the deploy stage.  Support tells me we're trying to do too many machines or too many patches but its the same number we've always done and even when running a manual job on just a handful of machines (or even just one) we get the same results.  The 7.1 update seems to have improved things somewhat but we're still running into more of the same issues.  Any idea how to troubleshoot this? I've had an ongoing support ticket for a while and I'm not 100% sure how to proceed.
4 Comments   [ + ] Show Comments

Comments

  • Try deleting and re-creating your patch smart labels. I noticed the SQL changed since I originally created my patch smart labels in 2012.
  • I had the same issue - I revert to client 6
    Even the newest 7 client only helped on the first detect and then failed.

    Infact I've found the client 7 to be really slow in doing everything, especially forced inventories and patch detection.
  • Are there any issues running the 6.4 client with a 7.1 server? We are planning to upgrade from 6.4 to 7.1.
    • I we've upgraded to 7.1 and have a few machines still running 6.4 agents. I haven't seen any major issues yet.
  • none that i can see - just makes sure you tick the

    Enable Pre-7.0 Agent Support

    Box under Settings->Agent Settings
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity