Exchange 2010 SP1 support status in WebsitePanel RRS feed

  • Question

  • At the moment we are investigating possible issues with GAL access that may be experienced after upgrading Exchange 2010 with SP1 update (without hosting switch). Currently Exchange 2010 SP1 is not supported in WebsitePanel and we strongly discourage you to install Exchange 2010 SP1 on production environment.
    Inesa Fain - MSFT
    Wednesday, October 13, 2010 6:29 PM

All replies


    Status update for Exchange 2010 SP1:

    WSP 1.1.0 provides support for Exchange 2010 SP1 installed with /hosting switch which is the recommended version of Exchange to work with WebsitePanel.

    Exchange 2010 SP1 installed without /hosting switch is not supported (please see  this post for details).


    Customers who recently upgraded their Exchange 2010 managed by WebsitePanel with SP1 without /hosting switch may experience GAL access issue as described here. The cause of this issue is msExchQueryBaseDN attribute that is used for OWA segregation in WebsitePanel Exchange 2007 and Exchange 2010 modules. After Exchange 2010 is upgraded with SP1 without using /hosting switch, msExchQueryBaseDN attribute set to any value causes Global Address List in Outlook clients to be empty.


    WebsitePanel 1.1.0 provides a workaround for GAL access issue that doesn't set msExchQueryBaseDN attribute for newly created users. This workaround is not switched on by default; to switch it on you need to add WebsitePanel.Exchange.ClearQueryBaseDN setting to the WebsitePanel Server’s web.config as described below:



       <add key=”WebsitePanel.Exchange.ClearQueryBaseDN” value=”true” />



    This workaround stops setting the msExchQueryBaseDN attribute for newly created users, but it doesn't blank out the attribute for previously created users. If you decide to use the workaround and there were already Exchange users created by WebsitePanel before the fix, you would need to do additional steps to reset the attribute for existing users.


    Please note that after the workaround is switched on, OWA segregation that was previously done by setting msExchQueryBaseDN attribute no longer works. For guidance on additional configuration steps that may need to be done for OWA and Outlook to show correct address lists, please refer to the article provided by WebsitePanel customer Omar Armenteros who first identified the issue and how he resolved the problem:



    Please note that the steps may vary depending on Exchange configuration and look at this article as helpful guidance but not as a complete solution. The guidance provided in this article is not supported by Microsoft.


    If you decide not to apply the workaround, please make sure that Offline Address Book is downloaded to end-user's Outlook. In this case, OAB will be default address list shown to a customer which may reduce the severity of GAL access issue for end-users.

    Inesa Fain - MSFT
    Thursday, November 18, 2010 12:00 AM