asked on
Should I Continue to Patch Client Pc's with SCCM or Switch to WSUS?
*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
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
Microsoft Server OSMicrosoft Server AppsMicrosoft Applications
Last Comment
DonaldWilliams
ASKER
Your correct about your #3, I was shocked to see how many updates were reported being missing.
I just have a couple more questions:
1) Should I set up GPO to point the clients to my SCCM server, or should I just disable Windows Updates via GPO and continue to manually setup "update lists" and push the updates out via SCCM.
2) Is there anything I need to configure in the WSUS console, or can I just ignore that and do everything out of SCCM?
3) What is the difference in updateing via SCCM and WSUS? Is WSUS the automatic way for the clients to update and SCCM is the manual way?
As far as the bandwidth issue is concerned, I have another thread on that already open. :)
I just feel like having WSUS on my SCCM server is redundant. I opened up the WSUS console and saw 2K updates that needed to be approved, yet when I setup "update lists" via SCCM, and push them out, the clients update. If I can get the clients to auto check for updates on my SCCM server w/o crashing my network, that would be wonderful.
I just have a couple more questions:
1) Should I set up GPO to point the clients to my SCCM server, or should I just disable Windows Updates via GPO and continue to manually setup "update lists" and push the updates out via SCCM.
2) Is there anything I need to configure in the WSUS console, or can I just ignore that and do everything out of SCCM?
3) What is the difference in updateing via SCCM and WSUS? Is WSUS the automatic way for the clients to update and SCCM is the manual way?
As far as the bandwidth issue is concerned, I have another thread on that already open. :)
I just feel like having WSUS on my SCCM server is redundant. I opened up the WSUS console and saw 2K updates that needed to be approved, yet when I setup "update lists" via SCCM, and push them out, the clients update. If I can get the clients to auto check for updates on my SCCM server w/o crashing my network, that would be wonderful.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you for taking the time to give me all this valuable information. Let me review what you have given me and I will get back to you. If iI find that it answeres my questions, I will "accept as solution" and award the points; if not, I will be asking more questions. :)
ASKER
Can someone point me to a link (is there one) that describes EXACTLY how to setup WSUS with SCCM?
The way I have it now "works", but I don' think it is "right"....
The way I have it now "works", but I don' think it is "right"....
ASKER
This solution pointed me into another direction that I will follow up on.
2)Yes, there are a lot of things you'll need to configure and tweak for your environment, there will be lots for WSUS to. You'll need to get the setup guide and go through it and it might take a couple of days.
3)Is it bad? you have no control of what updates get pushed or when or any way of knowing if computers are up to date so if any of that you consider bad...Im sure you will be shocked to find out how many updates are missing once you get all the clients reporting through the GPO... virus makers depend on machines not being patched :)
4) with both SCCM and WSUS you need to CONFIGURE bandwidth management. What groups get what patches when and at what time, randomization of patching etc. When you use central management like SCCM and WSUS you should only be downloading the patches 1 time, to the WSUS storage area. then the patch is distributed locally over your LAN. This should have minimal bandwith impact. You should be able to do it during the day without anyone noticing!