LCR (local continuous replication)
this was mainly used for small business who wanted to replicate a copy of their Exchange database to another disk on the same server.

SCC (Single copy cluster)
was what I would call a traditional Exchange cluster which used shared storage to host the Exchange database.

CCR (cluster continuous replication)
was used to replicate Exchange database information between 2 Exchange server allowing for hardware and storage redundancy but was limited to 1 Active node and 1 Passive node.

SCR (standby continuous replication)
was introduced in Exchange 2007 SP1 to provide the ability to replicate Exchange databases to an disaster recovery location.

Exchange 2007 SP1 Rollup 9 is available. You can download it here.

Update Rollup 9 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

After you migrated from Exchange 2003 to Exchange 2007, you receive an error when you try to edit your Address Lists “All Contacts”, “All Groups”, “All Rooms”, “All Users”, “Default Global Address List”, “Public Folders”.

let’s update the Address Lists!

Set-AddressList “All Users” -IncludedRecipients MailboxUsers

Set-AddressList “All Groups” -IncludedRecipients MailGroups

Set-AddressList “All Contacts” -IncludedRecipients MailContacts

Set-AddressList “Public Folders” -RecipientFilter { RecipientType -eq ‘PublicFolder’ }

After you migrated from Exchange 2003 to Exchange 2007, you receive an error when you try to edit your recipient policy “Default Policy”.

“Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the ‘Set-EmailAddressPolicy’ task, with the Exchange 2007 Recipient Filter specified.”

Oké, let’s update the recipient policy! With the following command you can see the properties of this recipient policy.

Get-EmailAddressPolicy | fl Name,*RecipientFilter*,ExchangeVersion

Set-EmailAddressPolicy “Default Policy” -IncludedRecipients AllRecipients

After running this commands, you’re able to edit the “Default Policy” again.

If you want an overview off all the mailboxes in your Exchange 2007 environment with there primairy SMTP address and there extra SMTP aliasses, you can run the following command.

For a overview off all the options after the pipe command, you can the following command.

Get-Mailbox -Identity <useralias> | fl

Get-Mailbox | fl UserPrincipalName, ServerName, PrimarySMTPaddress, Emailaddresses

Mailbox data isn’t specific to any one server. Why should access to this data be?  This is the reason behind the Database Portability feature, enabling a mailbox database to be mounted on any server in the same forest. In earlier Exchange versions, such an object could only be mounted in an RSG (Recovery Storage Group). Only mailbox databases are portable. Public Folder  data should be moved by replication, not file copy.

Database Portability cuts disaster recovery restore time:

1) Run eseutil /r <Enn> to commit all logs and put database into clean shutdown state.
<Enn> specifies the log file prefix for the storage group that contains the database into which you intend to replay the log files. The log file prefix specified by <Enn> is a required parameter for Eseutil /r. You can run the following Exchange Management Shell command to determine the log file prefix of a storage group:
Get-StorageGroup <Server_Name>\<StorageGroup_Name> | fl LogFilePrefix

2) Select a storage group on the replacement server and create the required database.
(Note: make sure the Storage Group and the Database have the same name as previous configuration on the crashed server).
3) Enable: EMC > Server Configuration > Mailbox > Database Management > Properties > General > This database can be over written by restore. Or: Set-MailboxDatabase <Database Name> -AllowFileRestore:$true.
4) Move database files (edb & log files, Exchange Search catalog) to appropriate location on new server.
5) Mount database.
6) Run Move-Mailbox -ConfigurationOnly — so accounts in AD will point to mailboxes on the replacement machine.
Get-Mailbox -Database <SourceDatabase> |where {$_.ObjectClass -NotMatch ‘(SystemAttendantMailbox|ExOleDbSystemMailbox)’}| Move-Mailbox -ConfigurationOnly -TargetDatabase <TargetDatabase>

After replication completes, when Outlook clients try to connect to their mail, the Autodiscover service will automatically redirect them to its new location.

When you’ve an up and running Microsoft Exchange 2007 environment, you’ve to perform some maintenance on your databases after some time. You can use the tool ESEUTIL for this job. Let’s have a look on some commands.

1) Open the commandline
2) Type in eseutil /?
3) Choose the right switch

———————————————————————–
Checking your database integrity: (Note: make sure you’ve dismounted your database(s)!! )
eseutil /g “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPINTEG.edb”

eseutil /g: tool with the check integrity option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPINTEG.edb”: location of the temperary database file

       
———————————————————————–

Repairing a corrupted or damaged database:  (Note: make sure you’ve dismounted your database(s)!! )
eseutil /p “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPREPAIR.edb”

eseutil /p: tool with the repair option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPREPAIR.edb”: location of the temperary database file

       
———————————————————————–

Offline defragmentation of a database:  (Note: make sure you’ve dismounted your database(s)!! )
eseutil /d “E:\Database\SG01\MD01.edb” /t “E:\TMP\TEMPDEFRAG.edb”

eseutil /d: tool with the offline defragmentation option
“E:\Database\SG01\MD01.edb”: location of the database(s)
/t “E:\TMP\TEMPDEFRAG.edb”: location of the temperary database file

   
———————————————————————–

When you have a up and running Exchange 2003 environment, and you want to migrate to an completely new Exchange 2007 environment, also with a new Active Directory, you can use the following tools to migrate the user mailboxes.

First of all we are gonna export the user mailboxes with ExMerge, after the export, we are gonna import the mailboxes with PowerShell. You can follow this article to provide the migration step by step.

I’ve installed an Microsoft Exchange 2003 Enterprise SP2 environment with 10 user mailboxes. I’ve also installed a Microsoft Windows XP workstation with Microsoft Office 2007.

The allias of the user is the same as the User Logon Name.

By default, the Administrators, Domain Admins and Enterprise Admins have deny permissions on the Information Store. Make sure you configure the right permissions, so you have access to the mailboxes for making the export with ExMerge.

1) right-click on your Exchange Server, choose Properties
2) go to the Security tab, hit Administrators (also do this for Domain Admins and Enterprise Admins)
3) Advanced, hit Allow inheritable….Copy
4) hit Administrators, allow Send As and Receive As (also do this for Domain Admins and Enterprise Admins)
5) Restart the Microsoft Exchange System Attendant service.

Configure an MAPI profile for a user and generate some e-mail traffic. (e-mail, calendar items, tasks etc..)

Now we’re gonna export the user mailboxes with ExMerge.

        

In the next post, we’re gonna import the user mailboxes into the new Microsoft Exchange 2007 SP1 environment using PowerShell.