It would be of some help listing what version / patch level you're on for one .
Sorry, you are right. Both the core and the agent are versions 2017.3 SU2 (10.1.30.401).
Unnecessary reboots were always a big problem for our users. I thought it was a problem for others users as well. I will contact Ivanti tech support if this behaviour is a bug or not.
1 of 1 people found this helpful
The described problem appears only under Windows 10, 1709. It will be repaired by Ivanti with the next SU.
Did Ivanti give you an idea when the next SU will be released? I am planning to upgrade from 2017.1 to 2017.3 soon.
This is what I got from support engineer: "there is a defect submitted for this under 233030. The defect should be resolved in next SU."
Unfortunately no date.
Find out whether they mean "SU3" (for 2017.3) or "SU4" as "the next SU".
So SU3 should be out for limited release (i.e. - "available via support - intended for affected customers only") in the next few weeks (depending on how smoothly things go with final testing).
If "next SU" is intended to be SU3, then you don't have a long wait. If "next SU" is expected to be SU4, then chances are you might have to wait longer.
So - yeh ... depends on which "next" SU they're talking about (as SU3 is "locked in" and in its final testing phase). If it is SU3, support should be contacting you once it's gone live for limited release.
Assuming things go well with the limited release, we will make it available for global availability via patch content for everyone (as is our current standard process).
Hope that helps?
A public roadmap for release and fix would be very useful, at least for partners
Suggest it to PM? Essentially via - Enhancement Requests - type of thing?
There's a lot of "it depends on how smoothly things go" and "must have" things that skewer "nicely laid plans" often enough (i.e. - say "Meltdown affected our code" (it doesn't - just highlighting the sort of thing we may need to respond to), then obviously we'd have to jump on that thing right away). So at best we tend to have pencilled in ETA's.
But the threat landscape of recent years has been making things a LOT more awkward for everyone (heck, Microsoft released a Meltdown patch, then had to pull it the next day because it would brick AMD machines... joy).