WSUS 3.0 versus ConfigMgr (SCCM) 2007

This question seems to be coming up quite a bit: What are the differences for Patching between WSUS 3.0 and ConfigMgr?

Jeff Gilbert posted this to the SMS email discussion list a few minutes ago…

Function

WSUS 3.0

ConfigMgr

Microsoft Update Source

Yes

Yes

Hierarchical architecture

Yes

Yes

BITS download

Yes

Yes

Categories

Yes

Yes

Scheduled install

Yes

Yes

MMC 3.0

Yes

Yes

3rd party updates

No

Yes

Deployment templates

No

Yes

Update lists

No

Yes

Maintenance window

No

Yes

Wake On Lan

No

Yes

Reports

Few (7)

Many (34)

Troubleshooting reports

No

Yes

Desired Configuration Integration

No

Yes

NAP Integration

No

Yes

 

And there are some additional advantages: If you have ConfigMgr, virtually all of your distribution mechanism could be unified (OS. Apllications, Updates, Drivers etc. etc.) so, you have to maintain ONE consistent architecture.

 

Published Monday, October 15, 2007 12:06 PM by rodtrent

Comments

# re: WSUS 3.0 versus ConfigMgr (SCCM) 2007

Monday, July 07, 2008 5:07 PM by heathsaunders

Nice chart. Just thought you may want to add the fact that you can't autoremove updates in ConfigMgr, but you can in WSUS. Also you can't autoapprove definition files or other updates in ConfigMgr.

# re: WSUS 3.0 versus ConfigMgr (SCCM) 2007

Monday, July 07, 2008 5:14 PM by rodtrent

Good point!  Thanks!

Powered by Community Server (Commercial Edition), by Telligent Systems