WSUS or SCCM SUP
We currently deploy all our microsoft security updates simply with a single WSUS server. However we have a number of different sites with a mixture of slow and fast links.
I have been asked to put together the pros and cons of each. Does anyone have a list of these, I am already using sccm for a number of other things but need the evidence to show that it would be better using sccm than leaving it up to WSUS?
I have been asked to put together the pros and cons of each. Does anyone have a list of these, I am already using sccm for a number of other things but need the evidence to show that it would be better using sccm than leaving it up to WSUS?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Are there any big things that SCCM can do that WSUS (on its own) can not, and vise versa
- With SCCM you can define exaclty the time when installing updates.
- Also it's very easy to build logical computer groups for which you can define specific update deployment settings.
- You can handle the download behaviour if the remote location has a bad bandwith with SCCM
- Also it's very easy to build logical computer groups for which you can define specific update deployment settings.
- You can handle the download behaviour if the remote location has a bad bandwith with SCCM
additionally, if you use Configuration Manager SUP:
1- Provides visual workflows for software updates processes.
2- Better reporting and checking for update setup status on the client machine.
3- Inventory Tool for Microsoft Updates.
4- You can use deployment templates.
For more information about Configuration Manager SUP, you may check the following link:
http://technet.microsoft.com/en-us/library/bb633264.aspx
1- Provides visual workflows for software updates processes.
2- Better reporting and checking for update setup status on the client machine.
3- Inventory Tool for Microsoft Updates.
4- You can use deployment templates.
For more information about Configuration Manager SUP, you may check the following link:
http://technet.microsoft.com/en-us/library/bb633264.aspx
if you are interested in other solution then
http://www.manageengine.com/products/desktop-central/patch_management_supported_application.html
thanks
Mathi
http://www.manageengine.com/products/desktop-central/patch_management_supported_application.html
thanks
Mathi
What I would do since you have some slower links is throttle BITS
WSUS: How To Throttle BITS
http://blogs.technet.com/b/sus/archive/2008/06/30/wsus-how-to-throttle-bits.aspx
WSUS: How To Throttle BITS
http://blogs.technet.com/b/sus/archive/2008/06/30/wsus-how-to-throttle-bits.aspx
On your slow links you can create secondary sites or Distribution Points to deploy the updates, and schedule those to only deploy to the site overnight.
Also, SCCM gives you the option to wake-on-lan and deploy, which can be a big help to your success ratio.
And if you use SCCM for imaging you can force install the updates as part of the imaging process.
My general rule is if you have a 'simple', highly connected environment and don't need WOL, then stick with WSUS. In a highly distributed environment, I'd go with SCCM.
Also, SCCM gives you the option to wake-on-lan and deploy, which can be a big help to your success ratio.
And if you use SCCM for imaging you can force install the updates as part of the imaging process.
My general rule is if you have a 'simple', highly connected environment and don't need WOL, then stick with WSUS. In a highly distributed environment, I'd go with SCCM.
WSUS 3.0 vs SCCM SUP
http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/46d4f200-d650-4a91-b7d3-eb1a68a21a58/