Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Client install rebooted all my servers

Con risposta Client install rebooted all my servers

  • Tuesday, September 16, 2008 5:04 PM
     
     
    Sign In to Vote
    0

     

    This is a bit information for those of you who are going to use software update clients.  We ran into and issue with our servers (about 50 of them) that got the system center client and rebooted.  What we originally had setup to manage our patches was a patchserver and GPO for workstations and servers seperated.  Because we have implemented SCCM we moved the role to the same server, so that we could get rid of the other patch server since its redundant. 

     

    We started using SCCM for use with our workstations and changed the GPO to point to our SCCM server.  But we had not changed the GPO for the servers yet.  What I just found out is that the software update point client installation is a bit seperate from the client installation it terms of how it functions.  Its basically mandatory and forces the installation of the client and components that go with it.  As soon as we change the server GPO to point to our SCCM box it got the update it needed to have the software update point client installation.  So unlike being able to controll the client push there is no controll of the SUP client install.  This in turn installed the client on all of our servers and then forced some of the other neccessay components such as BITS to be installed.  The client does not need a reboot but the components like BITS does.  This forced a reboot on all of our production servers the the GPO got refreshed so for about 2 hours we had servers go down. 

     

    I thought I would share this tidbit with everyone in hopes that you dont end up with a similar situation.  Also any input and thoughts would be appreciated. 

     

All Replies

  • Tuesday, September 16, 2008 7:44 PM
     
     Answered
    Sign In to Vote
    0
    It's not the client that forces a reboot but the BITS update.

    You have to distribute this in a controlled manner first, and then you can distribute the client through GPO or the more techsexy WSUS way Smile
     
  • Friday, October 17, 2008 10:14 PM
     
     
    Sign In to Vote
    0

    Lerun is correct.  The BITS update during SCCM client install can require a reboot.  Just to clarify - there  are no extra Software Update pieces that get installed later on a client.  Everything is installed on all SCCM clients. 

     

    -Eric