question

RonaldSeow avatar image
0 Votes"
RonaldSeow asked ·

System Center Configuration Manager 2012 Suppress Reboot Deployment

Hi!

I have a question with regards to SCCM 2012 updates/patch deployment which I hope you can share your expertise with me. As I have just taken over, I do not have full picture of the entire setup as yet. Hence, appreciate any help.

The scenario is such;

  1. In our environment, we have quite a number of servers and they are placed in a few device collections. Some servers exist in more than 1 collection.

  2. I created a new collection and place 2 servers in it.

  3. I created a software update group with the patches and updates I wish to push to those 2 servers.

  4. I created a deployment and specified suppress reboot in user experience.

  5. I defined the maintenance window for that collection.

  6. I download computer policy for that collection.

The result wasn't as I expect. It was suppose to download the packages and install and not reboot the server. But however, it rebooted.

Can any one advise what can cause the suppress reboot specified in the user experience to not work.

Appreciate any form of help.

Thank you.
Ronald



mem-cm-generalmem-cm-site-deployment
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

3 Answers

FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered ·

@RonaldSeow

Thank you for posting in Microsoft Q&A forum.

---->Have we seen the RebootCoordinator.log before? The details about our client restart after software update installations may record in it.

---->Since we have checkd the suppress reboot during our deployment,maybe we could check the UpdatesDeployment.log on our client to see the details of our suppress reboot behaviour.
Like the image shown below,normally it may display after rebbort value.
34117-image.png

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



image.png (37.8 KiB)
· Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered ·

@RonaldSeow

Thank you for posting in Microsoft Q&A forum.

---->Have we seen the RebootCoordinator.log before? The details about our client restart after software update installations may record in it.

---->Since we have checkd the suppress reboot during our deployment,maybe we could check the UpdatesDeployment.log on our client to see the details of our suppress reboot behaviour.
Like the image shown below,normally it may display after rebbort value.
34109-image.png

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



image.png (37.8 KiB)
· Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jason-MSFT avatar image
0 Votes"
Jason-MSFT answered ·

Are you really using ConfigMgr 2012? Do you know it's only 18 months away from end of life?

To @FionaYan-MSFT's point above, how do you know that COnfigMgr rebooted the system? Do you have automatic updates disabled?

· Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.