Should I Continue to Patch Client Pc's with SCCM or Switch to WSUS?
Posted on 2010-11-11
*I apologize in advance if this is hard to follow and for this being a very long question. I will try to ask this is the most clearly as I can, but please don't hesitate to ask me to clarify on things if you'dre not sure what I'm asking*
I have a server configured to just run SCCM '07 SP2, and this server also has WSUS installed as was required for the installation of SCCM '07. I'm finding that using SCCM to update client Pc's is VERY cumbersom and inconvenient for me as I have to: manually download updates, add them to update lists, sync the updates with the distribution servers (this NEEDS to be done at night as it sucks up ALL available bandwidth), and then schedule the install to the clients. My questions are the following:
1) Is it just better to use WSUS and point the client Pc to the WSUS server via GPO. There are >300 systems on the network.
2) If i keep using SCCM to deploy updates, does anything need to be configured in GPO to point the client Pc's to the SCCM server? I dont have anything setup now, and when I deploy udates via SCCM, it DOES work.
3) I'm still using Windows Updates (poining to Microsoft's Update Server) because I can't update the Client Pc's as often as updates get released. Is this bad? Should I point them to the WSUS server? Even while using SCCM to update the clients?
4) If I decide to use WSUS for client updates; what about bandwidth usage in regards to remote clients at remote locations hitting the WSUS server? Should I setup a WSUS server on each subnet. I just dont want 200 Pc's trying to download updates over one connection and flodding that connection.
I'm driving my self nuts and I feel like I'm making things much harder for myself then they need to be. I have more questions, but they're based on what answers I get for the above questions. I will also create a new thread if I have to for those ones.
Thank you for your help