I had meant to copy this over to my blog last week! We have had a few sites with this issue, so the more people with this information the better. Taken straight from The Official SBS Blog.
Issue Description and Symptoms:
Last Tuesday (9/13/2011), KB2494001 “MS11-074: Description of the security update for Microsoft SharePoint Foundation 2010: September 13, 2011” was released to Microsoft Update.
By default, the update will be automatically approved for installation on SBS 2011 Standard. However it will still require administrative action to be installed.
As with all SharePoint Foundation 2010 updates, you must complete the update process by running psconfig after the update is installed. If your server is not yet running SP1 for Windows SharePoint Foundation and you do not run psconfig after installing this update you may encounter the issues described in http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx. The most common issue is that SBS backups start failing.
The symptoms and behavior are described here in more detail:
To resolve this issue you must run psconfig as described in this blog:
- Open an Administrative command prompt.
- Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
- Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
SBS 2011 Standard UR1 Improvement:
Since Windows SharePoint Foundation 2011, included in SBS 2011 Standard, is the first version that requires psconfig to be launched manually we expect that this is an issue that will linger for the foreseeable future.
To address this issue we have introduced a new feature in SBS 2011 UR1. SBS 2011 Standard Rollup Update 1 was released yesterday (9/15/2011) and when installed, it adds warnings in the console and the desktop that will help identify this situation and provide documentation on how to recover.
After installing the rollup, a new scheduled task will be created; this task is set to run every day at 1:15am.
This task scans the event logs to see if the SharePoint Health Monitor that is scheduled to run at 12:00am has detected a situation that requires the databases to be upgraded using psconfig.
When the issue is detected, a Domain Wide group policy that is created by the UR is enabled to show the message on logon to any Domain Admin login on to any domain workstation. When is no longer detected, the User configuration settings are disabled.
When the issue is active, this is what a domain administrator will see when logging on:
Note: this message will only be cleared after the issue is resolved and the schedule task runs again that night. If needed, you can re-run the scheduled task in Task Manager, under Microsoft\Windows\Windows Small Business Server 2011 Standard.
The task writes a log called WSSPsconfigurationNotification.log in C:\Program Files\Windows Small Business Server\logs.
We also have the more traditional console alert, if configured, an email will be sent when this alert is detected.
The alerts point to Kb2580174 Receiving SharePoint Health Analyzer alerts in SBS 2011 Standard
Today we were setting up a customer with SBS Essentials. They had a few XP machines that needed to join the SBS Essentials network.
Oddly, they failed after they joined the domain, but tried to install the client connector software.
On looking in the logs in:
C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs
I found this line:
ClientSetup: Could not ensure NetTcpPortSharing service is Running:
I then checked the services and sure enough the .NET framework 4 service had completely hung. Killing the service did nothing and restarting also failed.
Eventually, I ended up having to use a completely horrible and unsupported fix…. which was as follows:
Kill the service:
Then go into:
C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation
Copy SMSSvcHost.exe and SMSSvcHost.exe.config from that location.
Then go to:
Backup the two files above mentioned in THIS folder (or rename). Then copy the files from above to here. The service that is hanging will then start correctly.
Then, your Connect computer wizard will run perfectly!