Category Archives: 14023

Exchange 2010 SP3 and Exchange 2013




Yesterday Microsoft released Service Pack 3 for Exchange 2010.  You can download Exchange 2010 SP3 here.



We had been told at MEC 2012 that Exchange 2010 SP3 would be required for Exchange 2013 interoperability, and it is. Unfortunately, we learned yesterday that we now need to wait for Exchange 2013 Cumulative Update 1 to complete the coexistence story.  Exchange 2013 CU1 is due Q1 2013 — in other words, within 90 days or so.  I expect that it might be sooner.



Exchange 2013 CU1 includes a number of fixes that will make the coexistence story much better and smoother.  It will be worth the wait.  This will be the first update for Exchange 2013 using the new service strategy and we can expect new CUs every quarter.



The good news is that this gives us time to install Exchange 2010 SP3 in our environments prior to introducing Exchange 2013 to production.  It also gives us time to test coexistence in a test lab, or as stated on the EHLO Blog, “Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1.



Exchange 2010 SP3 includes the same schema update as Exchange 2013 RTM – schema version 15137.  You can run the following command from a CMD prompt to determine your current Exchange schema version:



dsquery * CN=ms-Exch-Schema-Version-Pt,cn=schema,cn=configuration,dc=domain,dc=local -scope base -attr rangeUpper

You can refer to the Exchange table in the TechNet article, “How to determine the current Active Directory or Exchange Server schema version“, to determine your current schema version.



Even if you have no plans to migrate to Exchange 2013 yet, Exchange 2010 SP3 includes several important updates and fixes, as well as allowing you to install Exchange 2010 on Windows Server 2012.  This is really huge, since Windows Server 2012 is an amazing platform and Exchange can really benefit from SMB3.  And since Windows 2012 includes PowerShell v3, this means that Exchange 2010 should be compatible with that version and Management Framework 3.0.



SP3 also includes a new Sent Items Management feature for Outlook Web Access. This provides control over whether an item that is “sent as” you, or “on behalf of” you, is copied to your Sent Items folder and to the sender’s Sent Items folder. Before Exchange 2010 SP3, messages that are “sent as” you or “on behalf of” you are copied only to the sender’s Sent Items folder.



You can configure the Sent Items Management feature in OWA on the Options page.



Note that RU6 for Exchange 2010 SP2 was also released yesterday.  Exchange 2010 SP3 includes all those fixes, plus additional ones.  Refer to the EHLO Blog article and TechNet for details.


The New Exchange 2007 SP3 Password Reset Tool

Exchange Server 2007 Service Pack 3 includes a handy new web page that allows users to change their password before logging into Outlook Web Access (OWA).

Previously, new users who are required to change their password at next logon or users whose password has expired cannot log on to OWA.  They will get the less than helpful error from the OWA, “The user name or password that you entered is not valid. Try entering it again”, as shown below:

 
In order to logon to OWA, the user must logon to the network, enter their old password and the new password.  Obviously, this causes problems for remote users whose password has expired or for new users who must change their password before logging in for the first time.

Exchange 2007 SP3 introduces a new SSL web page for these users that allows the user to change their password outside of OWA.  The page tells the user, “Your password has expired and you must change it prior to signing in to Microsoft Outlook Web Access.”

 
Once the user changes their password, the page redirects the user back to OWA.

This new functionality is not enabled by default, since some organizations do not allow password changes from outside the internal network.  To enable it:
  • Logon to the CAS with administrator rights
  • Run Regedit and navigate to HLKM\SYSTEM\CurrentControlSet\services\MSExchange OWA
  • Create a new DWORD (32-bit) Value called ChangeExpiredPasswordEnabled
  • Assign the ChangeExpiredPasswordEnabled value: 1
  • Restart IIS using IISRESET /NOFORCE from the command line
Surprisingly, this functionality does not exist in Exchange Server 2010 (or the SP1 beta).  I hope Microsoft decides to implement this when Exchange 2010 SP1 is finally released.  It’s a pretty handy feature!

Fix for Microsoft Exchange Protected Service Host service failed to start

If you install Exchange Server 2007 SP3 on a Windows Server 2008 R2 all-in-one server, you may get an error during installation of the Hub Transport role.  The error says,
A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Protected Service Host service to connect.

The Microsoft Exchange Protected Service Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
This happens because there is a dependancy in the Microsoft Exchange Service Host service on IPv6.  Check to ensure that Internet Protocol Version 6 (TCP/IPv6) is enabled on the properties of the network adapter.