Disable Windows Update Services (WSUS) – Small Business Server and Doman Controllers

Windows Update Services, or WSUS can be a real pain at the best of times. On Small Business Servers, which are often neglected, some strange issues can arise.

The most common issue is that WSUS goes crazy and downloads everything. Yes, this does happen.

You may not know, but you shouldn’t uninstall WSUS on a domain controller, IE Small Business Server.

Here is how you can disable it and clean up the mess.

  1. Under Options, select Products and Classifications 
  2. Unselect everything, and then select Bing Bar. You need something selected.
  3. Under Classifications, select Critical Updates
  4. Remove Automatic Approvals
  5. Run the Server Cleanup Wizard with everything selected
  6. Once this is done, you can leave WSUS as is, or you can disable the service
  7. With the service stopped and disabled, you can also delete the content database. Only do this if you are never going to use WSUS again.

Hopefully this has helped someone.

SBS 2011: Post Migration – Problems with backup, spfarm, spsearch

If you install SBS 2011 and select install the latest updates, Sharepoint Foundation 2010 SP1 will be installed. SP1 for Sharepoint will only half install. It requires manual interaction to finish the install. If this is not done, you will recieve errors in the event log:

Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key. 

This can be fixed by doing the following:

  • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
  • Once the shell opens, type the following command followed by enter:
    (get-spserver $env:computername).NeedsUpgrade


If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.

To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:

In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

1. Open an Administrative command prompt.
2. Change directory to C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.

Link: http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx

SBS 2003 -> 2011 Migration Part 1 – SBS 2011 Install

Microsoft Small Business Server provides many improvements over Small Business Server 2003 and 2007. Built on Windows Server 2008 R2, SBS 2011 Standard includes Microsoft Exchange Server 2010 SP1, Microsoft SharePoint Foundation 2010, and Windows Server Update Services.

This post will cover the following areas:

  • Configuring a SBS 2011 server for migration from SBS 2003 to 2011
  • Migrating Data
  • Migration of Exchange 2003 to Exhcange 2010 SP1
  • Migration of Sharepoint V3 to Foundation 2010

You can download the migration manual here.

I take it if you are reading this document, you have made the decission to upgrade to SBS 2011.

To begin there’s a few things you need to do first.

  1. Your new server requires atleast 120gb on the main partition to be able to install SBS 2011.
  2. Your existing server needs all service packs applied. This includes SBS 2003 SP1, Exchange 2003 SP2 and the Sharepoint updates. If these are not installed, the migration wizard will fail.
  3. Install Powershell 2.0 and the Microsoft Configuration Analyzer on the existing server
To begin:
  1. On the existing server, insert the SBS 2011 install DVD and run the migration tool. Step through this. This will let you know if you are missing any required updates.
  2. At the end of the migration wizard, it will ask you to run the answer file wizard. Run this and create an answer file
  3. Once you know the answer file is correct, you need to copy it on to a USB stick or create an ISO with this file on it (If using VMWare)
  4. You can also copy the Tools directory off the disk and place this folder on the existing server. This folder contains the migration wizard and answer file wizards.
  5. On the new server, install the SBS 2011 installation disk. Run the setup.
  6. Go through the options and install using custom install if you wish. Make sure the USB stick with the migration file is inserted (or mounted).
  7. Once the server is installed and has rebooted, you will see that migration mode is selected. This means it has detected the answer file.
  8. You will see the verify clock settings once you select migration mode. If you don’t seen this, something is wrong with the answer file.
  9. Next you will need to confirm your network settings on the source and destination server.
  10. Next you will need to confirm your source name and authentication credentials.
  11. If you get an error saying “Cannot verify server” hit shift + f10 and check your IP/DNS settings. I recommend doing a NSLOOKUP to ensure these settings are correct.
  12. Next you will need to configure the company information.
  13. Next SBS 2011 will now install any updates and complete the install. After around the 3rd reboot you will see the server in Active Directorty.
  14. Just a note: The setup says this step will take 30 minutes. Ours took a lot longer, around 2 hours. At one point it looks like it fails. Reading the log file in c:program filesWindows Small Business ServerLogs we found there were errors replicating. Replication took along time.

Stay tuned for Part 2.

Installing SBS 2003 SP1 after Exchange SP2 and Windows 2003 SP2 already installed

Doing a migration to SBS 2011 and I’ve had a few interesting issues. With this customer, SP1 for SBS 2003 was not installed. Interestingly, the other service packs were installed. Upon installing SBS SP1 I got the following error in the error log saying that the current user didn’t have the correct access. I was logged in with administrator (which you need to be logged in with to install SP1 for some odd reason).

Upon further investigation I found that the SBS user templates were disabled. I re-ran the SP1 wizard and it installed correctly.