SCCM 2012 R2 SP1: automatic upgrade clients: reboot needed?
Hi,
We will upgrade to SCCM 2012 R2 SP1. Client upgrades are set to automatically. Since we have a few hundred systems we really need to know this upgrade is done smoothly but cannot test it.
So do you have experience with it? Then also will it need & force a reboot? In that case we might need to set the upgrade to manual but I'd like to avoid that and have it upgraded in 1 go.
September 1st, 2015 7:41am
No reboot require for automatic upgrade of client.
Also the automatic client upgrade take into account mainteannce windows
-
Edited by
Frederick Dicaire
20 hours 3 minutes ago
-
Marked as answer by
janhoedt
16 hours 21 minutes ago
September 1st, 2015 7:43am
No reboot require for automatic upgrade of client.
Also the automatic client upgrade take into account mainteannce windows
-
Edited by
Frederick Dicaire
20 hours 1 minutes ago
-
Marked as answer by
janhoedt
16 hours 18 minutes ago
September 1st, 2015 7:45am
I've seen CU1 require a reboot however the automatic update/upgrade process will never ever actually force a reboot.
September 1st, 2015 9:08am
No reboot require for automatic upgrade of client.
Also the automatic client upgrade take into account mainteannce windows
-
Edited by
Frederick Dicaire
Tuesday, September 01, 2015 11:46 AM
-
Marked as answer by
janhoedt
Tuesday, September 01, 2015 3:28 PM
September 1st, 2015 11:43am
Thanks! Update is done but I don't see any clients upgraded beside the sccm-server itself. Automatic update of clients is selected. Any idea how much time we should give this process of upgrading the sccm client?
September 2nd, 2015 3:48am
but I don't see any clients upgraded
How did you check that?
September 2nd, 2015 4:00am
I have a collection which queries the systems. However, I see now that the default automatic upgrade is "within 7 days". Then also probably a hardware scan is needed to inventory the updated clients.
September 2nd, 2015 4:03am
It's heartbeat.
September 2nd, 2015 4:27am
Though I've read no reboot is necessary, most of my clients are in the collection "Reboot pending". Maybe due to the fact that CU1 is now applied automatically (apparently SCCM SP1 automatically deploys CU's too -previously it did not)?
September 7th, 2015 10:35am
"Reboot pending" is not a default collection. How is it set up? How did you determine that the client upgrade is responsible for the pending reboot?
September 7th, 2015 10:53am
It's a compliancy rule. Did crosscheck the collection and found every client having a pending reboot (checked 10 clients).
Well, I'm not sure it's the update of the client but nothing else explains a sudden "pending reboot" of all clients whereas last week there were only a few.
Therefore my assumption that the CU was repsonsible for it.
September 7th, 2015 11:16am