By the way, the computer does wake up shortly after the task hits the 1 minute mark after being started.
Heyas Curtis - I'd suggest making sense of things by understanding what's going on / where / at what point. Also, it'd help stating what version you actually *ARE* on -- saying you moved from 9.5 is somewhat handy as a reference, but we've no idea what you've moved *TO* .
To this end...
... enable max logging on the Core & at least one Client that reliably behaves like this (see -- How to enable Xtrace Diagnostic Logging -- note that the registry paths are DIFFERENT for Core & client!).
... and then follow the trail of logs, and see what happens / "delays" where to begin with:
Sounds like you're using WOL with a 1 minute delay for a start, so that'd explain the first minute.
As long as you're doing a simple policy supported push, chances are you may have issues with agent discovery (which can be down to DNS, networking, firewalls. etc, etc.) if the Core has to time out a few times in discovering clients for instance.
See where the logs take you ... if you're not super familiar with the logs / what to look for, you can try to involve support / your partner in helping you make sense of things. There's a whole bunch of those, and the first step is finding out "where things take a lot of time" -- that'll then be a starting point on where to look for things.
A simple / short task definitely doesn't take 7 minutes to start running normally ... and there's a whole butt-load of settings you *CAN* do. For instance, if you use Multicast, remember that the clients are WAITING for a configurable amount of time (5 mins default, I think) for other clients to join the multicast session first (it's no longer managed by the Core - multicast is "self-organised" now). So if you remove multicast (as a test), does stuff "work much faster" all of a sudden?
A 5-minute window for self-organising multicast is fine - I suspect you just need to familiarise yourself with the tech advancements from 9.5 (of which there are *A LOT* - 9.5 to 9.6 was a massive paradigm shift in software dist concepts, so you may need to re-learn those).
Does that help / make sense? Soft Dist has changed a *LOT* from 9.5 days (to the better) ... I suspect it's a case of "working as configured" and it's just a learning curve with the changes at the moment?
The following may be helpful to get an idea as to all that's changed... (this stuff started with LDMS 2016-ish, and is a good "whirlwind tour" type affair of all the new things in the relevant releases. Even at a rapid pace, those are roughly 40 mins of overview!)
Sorry about not giving the version we now have - I assumed that if someone just upgraded that it would have been to the latest version. We upgraded from LANDesk v9.5 to Ivanti Management Console 2017 v10.1.10.287.
I reviewed what you gave me and then started looking at how the "Services" settings were set on our old console as compared to the new one - they appeared to be all the same. But, I noted that the "Wake up" was set for "300 seconds" on both consoles and then I remembered that since the newer version no longer uses the old "Delivery Methods" settings - we had the "Wake up" within each of those set for "120 seconds". So...after setting the "Services" "Wake up setting to "120 seconds", that reduced the entire (wake up) distribution or scripting job time down to just 4 minutes, which is much better than the previous 7 minutes.
Thanks for your assistance and the information.
1 of 1 people found this helpful
Happy to help .
And - it'd be *NICE* if upgrades worked that way, but unfortunately in my line of work we're forced to ask. I've had dealings with a customer that "upgraded" to 9.6 earlier this year, even though both 2016 and 2017 were available. So ... we never assume .
The community is there for you should you run into other issues / questions & such.