Patching behavior of newly added Windows machines?
We're deep in our trial of Desktop Central.
I'm seeing what I consider odd behavior on newly added windows machines. I add the DC client to a machine, and the first thing that happens is that for any applicable APD task, the machine goes into the "patching complete" state in APD no matter how many patches it has lined up. It then stays in that state until at least the next vulnerability DB update, and sometime after that runs patches. This can take up to almost a day unless I force the patches.
Is this expected behavior? I really don't like seeing machine that needs patches come up as "patching complete" anywhere.
I'm seeing what I consider odd behavior on newly added windows machines. I add the DC client to a machine, and the first thing that happens is that for any applicable APD task, the machine goes into the "patching complete" state in APD no matter how many patches it has lined up. It then stays in that state until at least the next vulnerability DB update, and sometime after that runs patches. This can take up to almost a day unless I force the patches.
Is this expected behavior? I really don't like seeing machine that needs patches come up as "patching complete" anywhere.
Topic Participants
Jordan D
Roobhan Karthikeyan
New to M365 Manager Plus?
New to M365 Manager Plus?
New to RecoveryManager Plus?
New to RecoveryManager Plus?
New to Exchange Reporter Plus?
New to Exchange Reporter Plus?
New to SharePoint Manager Plus?
New to SharePoint Manager Plus?
New to ADManager Plus?