SMS 2003 SP3 ITMU V3 DSUW question

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SMS 2003 SP3 ITMU V3 DSUW question

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> SMS 2003 SP3 ITMU V3 DSUW question

Page: [1]

Message

<< Older Topic Newer Topic >>

SMS 2003 SP3 ITMU V3 DSUW question - 10/8/2008 5:21:56 PM

criticalerror

Posts: 98
Score: 0
Joined: 6/19/2007
Status: offline

In the last several SMS environments i've worked in i've avoided ITMU completely and used SUS and WSUS just because its so much easier to manage. Well, in my current position im being asked to move off WSUS and switch server patching to SMS because our corporate office is moving in that direction. Also, there is the whole scheduling issue with WSUS.

When I work in the WSUS console the updates tell me the MSRC # they are bundled in. We only approve security and critical patches based off their MSRC # (MS08-040). Well, when I run the DSUW it only gives me the QNumber during the update approval section. This is going to be a real pain for me. Is there something I am missing or a better way to use this wizard? If not I will have to manually download each MS# that is approved and create all the packages and advertisements myself which defeats the whole purpose of automating patch deployment. Plus I need the service window thats only seems to be avliable in the wizard.

Any suggestions?

I only have to deal with this for a few more months until I get SCCM in place.

Post #: 1

RE: SMS 2003 SP3 ITMU V3 DSUW question - 10/9/2008 12:10:34 PM 1 votes

bmason505

Posts: 2010
Score: 112
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline

I suggest you stick with WSUS because SCCM uses it (assuming you'd like to upgrade someday). Barring that, the DSUW is ugly, yes. You can't see superseded updates. It'll try to bundle some for you, but ultimately, you'll have to go read the bulletin and find each KB listed inside.

Hey wait, you say you are going to SCCM. Forget this nonsense. It's a waste of time for you to try to start this now.

_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to criticalerror)

Post #: 2

RE: SMS 2003 SP3 ITMU V3 DSUW question - 10/9/2008 2:28:01 PM

criticalerror

Posts: 98
Score: 0
Joined: 6/19/2007
Status: offline

Thanks Brian. I'm starting to think the same thing but politics out way common sense most of the time. Management wants it working here because our corp hq is having problems with it so if we get it working and they cant its a bunch of ra ra for us. I'll just manually download the MSRCs and build everything myself (BLAH) for the next 2 months.

Speaking of the upgrade ... does anyone know where I can find a Business Case template for upgrading. It would be nice if MS sales had something rather me spending the time writing it. Lazy I know. I already have approval because I've proved in a lab that there will be a lower TCO with SCCM but I still need documentation.

(in reply to bmason505)

Post #: 3

RE: SMS 2003 SP3 ITMU V3 DSUW question - 10/9/2008 3:57:45 PM

bmason505

Posts: 2010
Score: 112
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline

Just know of the one doc: http://download.microsoft.com/download/9/9/9/9994213d-db9f-4b3b-93b1-3832f85aa555/System%20Center%20Configuration%20Manager%20Why%20Updgrade%20FINAL.pdf

Politics. Blech.

_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to criticalerror)

Post #: 4