As we enter 2014, there are still plenty of new SBS 2011 servers being installed in offices. SBS 2011 is the last version of Microsoft’s Small Business Server (SBS) product line. SBS 2011 comes with Exchange, SharePoint and WSUS pre-installed.
If your site also has Windows 8/8.1 computers, you may discover that running Windows Update on those computers may generate an error 800B0001.
Now, if you do your due diligence and search for this error, you will find suggestions that a credential on your Windows 8 computer is corrupt, and that you should run a pair of DISM commands to attempt to repair the situation:
But, in most cases, running these commands will NOT resolve the issue. So what’s causing the error?
Simply put, you are missing a couple of required updates on your SBS 2011 server, updates that resolve the issue of Windows 8/8.1 communicating to the WSUS server:
KB 2720211 – Update for WSUS 3.0 SP2
KB 2734608 – Update for WSUS 3.0 SP2
I manage several SBS 2008 and SBS 2011 servers. One of the key maintenance issue is the size of the WSUS database. There are plenty of posts from people bemoaning the fact that suddenly the WSUS Content folder has grown to over 20gb (or more)!
WSUS provides an easy way to run the wizard manually. But doing this requires one to log into the server, and start up the wizard. Why do that, when you can schedule the wizard to run on a weekly basis?
Kudos to my good friend and fellow MVP’er, Kevin Royalty, for this information.
STEP 1 – Run the WSUS Cleanup Wizard manually
Before scheduling the wizard to run automatically, it is important to run the wizard manually first, especially if it has not been run in a long time. Do not be concerned if the wizard takes hours (literally) to run the first time. My fellow MVP’er, Philip Elder, blogged that he had one server required 36 hours to do the initial cleanup!!!
Review my post for running the wizard manually.
STEP 2 – Create the WSUS Cleanup Batch file
- Go to the Codeplex site and download the WSUS Cleanup v2 tool (zip file)
- Extract the files to your desired folder (C:\Scripts in my case). Three files are extracted.
- You then need to create your own batch script/command, and documentation to do that is available from the Codeplex site
– OR –
Just download my script (WSUSCleanup.txt) and save it to your Scripts directory (be sure to rename it from WSUSCleanup.txt to WSUSCleanup.cmd)
STEP 3 – Schedule to run the batch file automatically
The only thing left is to schedule the task to run on a regular basis (perhaps weekly on Sunday mornings).
- Click Start –> Administrative Tools –> Task Scheduler
- Click Create Basic Task… from the right hand frame
- Type in a name (for example Weekly WSUS Cleanup)
- Click to run it weekly
- Click to run it every Sunday, and set your time (for example 9:00am)
- Click to ‘Start a program’
- Browse and locate your script (again, as a reminder, if you downloaded my script, be sure to rename the suffix from .txt to .cmd)
- Click to select (enable) the ‘Open the Properties dialog box …’ option, then click Finish.
- Click to select (enable) the ‘Run whether user is logged on or not’ option, then click OK
- You will be prompted to enter the appropriate user account information for running this task.
- I would suggest running the task immediately after creating it and monitor to make sure it runs successfully.
Finally! One of the major features, in the eyes of many I.T. professionals and consultants, missing from the Windows Server 2012 Essentials product was the ability to fully manage, approve/reject, and deploy Microsoft updates to the attached workstations in the network.
This feature, Windows Server Update Services (WSUS), was a built-in server role in all of the Small Business Server (SBS) product line, as well as Windows Server 2012 Standard and Datacenter, with enhanced features.
Microsoft has now released the enhanced version of WSUS for Windows Server 2012 Essentials! It is packaged as a Microsoft hotfix.
Here are the links you need:
- Coffee Coaching – HP & Microsoft blog announcement
- WSUS features and requirements (KB 2762663)
- WSUS 2012 Evaluation Guide
- Download the Microsoft WSUS hotfix here
There have been several reports about recent updates taking an extremely long time (4-6 hours) to completely install on SBS 2008 servers. For example, some report that after rebooting the server and it starts to apply updates, it may sit at 0% for more than an hour.
The reaction is to think that something is wrong and to force a reboot.
These issues are being investigated, but the best advice is that if you have already started updating your server, just let it run and do not force a reboot. And expect that it may be down for several hours.
If you have not yet started applying updates, my typical procedure is as follows:
Reboot the server BEFORE installing any updates
Install updates in groups – all security patches first, then .Net patches, then each rollup or service pack individually
After the updates have been applied, some things may still not work, such as some services not starting or Companyweb not available. In these cases, first try rebooting the server again, and checking things out. for companyweb, please remember that you generally need to manually run the psconfig command after installing SharePoint updates.
finally, it is always advisable to make sure you have a full, validated backup of your server before installing any patches, rollups or service packs,