The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of Chris Puckett from Product Quality]
Windows Small Business Server (SBS) 2008 Update Rollup 4 is now available on Microsoft Update and WSUS. This rollup package addresses the following issues in Windows Small Business Server 2008.
NOTE: This update also includes all updates from Update Rollup 1, Update Rollup 2, Update Rollup 3 and supersedes those previous update rollups.
How to obtain this update
This rollup fails to install on my SBS 2008 server.
Why is there so many issues? hmm..but at least it was released.
Please call Microsoft support so we can investigate why the rollup will not install on your server. Since the issue is that an update does not apply the case will be no charge.
When trying to install SBS 2008 Update Rollup 4 Release (KB979454) on my server the update is actually failing with Error Code 6BA which is one of the Issues this update is trying to address! Any ideas on how to successfully install this Update Rollup in cases like this?
From previous posts regarding 6BA for the other update rollups, check the C:\Windows\temp\EnableKerberosLog_2009_<date_time>.log file for more clues.
What about if you have installed SP2 for server 2008. Will it still work
Yes, SBS 2008 Update Rollup 4 will still apply to SBS 2008 servers with Windows 2008 Service Pack 2 installed.
Has anyone had any issues with accessing sharepoint through rww after applying this roll up?
If I want to install the recent Exchange 2007 sp3 and the rollup, do I need any further patches and will they work well together?
Yes, you will be able to install Exchange 2007 SP3 when it releases and any rollups with the SBS 2008 Update Rollup 4 on the same server.
Off topic question:
When can we expect to get more info about the future release of SBS? Potentially SBS 2008 R2 with Exchange Server 2010, I have quite a few customers holding back their SBS migration/deployment since they don’t want to be tied in to an older exchange version for the next 3/5 years. This info would help partners and customers make better decisions whether to migrate/deploy now or wait for a R2.
Please don’t answer “software assurance” since this doesn’t help any “SMB” because there is no in place upgrade and they will need a new server which defeats the purpose of 3 to five year server investment.
If the fail is because of enablekerberos,
the log is at: %temp%_\EnableKerberosLog_2009_<date_time>.log.
You also can find the details in eventlog under Application, with Windows SBS Update Rollup as its source.
I Get 6ba error code as well - Here's the log
2010/05/15 00:24:38| Reading registry keys to get URL for SBS SharePoint
2010/05/15 00:24:38| Trying to enable Kerberos, as well as set other authentication configurations
2010/05/15 00:24:38| Backup original settings of site https://sites:987
2010/05/15 00:24:38| Webapplication found
2010/05/15 00:24:38| Webapplication is running in app pool with identity NetworkService
2010/05/15 00:24:38| Checking authenticaiton mode for Default zone
2010/05/15 00:24:38| Authentication provider is Kerberos
2010/05/15 00:24:38| Originally not allow anonymous
2010/05/15 00:24:38| Originally client integration enabled
2010/05/15 00:24:38| Originally not use basic authentication
2010/05/15 00:24:38| Original settings backup-ed. The machine is ready for authentication settings configuration
2010/05/15 00:24:38| Calling stsadm.exe to enable Kerberos with parameter "-o authentication -url https://sites:987 -type windows -enableclientintegration -usewindowsintegrated"
2010/05/15 00:24:42| Microsoft.WindowsServerSolutions.IWorker.EnableKerberos.InstallException: Fail to enable Kerberos with exit code -1
at Microsoft.WindowsServerSolutions.IWorker.EnableKerberos.Program.Main(String args)