SBSized Windows 2003 sp2 release notes

Blog SBSPraxis.de » Tipps zur Installation des Windows Server 2003 SP2 auf einem Windows 2003 Small Business Server

Sun, 05 Aug 2007 18:56:37 GMT

Pingback from Blog SBSPraxis.de » Tipps zur Installation des Windows Server 2003 SP2 auf einem Windows 2003 Small Business Server

the back room tech Windows 2003 SP2 problems on Windows 2003 SBS servers «

the back room tech Windows 2003 SP2 problems on Windows 2003 SBS servers « — Sat, 26 May 2007 15:31:40 GMT

Pingback from the back room tech Windows 2003 SP2 problems on Windows 2003 SBS servers «

Has asus.tw been hacked again? Also, ANI Patch released.

Spyware Sucks — Wed, 04 Apr 2007 00:14:34 GMT

Source: Comment to Susan's blog by Lars Nelson: http://msmvps.com/blogs/bradley/archive/2007/03/18/sbsized-windows-2003-sp2-release-notes.aspx

Has asus.tw been hacked again? Also, ANI Patch released.

Spyware Sucks — Tue, 03 Apr 2007 22:19:09 GMT

Source: Comment to Susan's blog by Lars Nelson: http://msmvps.com/blogs/bradley/archive/2007/03/18/sbsized-windows-2003-sp2-release-notes.aspx

re: SBSized Windows 2003 sp2 release notes

Lars Nelson — Tue, 03 Apr 2007 20:50:53 GMT

First Susan, thanks for your time posting these notes to make our life easier.

2nd I'm with James. I've just about had it.

Right now, my mood is terrible, because before I could get down my first bit of coffee this morning, my Symantec AV was telling me that the ASUS website just tried to pass along the currently unpatched .ANI exploit. Yes, it appears as though ASUS has been hacked and is passing along the .ANI exploit that as I understand Microsoft has know about for a few years. See http://www.dynamoo.com/blog/ for details on the ASUS thing.

And now, SP2 on SBS is shaping up to be a major ordeal -- just like SP1 was.

I don't know about anyone else, but whenever I have to apply a patch, or especially a service pack on SBS I sweat bullets until the thing is in -- because of so many issues, tweaks, workarounds etc.

IS ANYONE ELSE SICK OF WORKAROUNDS? I AM.

As the worlds wealthiest company, and as this is software, why can't we be given a tested pack that works 99% of the time out of the box -- on SBS? Or, if there are engineered issues with the SP on SBS, a short/consise document that explains what they are and not the technobabble that typically accompanies a SPack release.

It's as if a whole industry has sprung up in direct relation to MS incompetance/indifference/laziness or all three of the above.

All too often, we seem to look at these MS shortcomings as cute, folksey etc. This may have been fine back in the days of Standalone DOS where VisiCalc, Dbase and WordStar were really toys and not mission critical apps.

These days if the SBS Server is down, whole businesses stop functioning.

To my customers, SBS is as important as Ma Bell and the Electric Company to it's survival. We would never tolerate such performance from our utilities and we should stop taking this garbage from MS.

It is not fun be looking a an error dialog box, or, service failed to start screen at 3:30PM on a Friday while you have had a client network already down for 2 hours of patching with the Small Business Owner looking over your shoulder and asking how everything is going.

For you, or me to have to place SP2 in a VM and test it and get to know its nuances and to have a full backup and all tested and lastly have the box blessed by the pope before we install a patch or SPack it just isn't right.

If the server works before the patch, the patch should not break the server.

OK. I'm done now and feel nuch better.

Win 2003 sp2 on Microsoft update now

E-Bitz - SBS MVP the Official Blog of the SBS "Diva" — Wed, 21 Mar 2007 17:09:41 GMT

EDIT - FOR THOSE SEEING ISSUES PLEASE VISIT THE SBS BLOG AT HTTP://BLOGS.TECHNET.COM/SBS AND THIS POST

re: SBSized Windows 2003 sp2 release notes

Pat D — Mon, 19 Mar 2007 21:35:08 GMT

So remind me what happened with SBS 2003 when server 2003 SP1 came out. Did they not initially say it was fine for SBS? And then a few days later they pulled it and said NOT to install on SBS yet? Then they came out with the additional SBS SP1 patch to be run after the server 2003 sp1 patch.

What was all that about, and should we be waiting to see if it happens again?

re: SBSized Windows 2003 sp2 release notes

Sylvia Dulaney — Mon, 19 Mar 2007 14:50:46 GMT

Since an attempt at installing SP2 on SBS2003(Basic), when I use System Management and click Monitoring and Reporting, I get "No performance data is available at this time. Performance data is collected hourly." Is this related to your comment 4. Help and Support is missing? (Sorry if this got posted twice).

re: SBSized Windows 2003 sp2 release notes

bradley — Mon, 19 Mar 2007 13:08:49 GMT

James, there is no need for a SBSized patch because this is just a recap of unusual items. This isn't the list of "oh this will get you " this is a list of what may.

I did it to help, just in case folks got stuck, not to point out that it would happen.

Most of the issues here are related to out of date ISA or those broadcom nics.

Yes, the Server team needs to learn how to post a blog post before something hits the download page, but there is nothing in this service pack we weren't seeing networking wise in SP1.

re: SBSized Windows 2003 sp2 release notes

James B — Mon, 19 Mar 2007 12:15:37 GMT

How about instead of having a list of un-official fixes for a MS patch we instead demand MS release a fixed patch for SBS and to get their heads out of their ….. and stop posting crap to WSUS that is not ready for prime time. There is no way MS can state this SP was tested on a fully deployed SBSr2Pre server not to mention the lack of a KB then to change the KB basically once a day for a week.

MS tells customers to stay patched, customer has ponied up the bucks for SBSr2, followed all the install prompts so has WSUS running, patched their WORKING server and now it’s broke, who is suppose to pay for that down time? Not every SBS customer out there has a full time IT person or even a support shop they call so how are they suppose to know they can’t or shouldn’t install certain patches unless they have the time and expertise to fix what the patch breaks? Even those with support such as some of my customers are sick and tired of “patching” so they can be “broken” so I have to bill them to “fix the patch”.

As much as I think UAC is useless because it will train users to just click “allow” all the time, see MAC Ads, users are getting tired of having working machines become broken from Windows updates and we might just find them refusing to patch. I’ve ran across a number of machines in the past few months that were not just not up to date but rather years out of date. Customer’s answer, everything works so why update. Well MS if you’re going to break things with patches that is exactly what end users will start saying across the board. From patches to a totally broken DST process there needs to be a hard look at what’s coming out of MS “Fixes” Division.

re: SBSized Windows 2003 sp2 release notes

Dag Staale Jensssen — Mon, 19 Mar 2007 07:13:58 GMT

Time will tell.

Release Notes for Microsoft Windows Server 2003 Service Pack 2

Dag Staale Jenssen — Mon, 19 Mar 2007 07:11:30 GMT

MS har lagt ut Release Notes for Microsoft Windows Server 2003 Service Pack 2. ...