[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] Does that Exchange patch affect SBS 2003 RTM? - THE OFFICIAL BLOG OF THE SBS "DIVA"
Wednesday, May 10, 2006 12:05 PM bradley

Does that Exchange patch affect SBS 2003 RTM?

http://support.microsoft.com/gp/lifesupsps

http://www.microsoft.com/technet/security/Bulletin/MS06-019.mspx

NA in the blog posts...

Well, for those of us who just aren't with the program - or for customer's who will never be with the problem... and they're running SBS2003 no SP, Exchange no SP - but fully patched otherwise, how do we tell if we're at risk? According to MS06-019 the update only applies to Ex2000-postSP3rollup, Ex2003Sp1, and Ex2003SP2. What if you're at Ex2003-noSP on a SBS2003-NoSP box? What to do then?

I don't buy the whole "get with the program, that was a year ago" argument. Because no matter what I do, I'm going to have a subset of customers who will never "get with the program".

NA.. it's your JOB to get your clients "with the program"... you see that Exchange 2003 RTM that came with that customers SBS 2003 that you don't have Exchange sp1 on?  It's no longer offiically supported... DUDE this Exchange patch is needed on that box.  You need to sit them down and 'get with the program' because that box is now in a unsupported state because you are not keeping it up to date with patches.

06-019 is a vulnerability FROM REMOTE with a crafted calendar invite hitting your SBS box to take control of it.. Microsoft update that box.. get Exchange SP1 on it.. jump to SP2 so you'll get the immediate benefit of 18 gigs versus 16 gigs up to a max of a 75 gig store.. but please... people.. PATCH.

This requires a REBOOT on my boxes that I've tested....

Filed under: ,

# re: Does that Exchange patch affect SBS 2003 RTM?

Wednesday, May 10, 2006 3:13 PM by Jonathon

It will ask you to reboot, but if you don't, all the services, including IIS, will be in a stopped state. So beware.

# re: Does that Exchange patch affect SBS 2003 RTM?

Wednesday, May 10, 2006 5:17 PM by Jeremy

Y'know...rather than haranguing NA and others you could have simply said "Yes" and followed up with the comment only way to get a patch to address it is to update to at least SP1 prior to updating. There's little need to be so dramatic about it, as we can all read the severity levels on the notice.

Thanks for the link to the support expiry page though...it's always good to know the official stance from MS regarding support of their products.