Windows Small Business Server (SBS) 2008 Update Rollup 2 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, and supersedes that update rollup.
[Today's post comes to us courtesy of Damian Leibaschoff, Justin Crosby and Chris Puckett]
You may notice an issue where the Windows Update (WUAUSERV) service will be spiking one of the logical CPUs on servers running Exchange 2007 with automatic anti-spam updates turned on. This will include any SBS 2008 installation where Forefront for Exchange was installed as part of the setup. Please note that the service displayed will by SVCHOST, since WUASERV runs inside SVCHOST.EXE.
This issue has now been resolved on the Windows Update backend, and should clear itself automatically after your WSUS server’s next sync. If you are still experiencing the issue you can start a manual WSUS sync by:
If you cannot start ISA on SBS after installing MS09-012 and receive "Event ID 14109: (The ISA Server Standard Edition cannot run. Either the server is using more than 4 processors....)." please see the following post on the ISABlog: http://blogs.technet.com/isablog/archive/2009/04/18/ms09-012-and-isa-server-standard-edition-14109-failures.aspx
[Today's post comes to us courtesy of Chris Puckett]
When you select the server and click Restart in the IIS Manager console, the Terminal Services Gateway service will be stopped and not restarted, even though the World Wide Web Publishing service is restarted. If you are logged into the server via RWW or a TS Gateway session, your connection will be dropped and you will not be able to get back in via RWW or TS Gateway. In addition, the following event will be logged in the Microsoft-Windows-TerminalServices-Gateway/Operational log.
Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Event ID: 400 Task Category: (3) Level: Warning Keywords: (16777216) User: NETWORK SERVICE Computer: SBS2008.CONTOSO.LOCAL Description: The TS Gateway service is shutting down. To diagnose possible causes for this problem, verify whether the following services are installed and started: (1) World Wide Web Publishing Service (2) Internet Authentication Service (IAS) (3) RPC/HTTP Load Balancing Service. Also, check Event Viewer for Network Policy Server (NPS) and IIS events that might indicate problems with NPS or IIS.
Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Event ID: 400 Task Category: (3) Level: Warning Keywords: (16777216) User: NETWORK SERVICE Computer: SBS2008.CONTOSO.LOCAL Description:
The TS Gateway service is shutting down. To diagnose possible causes for this problem, verify whether the following services are installed and started: (1) World Wide Web Publishing Service (2) Internet Authentication Service (IAS) (3) RPC/HTTP Load Balancing Service. Also, check Event Viewer for Network Policy Server (NPS) and IIS events that might indicate problems with NPS or IIS.
Keep this in my mind when working in IIS Manager on the SBS server remotely. Use iisreset /noforce instead or restart the World Wide Web Publishing service in the Services console.
[Today's post comes to us courtesy of Ketan Thakkar, Manish Kapoor, Chris Puckett, and Justin Crosby]
You may experience authentication issues browsing http://companyweb on SBS 2003 and SBS 2008 servers after installing the cumulative security update for Internet Explorer (963027 or 969897) or Internet Explorer 8.0 or Windows Server 2008 Service Pack 2.
When you try to browse Companyweb you will be prompted for authentication 3 times and eventually receive a blank page or 401.1. Your IIS logs will show your request failing with 401.1 Unauthorized.
Please use one of the following resolutions depending on the version of SBS you are running.
On an SBS 2003 server this issue can be fixed by applying update KB961143.
Note: You must have .NET Framework 2.0 installed before you apply this update.
On an SBS 2008 server this issue can be fixed by applying SBS 2008 Update Rollup 2 (960911). This update is now available on Microsoft Update and WSUS (must be approved by administrator).
Updated 6/26/2009 to include 969897 MS09-019: Cumulative security update for Internet Explorer.
Updated 5/1/2009 to include Windows 2008 SP 2.
Updated 4/28/2009 due to release of Update Rollup 2.
The workaround provided in the following blog post for IE 8.0 also applied to IE 7.0 with 963027 installed. http://blogs.technet.com/sbs/archive/2009/02/24/known-issues-after-installing-ie-8-on-small-business-server-2008-and-the-vista-clients-that-are-joined-to-the-sbs-domain.aspx.
Note: This issue will be fixed in upcoming update rollup for SBS 2008. We will update this post when it is available.
On SBS 2008 you can also implement method #2 from KB963027.
[Today's post comes to us courtesy of Ed Walters]
Some of the steps in this post have been taken from the following SBS 2003 blog post written by Wayne McIntyre: (http://blogs.technet.com/sbs/archive/2007/08/07/how-to-backup-and-restore-your-sbs-and-default-group-policies.aspx). They have been modified for use with SBS 2008.
SBS 2008 uses 2 default policies along with 9 “SBS specific” policies that provide the centralized management and configuration for the SBS 2008 environment. In cases where a policy was accidentally deleted or where policies were removed, there will be a need to restore these policies once the issue has been resolved. The following steps walk you through the process of creating a backup for the existing group policies, restoring them and re-linking policies in SBS 2008.
When you select a Group Policy that was restored, you will see that the “Links” window and “Security Filtering” window are blank.
Link the Windows SBS Client policies:
Link the Folder Redirection Policy:
Windows SBS Client – Windows Vista Policy, Windows SBS Client – Windows XP Policy, Windows SBS Client Policy have WMI filters associated with them. These filters will be associated with the group policy during the restore.
Note: These steps cover GPO backup and restore to the same server only. There is a similar but different procedure if you want to restore backups from one SBS Server to another. This scenario will be covered in an upcoming blog post.