We deploy most of our packages using different shedules which trigger on heartbeat.
The reason for choosing 1 package / shedule is that we have a lof of government legacy software running which doesn't always work with the latest version of java / firefox / chrome / ... so we have to carefull.
I know we could use nested packages, but I find more clear to have a shedule / packge. So we can disable a specific shedule in case of known problems or the opposite, force a specific package to fix issues.
We prefer working with a heartbeat trigger, so machines get updated when an employee enters the office and switches on his computer. A fixed sheduled would blow up parts of our network. Some remote locations use point to point beam connections.
The problem we face now is that some machines haven't updated in a while. I would guess the problem lies in the fact that some machines are never truly switched off, but go in this deep sleep (fast startup as Microsoft calls it).
The PDQ website cleary states: "When PDQ Inventory detects that a machine has gone from an offline state to an online state, it can trigger something that we call a Heartbeat Trigger."
Our users switch off their desktops every evening, but some machines report in PDQ Inventory that they are already up for 100s of days. I guess some computers use the fast startup method.
So if a machine never switches truly off, but uses that fast startup, the state from offline to online is never triggered and thus packages will not be deployed.
Am I understanding this correctly?
Please sign in to leave a comment.