ITMU never used it or done but need to now!

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:

ITMU never used it or done but need to now!

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 >> ITMU never used it or done but need to now!

Page: [1]

Message

<< Older Topic Newer Topic >>

ITMU never used it or done but need to now! - 6/23/2008 9:58:46 AM

Deviant

Posts: 2
Score: 0
Joined: 6/23/2008
Status: offline

Greetings everyone,

I have been tasked with using getting our installed ITMU up and in use! I have not used this before and need help!

But what would be really helpfull is to have a basic user guide of how to do this. A checklist of what you need to do on each patch tuesday!

My basic understanding is that I download a cab file. And do something with that. I use SMS as well to then push the update tool and scanner to the clients and it will return what patches they dont have. I then select what patches I want to allow to be put out to the test group. Monitor and then deploy.

So with that breath released. I do not actually no how these steps are done and what is involved in each one.

From scouring the www for guides or deeper info I only seem to uncover ITMU install guides.

Can any helpfull reader give me an insight or a guide?

Many many thanks in advance.

Post #: 1

RE: ITMU never used it or done but need to now! - 6/23/2008 10:41:04 AM

bmason505

Posts: 1981
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline

The MS docs are pretty good, e.g., http://www.microsoft.com/downloads/details.aspx?familyid=3d81b520-a203-4376-a72d-fd34a6c4a44c&displaylang=en

But I almost wonder if this late in the game, you might want to go with WSUS instead since you need it for SCCM anyway. If you don't have a huge shop, I think I'd go with it myself.

_____________________________

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

(in reply to Deviant)

Post #: 2

RE: ITMU never used it or done but need to now! - 6/23/2008 4:15:33 PM

mdermer

Posts: 15
Score: 0
Joined: 11/17/2006
Status: offline

I aggree with Brian. In addition, it will take you some time to work out the bugs with the ITMU, considering you haven't used it yet. It works fine, but requires a little time and understanding - stick with WSUS!

Mike

(in reply to bmason505)

Post #: 3

RE: ITMU never used it or done but need to now! - 6/25/2008 8:18:35 AM

Deviant

Posts: 2
Score: 0
Joined: 6/23/2008
Status: offline

Thanks guys,

I am not finding much help with the MS docs other than installation help which for me is the easy stuff. Its actually using it that I find complex. That doc you linked for me has been pointed to me by several resources now yet I still can not find a single referance to ITMU and security patching in it. I find its all about securing SMS and who and when should be able to admin what and where in SMS etc.

So far I have learned:

Download wsusscn2.cab
Run the batch file for updating the DP's
Run Distribute Software Updates Wizard <--- bit wobbly in here still
Import existing PatchAuthorize.xml file as referance point
Amend PatchAuthorize.xml (Authorised date) <-- another wobbly bit
Test prior to mandatory date and time

But that is by no means enough understanding yet.

Using wsus is not an option for me, I have replaced someone that left here who set this all up but did not document any of it and I was not given a hand over!

Again thanks for the input I apreatiate it!

(in reply to mdermer)

Post #: 4

RE: ITMU never used it or done but need to now! - 6/25/2008 12:14:21 PM

bmason505

Posts: 1981
Score: 104
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline

Looks like you're making it out harder than it should be.

In general:

A sync job is created. You can run that manually if you copy out the command line, or schedule it to run unattended.
That sync job enters the new patch data into SQL to be offered up via DSUW and it pushes the new cab to the DP's if it's been changed since the last sync.
You run the DSUW which creates a patch job and optionally an ad for it.

You can initially advertise it to a pilot collection. If happy, you can modify the ad time and collection for production.
Instead of editing the patchauthorize.xml directly, you can\should modify the command line of the patch job instead.
So for example, if you wanted to change grace period there or nag times or countdown times, doing it here will change the patchauthorize.xml for you.

Switches: http://www.myitforum.com/articles/8/view.asp?id=8052

_____________________________

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

(in reply to Deviant)

Post #: 5