Solved

SCCM 2012 Install Reboots

Posted on 2014-11-03
2
320 Views
Last Modified: 2014-11-14
We are currently deploying our updates and install to our Windows 7/8 workstations via MS SCCM 2012. It has been a recent trend where users are unexpectedly being prompted to restart their machine in the middle of the day (way after the scheduled deployment) without any suppress button.

We are looking for a method to ensure with 100% certainty that users machine's do not attempt to install\reboot 2-3 hrs after the initial deployment.

Any suggestions?
0
Comment
Question by:GR JN
2 Comments
 
LVL 24

Expert Comment

by:VB ITS
ID: 40420416
We are currently deploying our updates and install to our Windows 7/8 workstations via MS SCCM 2012. It has been a recent trend where users are unexpectedly being prompted to restart their machine in the middle of the day (way after the scheduled deployment) without any suppress button.
Firstly, are you deploying Windows Updates via SCCM or software updates?
0
 
LVL 17

Accepted Solution

by:
Brad Bouchard earned 500 total points
ID: 40420433
You simply set the options in the Software Updates section to not reboot; it really is that simple.  That being said, I've also ran into this and I had to dig through logs to determine what was either preventing it from happening, or overriding some setting I had.  

What I recommend is easy and will help ensure you don't have users who are being forced to reboot during production hours:

1)  Install the SCCM toolkit that comes with the SCCM console install.
2)  One of the tools installed with the above mentioned toolkit is CMTrace, and it is one of the best all around log readers/tools I've used.  
3)  Next, get the CCM logs from one of the computers in question that has rebooted unexpectedly, or out-of-band as we call it.  Usually located on the root of the C drive at C:\Windows\CCM\Logs.
5)  Locate the UpdateDeployment log and open it in CMTrace.  Look for any red or yellow values stating errors or warnings; if you don't find anything from here, look for informational items stating when the reboot happened.  If this log doesn't show the reboot, look through your other log files until you find the one that does.  I can't remember which log file shows the reboot from updates right off the top of my head, but it's either this one (mentioned at the beginning of this step) or one of the WU logs.

This is also a good reference to help.

That should get you at least on the right path.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
How to set up remote file access using Microsoft products 16 51
Windows 2012 R2 Evaluation 4 27
WMI - Issue Server 2012 R2 1 18
Do I need Remote FX when installing MS VDI 3 23
Resolve DNS query failed errors for Exchange
Note: This is the second blog post in a series on email clearinghouses (https://www.xmatters.com/alert-management/blog-email-has-failed-us?utm_campaign=70138000000ydLoAAI&utm_source=exex&utm_medium=article&utm_content=blog-post).   Every month t…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question