Upgrade Exchange 2010 SP1 or SP2 to SP3 for SBS 2011 Standard



Install Exchange 2010 SP3 on SBS 2011



1) Ensure that there is a good, full backup of VM or server

2) Make sure that you DO NOT have Windows Management Framework (WMF) 3.0      installed on the server

  • From a command prompt run –  wmic qfe list | findstr “2506143”
  • or look for KB2506143. You will need to uninstall this patch and then reboot the server before you install the SP3 upgrade

3) Ensure the account running the update is a member of Schema Admins and Enterprise Admins as SP3 involves an AD schema update

4) Reboot server before upgrading if not already rebooted from above step – Definitely recommended

  • Not required but allows for a clean start up, frees up resources and releases connections
  • Also ensures that in the event any “Previous installations” were attempted and NOT completed the server is rebooted to a ready state

5) Export current Certificate for mail services with private key

  • If the mail server certificate isn’t already fully exported and nicely tucked away somewhere safe and accessible then do so before performing the upgrade….JUST IN CASE

6) Stop Backup Exec services if in use

7) Turn off SBS manager in services

8) Stop BES services (if applicable) in correct order

To stop the services:

BlackBerry Controller

BlackBerry Dispatcher

BlackBerry Router

All remaining BlackBerry Enterprise Server services

9) Disable Anti Virus services

  • Disable don’t just Stop “real time scanning”. This will cause the Languages install phase to stall and I have seen users report times of up to 1.5 hours to complete…JUST THIS PHASE

10) Install  Exchange SP3

11) Upon SP3 completion launch Exchange Management Shell and execute:

get-exchangeserver | fl name,edition,admindisplayversion


12) In Internet Explorer deselect “Check for Publisher’s certificate” and “Check for server certificate revocation”


When you install an update rollup package, Exchange tries to connect to the certificate revocation list (CRL) Web site. Exchange examines the CRL list to verify the code signing certificate. If Exchange can’t connect to the CRL Web site, the following symptoms may occur:

  • The installation takes a long time to complete.
  • You receive the following message during the installation: Creating native images for .Net assemblies


  • Start Internet Explorer
  • On the Tools menu, click Internet Options
  • Click the Advanced tab, and then locate the Security section
  • Clear the Check for publisher’s certificate revocation check box, and then click OK


13) Update to latest rollup

14) Enable Anti Virus “real time scanning” to automatic (or previous startup state)

15) In Internet Explorer select “Check for Publisher’s certificate” and “Check for server certificate revocation”

16) Reboot server

17) Ensure all required services are running

SBS 2011 Monitoring, lento

Le prestazioni di SBS 2011 possono decadere a causa di “Sql Monitoring” con un eccessivo utilizzo di memoria e dimensioni del database eccessive (10 gbit).

Limitare l’uso di Ram dalla console Sql Management Studio e/o ricreare il database di SBSMonitoring

vedi: http://kwsupport.com/2013/05/sbsmonitoring-database-is-nearing-maximum-size/

script: Create-SBSMonitoringDb

se non funziona, modificare lo script così:

Stop-Service DataCollectorSvc -force
Stop-Service ‘MSSQL$SBSMONITORING’ -force

vedi: https://blogs.technet.microsoft.com/sbs/2011/08/22/how-to-recreate-the-sbsmonitoring-database/

WSUS not working on SBS2011


**** rimuovere \\ da filtro isapi ****

WSUS not working on SBS2011

I was investigating a fault today for a client – their new SBS 2011 server had stopped working with WSUS.  As my investigation went on I found that this issue would also affect the SBS Client Connect as well as other web based applications on this server.

The SBS console was reporting “An error occured while retrieving updates information.” as the screen below shows.


I did some digging and found that the WSUS console was broken too.

The event logs showed the error below.

Source: IIS-W3SVC-WP

Event ID: 2274

ISAPI Filter ‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

Look closely and you will notice above that there’s a double \\ in the path name.


Once I’ve modified it to remove the double \\ and done an IISRESEt – it’s all working just fine.  The picture below shows the problem line AFTER I’ve modified it.