[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] My apologies. - THE OFFICIAL BLOG OF THE SBS DIVA
Thu, Mar 31 2005 18:53 bradley

My apologies.

I'm an SBSer.  And I feel that I represent the SBS community to Microsoft.

I feel like I've let the community down today.

I didn't represent you well enough to the Windows Update team.  I didn't understand the impact of the 'normal' Windows 2003 service pack 1 was on our SBS boxes.  I didn't follow the beta closely enough to fully understand that it would have impact.  I didn't understand that a Service pack that has impact on our SBS boxes would be offered up to us top of the window in Windows Update today.

I let you down.  For that I apologize.

Going forward I'm going to make it my personal goal to ensure that the patching goals at Microsoft include a goal that if a service pack of any kind adversely affects us that it will be blocked in Windows Update and will not be offered up to you if you go to Windows Update[Update... the Service pack is no longer on Windows update -- Thank you Microsoft for being VERY agile and responsive]

Someone asked today how to set up a test network if all they had was a production one and you can [if you are a Microsoft partner...see why you want to be a Microsoft partner] get a subscription to the “Action pack” which is a bundle of software that would be perfect for a 'test' network.  But if you don't have the time for that ask in the communities about how the patch is working on systems.  We'll tell you.

This one should not be installed on SBS.


UPDATE - 4/2/2005 - Windows update no longer offers up SP1 to SBS boxes.   Thank you Microsoft for responding to our concerns. 


From Sean Daniel, Windows Small Business Server

There has been quite a few questions regarding Windows Server 2003
SP1 and it's support on Windows Small Business Server 2003: I hope
this post will clear up any of the confusion here.  If you have
immediate questions, please feel free to follow up in the public
Microsoft Newsgroup at: microsoft.public.windows.server.sbs I will
attempt to answer your questions as best I can.

Windows Server 2003 SP1 is supported on Windows Small Business
Server 2003, but there are some known integration issues that are
resolved in the Small Business Server SP1 (available within the next
60 days).  With the Windows Server SP1 installed, you may encounter
the known issues and our recommendation is to:
a)      Be patient with the issue and wait for Windows Small
Business Server 2003 SP1
b)      Un-install Windows Server 2003 SP1, and wait for Windows
Small Business Server 2003 SP1, which includes Windows Server SP1

Furthermore, a KB Article will be written to further address these
issues, I will post it to the public newsgroup when it is available.

In the mean time here is the short list of the known issues:
-      Remote Access Wizard hangs when creating the connection
manager package
-      Small Business Server Change IP tool will fail
o      Change IP tool will continue to fail after un-install of WS SP1
o      Workaround: Remove WS SP1, disable DHCP, re-run CEICW
-      Power Users retain SharePoint Administration privileges even
after the role is changed to Reader
-      Re-Install of Exchange fails
-      Re-Install of Intranet component fails
-      Fax Services won't start and the Fax Configuration Wizard
cannot be run after un-installing Windows Server SP1
-      DHCP service may not start after a restore

Please let me know if you have any further questions

 

Filed under: