SMS/ITMU vs. SCCM/WSUS/ITMU?

[Bjorn]

I've used SMS/ITMU mainly for reporting so far (i.e. Still using WSUS for
patch distribution). Currently I'm intending to setup an initial SMS/ITMU
collection and patch package infrastructure to cover all Microsoft patches
"to date". From that point on I'm assuming that it's best to build additional
individual OS-based packages each patch Tuesday... I'm assuming that ITMU
patch distribution collections should be based on OS. I lack resources to
establish a sufficient amount of remote SMS DPs to fully deploy ITMU across
my entire network, and look forward to SCCM's Branch DPs...

Q 1. What are some general recommendations on criteria for packaging
Microsoft updates for distribution through ITMU, and criteria for collections
used to distribute those patch packages?
Q 2. Can someone share test results of SCCM/WSUS/ITMU using Branch DPs?
Q 3. Can someone share a comparison between SMS/ITMU and SCCM/WSUS/ITMU?
Q 4. Any ideas on when SCCM and WSUS3 goes LIVE?

[unknown]

I use sms/itmu to do patches to 4000 desktops with dps in 200 branches. I manage them myself with very few issues. I have built a free way around sms's one dp at a time deployment tactic that can get 100meg of patches out to my slow branches in a few hours.

Dps, create a share on the server, add sms computer account to local admin group or to domain admins and give everyone full access to smspkg share you created. CReate dp share not server in console.. Protect them to your branch subnets. I did this in a couple days. Even with branch dps in sccm, you still gotta do the leg work. No more than 2003.

Just got back from mms 2007. sccm is a different beast alright but it looks good and if it works I will be liking what I saw. Console is a lot better.

Software updates is alot different, but being I create about 50 adverts a month patching I will like the new way better with wsus.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com