In many of the disaster recovery scenarios in Exchange 2007, one of the most useful cmdlets is the “Move-mailbox” with the “ConfigurationOnly” parameter.

With the “ConfigurationOnly” parameter the mailbox content is not physically moved but instead mailbox configurations gets changed “mailbox location”, for example we could direct the mailbox(s) to a functioning server and create a dialtone database or if we have a database with clean shutdown state (from a failed server or backup) we could mount this database on a different functioning server and redirect users to that database (Database Portability) .

In Exchange Server 2010 the “Move-Mailbox” cmdlet is now replaced with the “New-MoveRequest” cmdlet and the “ConfigurationOnly” parameter is no longer available.

So in Exchange 2010 to maintain this powerful functionality and to allow a configuration only move of mailboxes, we will be using the “Set-Mailbox” cmdlet with the “Database” parameter, for example to move all the users whose mailboxes is on database DB1 to DB5 we will use:

Get-Mailbox -Database DB1 | Set-Mailbox –Database DB5

The example above shows how powerful the Set-Mailbox cmdlet in Exchange 2010 and care should be taken when working with this cmdlet.

In Exchange 2007 Microsoft Office Outlook Web Access (OWA) includes a feature to let users change their passwords. However, this feature requires that users log on to OWA to change their passwords. In a scenario in which a user password has expired, or in which users have to change their passwords when they first log on, users cannot log on to OWA to access the password change feature. Exchange 2007 SP3 adds a new feature to the Client Access server (CAS) role. This feature creates a new Internet Information Services (IIS) 7 module that detects expired passwords, and redirects users to a new change password page. By default, this feature is disabled. To enable the password reset feature, you must set a registry key.

To enable the password reset feature  

1.     Log on to the Exchange server that is running the CAS role by using an account that has local administrator rights.

2.     Start Registry Editor, and then locate the following registry subkey:

HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA

3.     Create the following DWORD value if it does not already exist:

Value name: ChangeExpiredPasswordEnabledValue type: REG_DWORDValue data: 1

4.     Exit Registry Editor.

5. Perform IISReset.

The password reset functionality is enabled when ChangeExpiredPasswordEnabled is set to a nonzero (0) value. If this registry value is missing or is set to a value of zero, the password reset functionality is disabled.

Exchange 2010 SP1: Now that SP1 has RTM, it brings this feature to Exchange 2010, the password reset feature is not active by default.  To activate this feature in Exchange 2010 SP1, you will need to add the registry key above.

·        http://support.microsoft.com/kb/328841

·        http://support.microsoft.com/kb/245822

·        Exchange 2003 - http://support.microsoft.com/kb/823166

·        Exchange 2007 - http://technet.microsoft.com/en-us/library/bb332342(EXCHG.80).aspx

·        Exchange 2010 - http://technet.microsoft.com/en-us/library/bb332342.aspx

What’s new on the fly:

• Server Roles: Microsoft Exchange Server 2013 Preview consists of
  the following two server roles Client Access server role and Mailbox server
  role Exchange2013 Server Roles

• Exchange Administration Center: No Exchange management console
  ,Exchange 2013 Preview provides a single unified management console that allows
  for ease of use and is optimized for management of on-premises, online, or
  hybrid deployments. The Exchange Administration Center (EAC) in Exchange 2013
  Preview replaces the Exchange 2010 Exchange Management Console (EMC) and the
  Exchange Control Panel (ECP). ExchangeAdministration Center

• No Coexistence with Exchange 2003 Planning and deployment

• Exchange 2013 architecture  RPC is no longer a supported direct access
  protocol. This means that all Outlook connectivity must take place using
  RPC over HTTPS (also known as Outlook Anywhere).

• New public folder design: Public folders in Exchange 2013 Preview
  now take advantage of the existing high availability and storage technologies
  of the mailbox store. The public folder architecture uses specially designed
  mailboxes to store both the hierarchy and the public folder content. This new
  design also means that there is no longer a public folder database. Public
  folder replication now uses the continuous replication model. Public
  Folders.

• 2013 Preview has *Offline* access in Outlook Web App (OWA).

• The transport pipeline in Exchange 2013 Preview is now made up of
  several different services: the Front End Transport service on Client
  Access servers, the Hub Transport service on Mailbox servers, and the Mailbox
  Transport service on Mailbox servers. For more information, see Mail
  Flow.

• Site mailboxes improve collaboration and user productivity by allowing access to both documents in a SharePoint site and email messages in an Exchange mailbox, using the same client interface. A site mailbox is functionally comprised of SharePoint site membership (owners and members), shared storage through an Exchange mailbox for email messages and a SharePoint site for documents, and a management interface that addresses provisioning and lifecycle needs.see Site Mailboxes

The whole list is here http://technet.microsoft.com/en-us/library/jj150540(EXCHG.150).aspx#BKMK_Share

When upgrading your Exchange 2010 CAS to SP2 you may encounter the following error:

The "IIS WMI Compatibility" component is required.  Install the component via the Web Server Manager.

The IIS6 WMI Compatibility is a new prerequisites for upgrading to Exchange 2010 SP2

To upgrade from the command line without erros run:

setup.com /m:upgrade /InstallWindowsComponents

To upgrade from the GUI without erros

Before you run the Exchange SP2 setup program on your CAS Servers do the following:

• On the Start menu, navigate to All Programs > Accessories > Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:
  Import-Module ServerManager
• Use the Add-WindowsFeature cmdlet to install the necessary operating system component:
  Add-WindowsFeature Web-WMI