THE OFFICIAL BLOG OF THE SBS "DIVA"

I think I'll wait a couple of weeks on W2K3 SP2...

OOPS.

http://www.microsoft.com/technet/windowsserver/sp2.mspx

says it a RC.

WSUS says it's golden.

Definitely put AU on 'pause'

Susan,

I have been told that the update can't load even with auto updates turned on as the EULA has to be agreed.  

The KB article is now up - it says that if you are planning on doingone of these things, apply the update after you do it, or uninstall it, upgrade and then apply:

- You upgrade from an evaluation copy of Windows Small Business Server 2003 to the full retail version.

- You upgrade from Windows Server 2003 to the full retail version of Windows Small Business Server 2003.

- You migrate to Windows Server 2003 from Windows Small Business Server by using the Windows Small Business Server 2003 R2 Transition Pack.

ttfn

David

Susan,

The Windows Server Division blog has a post about the release of SP2 for Windows 2003 Server. They have linked to http://www.microsoft.com/technet/windowsserver/sp2/overview.mspx

The linked page has not been updated since November 16, 2006 and there is not  mention that Service Pack 2 is supported on Windows Small Business Server 2003.

Have you any KB articles that state that SP2 is supported on SBS2003? Is SP2 only supported on SBS2003 R2?

Why on Earth would anyone have automatic updates enabled on a server anyways? I can understand automatic downloading of the updates, but if you're ignorant enough to turn on the auto-install feature then it serves you right.

Show me the technical documentation on Microsoft's site that recommends you enable it on a server.

Even if such documentation exists, the server admin is - in my opinion - a moron for turning on automatic updates without first TESTING the updates themselves. While Microsoft does do extensive regression testing before releasing security updates and service packs, there is no way they can account for every possible scenario and server configuration.

Is this for real?  From the release notes...

If you installed Internet Explorer 7 after installing Windows Server 2003 SP1, you must uninstall Internet Explorer 7 before you install Windows Server 2003 SP2.

And how about this one...

If you are installing SP2 on a computer running SP1, to ensure that certain applications and components function properly, install SP2 by using Update.exe.

Gee, I guess she showed you Mike...

You are correct Mike. There is no way that MS can test all scenarios and server configs. Makes you wonder why Microsoft suggest that IT Admins should flip AU on.

The left hand sure doesn't seem to know where the right hand is these days in Redmond. I am worried about Microsoft and their future. I think there are some big bumps ahead for them - and us.

Mike, Martin,

IF you have a server admin, then updates should be tested.  IF you don't (and many small businesses don't or won't pay for support) then you are better dealing with an update issue (as MS will support you) than a security issue, which while you might get support, could cause far many more problems!!

ttfn

David

I love to spend my time patching servers, invariably out of hours, so the fact I have an un-announced service pack, that may or may not work on SBS, and that I have to uninstall IE7, with another reboot. My evenings have just got so much better!

As if we haven't enough problems with unstable patches....

<i>If you installed Internet Explorer 7 after installing Windows Server 2003 SP1, you must uninstall Internet Explorer 7 before you install Windows Server 2003 SP2.</i>

I worked my way through college with a part-time job at ComputerLand. This was not long after Windows 3.11 had come out and a major upgrade to Word for Windows was released. (On more floppy disks than I even remember.)

Prominent in the installation instructions was this gem, which I still recall nearly twenty years later:

"Microsoft recommends that you do not install Word for Windows while Windows is running."

Now, I know there was a perfectly good reason for this, but the fact that the perfectly good reason existed in the first place still, to this day, delights and terrifies me.

Installed via WSUS after full ASR backup. So far no problems. Still, one has to wonder at M$'s pushing of this SP with no notice.

This is just a quick note to say that the release notes are WRONG (and will be changed) in stating that

Note that it says "IT Professionals can use the Automatic Updates feature" and not "should". Again, even if I'm administering a SBS-based environment, I would not turn on AU. When the customer is ready for the updates to be applied, I tunnel into the network and apply them. It's not rocket science. Also, I don't see the gripe about no notice given with the release of SP2. The Release Candidate had been out there for a few months. Were you coming to the conclusion that the SP was vaporware and would never be released?

At the end of the day all servers regardless should be patched with the latest updates for security and feature reasons.

Why would you disable Automatic Updates on a server box, doesn't make sense - especially if running a web or mail server as they are targetted by hackers daily.

Unpatched servers and workstations are a liability and could be more hastle in the long run.

Kieran.

Can't afford nor have time to manage multiple servers on top of a few other jobs... I went to Windows Update and downloaded and installed SP2 and guess what ... I have spent the last 16 hours searching for a way to get my server back up and running... NO DHCP ... Can't ping server... yippy!