Cumulative Update 6 for Exchange Server 2013 (KB2961810) & Update Rollup 7 For Exchange 2010 SP3 (KB2961522)

The Exchange team is announcing the Cumulative Update 6 for Exchange Server 2013 (KB2961810) & Update Rollup 7 For Exchange 2010 SP3 (KB2961522).

Dial Tone Portability in Exchange 2013

Here with the good reference of Dial Tone Portability from Technet.

Dial tone portability is a feature of Microsoft Exchange Server 2013 that enables users to have a temporary mailbox for sending and receiving email while their original mailbox is being restored or repaired. The temporary mailbox can be on the same Exchange 2013 Mailbox server or on any other Exchange 2013 Mailbox server in your organization that has databases with the same database schema version. This allows an alternative server to host the mailboxes of users who were previously on a server that is no longer available. Clients that support Autodiscover are automatically redirected to the new server without having to manually update the user's desktop profile. After the user's original mailbox data has been restored, an administrator can merge a user's recovered mailbox and the user's dial tone mailbox into a single, up-to-date mailbox.

The process for using dial tone portability is called a dial tone recovery. A dial tone recovery involves creating an empty database on a Mailbox server to replace a failed database. This empty database, referred to as a dial tone database, allows users to send and receive email messages while the failed database is recovered.

There are three options for performing a dial tone recovery:

• Dial tone recovery on the server with the failed database   If the server hosting the failed database is still functional, we recommend that you perform a dial tone recovery on that server. This means less downtime because you don't need to move database files between servers. In addition, you won't need to reconfigure messaging profiles for clients that don't support Autodiscover.
• Dial tone recovery using an alternate server for the dial tone database   If a server fails and needs to be rebuilt, the most efficient way to give users basic mail functionality is to create a dial tone database on another server, and use database portability to move the users' mailbox configuration to that new server. Because this process involves moving the dial tone database back to the original (recovered) server, this option adds more time to the overall recovery process. In addition, this process is more complex than performing a dial tone recovery on the original server. When performing this process, the server hosting the dial tone database must have sufficient resources to support the added load of the additional users. In addition, if the users' client doesn't support Autodiscover, their messaging profile will need to be reconfigured to point to the dial tone server.
• Dial tone recovery using and staying on an alternate server for the dial tone database   This is similar to the preceding option, except that you don't revert back to the original server. We recommend this option for situations in which it isn't possible or feasible to recover the failed server. In this scenario, users typically remain on an alternate server after the recovery operation has completed. When performing this process, the server hosting the dial tone database must have sufficient resources to support the added load of the additional users. In addition, if the users' client doesn't support Autodiscover, their messaging profile will need to be reconfigured to point to the dial tone server.

All three options follow the same basic steps:

1. Create an empty dial tone database to replace the failed database. 
   This new database will allow users who had mailboxes on the failed database to send and receive new messages. Dial tone portability allows you to point a user to a different database without moving the mailbox. If you created the dial tone database on a different server than the server that housed the failed database, you need to move the mailbox configuration to that new server.
2. Restore the old database. 
   Use the backup and recovery software you typically use to restore the failed database. If there is no backup of the failed database, recover the failed database using other means if possible. If you're using the same server for dial tone recovery, you need to restore the database to a recovery database (RDB).
3. Swap the dial tone database with the restored database. 
   After the failed database is restored, swap it with the dial tone database. This gives the users the ability to send and receive email and access all the data in the restored database. If users were moved to a dial tone database on another server, you need to move the mailbox configuration back to the original server.
4. Merge the databases. 
   To get the data from the dial tone database into the restored database, you merge the data using the New-MailboxRestoreRequest cmdlet.

Perform a dial tone receovery which must be done via EMS:

1. Make sure that any existing files for the database being recovered are preserved in case they're needed later for further recovery operations.
2. Use the New-MailboxDatabase cmdlet to create a dial tone database, as shown in this example.
   New-MailboxDatabase -Name DTDB1 -EdbFilePath D:\DialTone\DTDB1.EDB -Server EXCH01
   

3. Use the Set-Mailbox cmdlet to rehome the user mailboxes hosted on the database being recovered, as shown in this example.
   Get-Mailbox -Database DB1 | Set-Mailbox -Database DTDB1
   

4. Use the Mount-Database cmdlet to mount the database so client computers can access the database and send and receive messages, as shown in this example.
   Mount-Database -Identity DTDB1
   

5. Create a recovery database (RDB) and restore or copy the database and log files containing the data you want to recover into the RDB. For detailed steps, see Create a recovery database.
6. After the data is copied to the RDB, but before mounting the restored database, copy any log files from the failed database to the recovery database log folder so they can be played against the restored database.
7. Mount the RDB, and then use the Dismount-Database cmdlet to dismount it, as shown in this example.
   Mount-Database -Identity RDB1
   Dismount-Database -Identity RDB1
   

8. After the RDB is dismounted, move the current database and log files within the RDB folder to a safe location. This is done in preparation for swapping the recovered database with the dial tone database.
9. Dismount the dial tone database, as shown in this example. Note that your end users will experience an interruption in service when you dismount this database.
   Dismount-Database -Identity DTDB1
   

10. Move the database and log files from the dial tone database folder into the RDB folder.
11. Move the database and log files from the safe location containing the recovered database into the dial tone database folder, and then mount the database, as shown in this example.
    Mount-Database -Identity DTDB1
    

    This ends the service interruption for your end users. They will be able to access their original production database and send and receive messages.
12. Mount the RDB, as shown in this example.
    Mount-Database -Identity RDB1
    

13. Use the Get-Mailbox and New-MailboxRestoreRequest cmdlets to export the data from the RDB and import it into the recovered database, as shown in this example. This will import all the messages sent and received using the dial tone database into the production database.
    $mailboxes = Get-Mailbox -Database DTDB1
    

    $mailboxes | %{ New-MailboxRestoreRequest -SourceStoreMailbox $_.ExchangeGuid -SourceDatabase RDB1 -TargetMailbox $_ }
    
    

14. After the restore operation is complete, you can dismount and remove the RDB, as shown in this example.
    Dismount-Database -Identity RDB1
    Remove-MailboxDatabase -Identity RDB1

Install and Configure Microsoft Exchange 2013 (Part 2)

3.0  Install Exchange Mailbox and Client Access Server Roles

1. Start Exchange 2013 Setup by double-clicking Setup.exe

2. Select “Connect to the Internet and check for updates” and Next

3. Next

4. The Introduction page gives additional guidance for the installation procedure. Review the content and Click next to continue.

5. On the License Agreement page, review the terms. If you agree to the terms, select I accept the terms in the license agreement, and then click next.

6. On the Recommended Settings page, select Use recommended settings then click Next.

  

7. On the Server Role Selection page, select Mailbox role and Client Access role and next

8. On the Installation Space and Location page, either accept the default installation location or click Browse to choose a new location with adequate storage space.

  

9. One of the new features of Exchange 2013 is the Malware Protection. If installing the Mailbox role a Malware Protection Settings page will appear. Choose whether to enable or disable malware scanning and click Next.

10. On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If unsuccessful, perform the required tasks and click Back, and Next to run the Readiness check again. If successful, click Install to proceed.

11. The installation will be performed.

12. Once the setup completes the installation, on the Setup Completed page, click Finish.

13. Restart the computer after Exchange 2013 installation has completed 

Install and Configure Microsoft Exchange 2013 (Part 1)

1.0 Install Prerequisite for Mailbox and Client Access Server Roles

1.1 Install the Windows Server 2012 R2 and Windows Server 2012 Prerequisites

1.     Open Windows PowerShell with Run as Administrator

2.     Run the following cmdlet to install the Remote Tools Administration Pack

Install-WindowsFeature RSAT-ADDS

3.     Run the following cmdlet to install the required Windows components for the server that install both the Mailbox and Client Access server roles on the same computer and restart the computer after install

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

  

4.     Install Microsoft Filter Pack 2.0 64-bit and Microsoft Office 2010 Filter Pack Service Pack 1 (SP1) 64-bit update

5.     Install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit located in D:\Exchange 2013 Pre-Requisite\Unified Communications Managed API 4.0 Runtime

2.0 Prepare Active Directory and Domains

Exchange needs to prepare Active Directory so that it can store information about your users' mailboxes and the configuration of Exchange servers in the organization. In fact, the ADprep is part of the installation. However, i prefer to run separately to see the outcome.

2.1            Prepare Active Directory

1.     Open a Windows Command Prompt window and navigate to the Exchange installation files. Run the following command:

Setup.exe /PrepareAD /OrganizationName:"YourExchangeOrgName" /IAcceptExchangeServerLicenseTerms

2.2            Prepare Active Directory Domains

1.     Open a Windows Command Prompt window and navigate to the Exchange installation files. Run the following command:

Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms