Restart client computers after updates deployment in SCCM 2012 R2

Hi everyone,
I've deployed some Windows updates to all of my Windows 7 workstations. I've set a deadline time to 48 hours after deployment avalaibility time - i.e., to 13:00. I've set the option "Supress reboot on workstations". In my default client settings,
I've set computer restart settings so: "Display a temporary notification..." - 360 minutes, "Display a dialog box that the user cannot close..." - 60 minutes.
The question is:
Can the end user delay restart on his workstation after deadline time - in this example, will be a temporary notification received, and the user will be able to click "remind me after 360 minutes" or so - or will be computer restarted in any case?
How can I prevent the restart, if end user cannot delay restart after the deadline time?

Hi
No they cannot stop or delay the deadline time. You can only set the time delay from the server.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • How to find who modified Software Update deployment in sccm 2012

    Hi,
    How to find who modified(Date & Time) software update deployment in SCCM 2012 ?

    In the Console :
    Monitoring / System Status / Status Message Query
    Right Click : "Deployments Created, Modified, or Deleted" - Show Message and select your period.
    You'll have your information there.
    Benoit Lecours | Blog: System Center Dudes

  • Lync 2013 x64 silent client deployment via SCCM 2012 SP1

    Greetings everyone!
    I ran into a problem with Lync 2013 x64 silent deployment.
    I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
    I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
    Added them as applications to sccm software library.
    Deployment of Lync 2013 x86 application was a success with over than 80% compliance. 
    But all Lync 2013 x64 automatic installations finish with different errors.
    I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
    My membership query-rules for this collection:
    Office 2013 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
    Office 2010 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
    My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
    So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
    The same configuration works with Lync 2013 x86 deployment, except other setup folders.
    When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
    I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
    Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
    sites with deployment point.
    Thanks in advance.

    Hi,
    Here are some tips and tricks for your reference.
    Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
    http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • I can't Log Out/ Restart/ Shut Down after updating to Mavericks

    I can't Log Out/ Restart/ Shut Down after updating to Mavericks.
    When I choose the above options nothing happens.
    MBPr can only go to sleep.
    When i force quit loginwindow from Activity Monitor nothing happens.

    I can sudo reboot /shutdown
    I tried several solutions on other threads nothing worked.

  • Is MDT must have for OS deployment in SCCM 2012

    I know that existing MDT could be integrated to a new SCCM.
    Is MDT must have for OS deployment in SCCM 2012 or SCCM has its own engine for OS deployment?
    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thanks for the answers.
    one more question...
    I am going to start SCCM deployment in test environment.
    For OS deployment part:
    if MDT is planned for integration with SCCM should I configure OS deployment in SCCM before adding MDT.
    Or in this scenario OS deployment in SCCM could not be touched.
    After all previous answers I understand that OS deployment module is part of SCCM installation and is independent from MDT.
    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

  • Some Systems Restarted Automatically after Updates Deployment with Restart Suppressed

    I've searched the forum and multiple blogs - but, I'm still confused about what is causing some of our workstations to restart after applying a software updates deployment.
    I deployed the Dec 2013 Patch Tuesday updates to a collection of workstations. The deployment was set to:
    Not allow restarts outside of a maintenance window (box is unchecked)
    Suppress restarts on workstations (box is checked).
    There is no maintenance window defined for any of our workstations
    On all the workstations, the HKEY_LOCAL_MACHINE\Software\...\WindowsUpdate\  values are:
    WUServer: http address of our SCCM SUP server
    WUStatusServer: http address of our SCCM SUP server
    Also, the key in HKEY_LOCAL_MACHINE\...\WindowsUPDATE\AU is:
    UseWUServer: 1  (which I understand disables the use of the automatic Windows update service)
    Some set of workstations automatically restarted shortly after 3:00 am the next morning. Clearly that's the Windows Update Agent jumping in a restarting the systems. However, I don't understand why it would do that. I really don't understand why it would
    have occurred on only some of the workstations while others are still waiting for users to manually restart 36 hours later.
    All of the workstations are in the same active directory OU - so the same set of GPOs applies to all.
    Note: none of the registry keys were set directly in any GPOs - I assume the values were set by the SCCM client.
    Any assistance would be appreciated.
    Larry

    depending on the OS version, this could be relevant:
    http://blogs.technet.com/b/wsus/archive/2013/06/11/wsus-blog-managing-updates-with-deadlines-in-an-era-of-automatic-maintenance.aspx
    http://blogs.technet.com/b/wsus/archive/2013/10/08/enabling-a-more-predictable-windows-update-experience-for-windows-8-and-windows-server-2012-kb-2885694.aspx
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Lync 2013 client deployment via SCCM 2012 forcing restart

    All, 
    I am attempting to deploy the Lync 2013 x86 client via SCCM 2012 to 158 machines running the Office 2010 suite. My package runs, and the installs complete but they are forcing a restart after the install even though I have gone in to everything that I can
    think of to tell the install not to force a restart. I am a newb in the ways of SCCM so I have been self teaching, and I may have missed something. 
    I have gone into the config.xml and changed the value SETUP_REBOOT to NEVER. 
    In the program properties I have RUN set as HIDDEN, and AFTER RUNNING set to NO ACTION REQUIRED. 
    Is there something that I am missing to stop the users machine from restarting after the install completes?

    Great, unfortunately it will be because files (usually shared DLLs) are in use as Office is opened, despite it being an older version. 
    Agree it's not optimal, I usually just tell clients that they will need to reboot, or that it will push out overnight (when I schedule it) and their computer will restart, so make sure they save everything.
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
    Georg Thomas | Lync MVP
    Blog www.lynced.com.au | Twitter
    @georgathomas
    Lync Edge Port Check (Beta)

  • Client version after update to R2 CU1

    Hi guys,
    I just updated SCCM from R2 to R2 CU1. I have distributed the four packets of CU1 to the distribution point and I checked with regedit and the console that the version is CU1 and .1203. But when I see properties for automatic upgrade of client, it shows
    .1000 version. When I see the properties of install client through software updates I see the same version (.1000).
    Must I do more to automatically update the clients?
    Thx!!!!!

    (Your English is fine.)
    2938441 is not included in the WSUS catalog so you can't directly deploy it using Software Updates.
    You have two recommended options:
    - Software Distribution. When you installed CU1 on the site server it prompted you to create client update packages. Use these to deploy the update. You don't specifically need to create new collections though, but that does work.
    - SCUP
    Both options are discussed at
    http://technet.microsoft.com/en-us/library/jj553405.aspx
    Jason | http://blog.configmgrftw.com

  • Blue screen on client computers after locking screen

    When I Lock or Curtain certain computers, instead of the picture of the lock and the message, some just show a blue screen - often with a mouse present that can still be controlled by the user. These computers then cannot be controlled by me or the user (any more than moving the mouse around a blank screen) and have to be manually shut down and powered on via the power button, forcing a loss of the current work on the computer. It is the same computers in which this continues to happen. I have tried reinstalling ARD client, repairing disk permissions and running anti-virus software.
    I am running ARD 3.3.2 and my client computers all have been updated to that as well. The computers are all mirrors of one another, and are updated and maintained at the same time. They are eMac PowerMac 4,4 running 10.4.11 with 700 mHz G4 and 1 GB ram. Thanks for any insight!

    Q: Why doesn't oracle rollback the transaction, if an application crashes? It isn't a good solution to kill the session manually.
    A: If ORACLE can get the information, that the client process is dead, than ORACLE can rollback the transaction
    Q: Can a simple update bring oracle in such a state?
    A: No
    Q: Can an oracle error crash the application or even windows XP?
    A: It's possible that the application crashs, but not Windows XP. An OS should prevent a client application to stop the OS.
    Regards
    Marc

  • Pre deploy applications sccm 2012

    Hey Everyone,
       I have a question regarding deployment of software. Current layout is as follows : 2200 machines ranging from always on desktops to about 400 only laptop users. We use SCCM 2012 to deploy applications etc. I am currently updating java and Imprivata
    Single Sign On. Regardless the process is to remove the old versions of JAVA , install a newer one , once that is complete lay down a newer version of Single Sign-On which requires a reboot. Since one depends on a another we decided that this is the best opportunity
    to update both. Anyway I push the software out to to machine collections as all machines need this regardless of users.
      I cant get the laptops that go home for the day , since I can't deploy during the day the machines are not getting this update. There is a setting within SCCM that allows a deployment to be " predeployed" to the users machine. Is there anyway
    I can utilize that to apply to the machines so that even when a laptop is offline the content is already pre-deployed to the machine so all that needs to happen is  ; a deadline to be set
    and the clients to be configured to automatically install required software after business hours ? I can push a script that would copy the installation files to the machines and kick of a script or a scheduled task to install the updates ,
    or many other ways. But I really wanted to use SCCM and since I noticed that check box for pre deplyment of content to the users machine seems like what I want. But since it targets users primary device and I am deploying to a device collection targeting machines
    not users  it doesn't seem to be working. Any ideas ? Is this possible ? 

    I have looked at Powershell deployment toolkit as it offers users the ability to snooze installs etc. But I don't have the time to adjust my deployment to this format as my deadline is coming up. But going back to your comment about packages having the ability
    to pre download content , wow that is awesome - huge limitation on application types in my opinion. Let me walk you through my mind set to see if I got the logic down please.
    1) I set the Scheduling on a deployment to a set deadline of 11/5/2014.
    2) On the User Experience tab I set the following 2 check boxes : When the installation deadline is reached , allow the following activities to be performed :
         a) Install Software
         b) System restart if required to complete the installation -  ( Do I need to set this if my deployment type : User Experience tab has the setting set of " Configuration manager client will force a mandatory device restart "
    3) With regards to Maintenance Window and Work Hours do I need to worry about anything here ? I know that if the deadline is set to a time where the maintenance window doesn't match it will be applied at the next maintenance window. But do I need to set
    anything else here to have this automatically get apply ?
    4 And last on the client side within the software center - options tab - computer maintenance " automatically install or uninstall required software and restart the computer only outside of the specified business hours " do I need to set this check
    box ? And do I need to specify logon hours to match up with the maintenance windows to have the software try and deploy prior to deadline but still offline ? 
    What I am trying to achieve is to get the software pre downloaded to the machines and then automatically get deployed during off hours but hopefully prior to the deadline. Meaning is there anyway using any of the mentioned steps above to have the system
    try and install the packages everyday between certain hours and once the deadline is reached to just install ? 

  • Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

    Hi,
    I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily. 
    I just installed Office 2013 on this system and have activated it as necessary.  The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM.  I have other systems with
    Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
    If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
    I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
    What can I check to try and determine what the problem is?
    Thanks in advance,
    Nick

    Yes, the 8.1 system is a member of collection where the update deployment is targeted.
    Are there any specific logs I should check in the client?  If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
    in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • SCEP going out to the internet after being migrated to SCCM 2012 and saturating facility MPLS.

    I was unaware of the fact that SCEP was gonig out to the internet to pull down 120 megs worth of data each time a client is migrated. I'm trying to determine the easiest or best way to avoid this. I've done some research and it looks like bundeling the SCEP
    policy with the migration package might work. I also saw some tool that you can use to add a SCEP update rollup to the package. Ultimately if i could just get the exact URL the clients are going out to our networking team could apply QoS to this URL. Unfortunately
    though it appears in the MPCMDRUN.log to go to go.microsoft.com/fwlink, but on the networking side in pathview i seen the client ends up going to Akamai.
    I'm assuming MS offloads their web traffic to Akamai and that first link is redirected, if that is even the right link. Does anyone know a way i can prevent this while still getting the client up to date. This entire time I thought the clients would pull
    what they needed from the SCCM 2012 env. I'm using ADR to push the definitions and that seems to be working fine except for 2 situations. One a client is migrated, or 2 the client comes online after being offline for more than 7 days and goes out.
    Either way if someone could provide me with the URL for throttling or a better method for deploying I would be very grateful. So far we've migrated about 8 thousand clients and have about another 10 thousand to go. The majority of the clients have local
    pull DPs, and if further details of my infrastructure would be helpful please just let me know.
    Thanks,
    -KR

    Jorgen,
    I appreciate you pointing out the setting and that has helped partially and I was able to track down the URL that is being used by the clients for QoS by networking. Now management has pushed back with why are the clients going to the internet at all. I
    can understand why. If were deploying all the patches why can't the clients pull their SCEP engine from the SUP/WSUS server. I see it finding it in the MPCMDRUN.Log file but it still goes out to Microsoft to pull the 120 meg file. Do i not have any other options
    for pushing the engine to the clients, if ADR is working for current clients what am i missing. I'm sure its something obvious, but my migration is on hold up until I can keep the clients from going to the internet for their new engine and deltas. 
    Any help you could provide i would very much appreciate. Thanks again Jorgen.
    -Sam Kachar

  • WinPE Error Capture and Deploy Win7 - SCCM 2012 R2 w/ CU1

    Hi Forum
    Deploy and Capture: Windows 7 x64
    SCCM Primary single site server: Server 2012 R2
    Version: SCCM 2012 R2 w/ CU1
    Environment is Hyper-V on Windows 8.1, deploying to a Gen1 VM with a legacy adapter.
    I am running into an issue whilst building a lab environment. I have built a Capture and Deploy TS (using the standard TS, ie not MDT although this is integrated) and deployed to an imported machine using the MAC address via PXE. Custom Client package has
    been created and put against the TS.
    The machine picks up the PXE response and boots into the SCCM WinPE environment and I choose the TS. The only currently available TS is the Build and Capture.
    It runs through the TS restarting at various points as expected and then after the Client Manager package is installed it restarts and runs the TS... at this point it starts saying. "Initiating Hardware Devices.." (or something to that effect).
    It does this for about 15 seconds before I get this error:
    Windows PE initialization failed with error code 0x8022001B
    Seen here:
    I am unable to get the cmd prompt up at this point and it will restart and carry on a normal build, no TS running, meaning no capture.
    If any can advise, please do.
    Thanks in advance
    NN

    Hyper-V should work fine without any drivers injected, and you did your VM correctly.
    During this error, what you see in a back ground, ConfMgr wallpaper or Windows 7 black first-run screen "preparing/first run"? I´m just thinking, is there any chance, that you have additional restart step set to boot to WinPE, instead of booting
    to default OS?
    Otherwise, you will need to be able to Access CMD with F8 for more troubleshooting. Make sure you have F8 command Support enabled on boot image and re-distrubute it. Or create new boot image as Peter suggested.  

  • Best practice for client migration from SMS 2003 to SCCM 2012 R2?

    Can anyone advise what the most recommended method is for migrating SMS 2003 clients (Windows 7) to SCCM 2012 R2?
    Options are:
    1. SMS package to deploy ccmclean.exe to uninstall SMS 2003 client. Deploy SCCM 2012 R2 client via SCCM console push.
    2. Simply push SCCM client from console installing over existing SMS 2003 client.
    I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
    3. Use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean and then install the SCCM client.
    Appreciate any feedback. Thank you.

    Hi,
    >>I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
    I haven't seen any official document records the option 2 method. There is only upgrading from SCCM 2007 to SCCM 2012 directly.
    I think you could use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean.exe. Then use SCCM 2012 to discover these computers and push clients to them.
    Best Regards,
    Joyce

  • How to remove the parent-child software update point in sccm 2012 sp1

    I have a CAS , Primary site server(1) and secondary site servers (7). I have software update point installed on CAS, Primary server and Secondary site servers as well.
    I have a situation to reinstall the software update point which is in primary site server.
    So, How to reinstall the software update point in primary site server since this is located in the middle between CAS and secondary site servers.
    So, please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
    I have referred few posts on how to remove SUP
    https://social.technet.microsoft.com/Forums/en-US/c7258aad-d968-427b-8826-4829916c14c9/remove-and-re-add-software-update-point-sccm-2012?forum=configmanagersdk
    and how to install SUP
    http://www.windows-noob.com/forums/index.php?/topic/4467-using-sccm-2012-in-a-lab-part-6-deploying-software-updates/

    Hi,
    >> please suggest me, do I have to do anything special apart from the normal steps to uninstall and reinstall the SUP point on primary site server?
    I just tried to reinstall the SUP on the Primary site(only one SUP on Primary site and there is a SUP on Secondary site). The SUP upstream data source of the Secondary site showed empty and greyed out. But the upstream data source resumed after a while.
    It seems nothing special needs to be done.
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Maybe you are looking for