There are a number of things that can cause a client machine to do an "all products" update - usually when you don't expect it
Them most likely culprits are:
1) The user doing an "update now" from the tray icon
2) Global updating
3) A deployment task actually performing an action (i.e installing or uninstalling something.)
Thanks for the ideas.
No to all three though.
The only thing I can think of is that the EPO 3.6 server DID have a task for engine updates.
But one would think that now that it has the EPO 4.5 agent on it and is pointing at a completely different/new server (I built it from scratch, so there's no database migration that occurred) that it would use the new policies.
But perhaps the old task/policy is cached and not overwritten when switching things?
I'll probably have to grab one of the log files and see where it got the idea to update the engine from.
I'd definitely check the agent logs as a first step - that should tell us why the task ran.