exchange migration of legacy public folders to 2013

ILL 3100: Migrating Public Folders from Exchange Server 2007 to Exchange Server 2013

DISCLAIMER

© 2015 Microsoft Corporation. All rights reserved.

Microsoft, Internet Explorer, Outlook, Windows, and Windows PowerShell are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND TRAINING PURPOSES ONLY AND ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

No part of the text or software included in this training package may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission from Microsoft. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

To obtain authorization for uses other than those specified above, please visit the Microsoft Copyright Permissions Web page athttp://www.microsoft.com/about/legal/permissions

This content is proprietary and confidential, and is intended only for users described in the content provided in this document. This content and information is provided to you under a Non-Disclosure Agreement and cannot be distributed. Copying, disclosing all or any portion of the content and/or information included in this document is strictly prohibited.

Table of ContentsLab: Migrating Public Folders from Exchange Server 2007 to Exchange Server 2013

Exercise 1: Enabling Connectivity to Legacy Public Folders

Exercise 2: Using Batch Migration to Migrate Public Folders

Exercise 3 (Optional): Removing Exchange Server 2007 from the Organization

Lab: Migrating Public Folders from Exchange Server 2007 to Exchange Server 2013During this lab, you will migrate the currently deployed Exchange Server 2007 organization public folders to Exchange Server 2013. You will then decommission the legacy Exchange Server 2007 server.

Estimated time to complete: 45 minutes

What You Will LearnAfter completing the exercises, you will be able to:

Enable coexistence sharing of legacy public folders

Migrate legacy public folders to modern public folders

Decommission Exchange Server 2007

ScenarioContoso Ltd. has installed Exchange Server 2013 into their Exchange Server 2007 organization and has already migrated mailboxes to the new Exchange server. As the company’s Exchange administrator, you need to enable access to the legacy public folders for mailboxes on Exchange 2013 during coexistence and then migrate the organization’s legacy public folders to the new Exchange server.

Exercise 1: Enabling Connectivity to Legacy Public FoldersIn this exercise, you will enable access from Exchange 2013 mailboxes to legacy public folders that are homed on Exchange 2007.

Virtual MachinesThe following virtual machines will be used during this exercise.

DC1

EX07

EX13

CL1

Tasks1. Create an empty mailbox database on each public folder server.

a. Switch to EX07 and open the Exchange Management Shell.

b. In the Exchange Management Shell, type the following, and then press Enter.

New-MailboxDatabase -StorageGroup "EX07\First Storage Group" -Name "PFProxyMDB"

c. In the Exchange Management Shell, type the following, and then press Enter.

Mount-Database PFProxyMDBThere is no output for this command.

2. Create a proxy mailbox for public folders.

Create a proxy mailbox within the new mailbox database and hide the mailbox from the address book. The SMTP address of this mailbox will be returned by AutoDiscover as the DefaultPublicFolderMailbox SMTP address. By resolving this SMTP address, the client can reach the legacy Exchange server for public folder access.

a. On EX07, in the Exchange Management Shell, type the following, and then press Enter.

New-Mailbox -Name PFProxy -Database PFProxyMDB -UserPrincipalName [email protected]

b. At the Password prompt, type Pa$$w0rd and then press Enter.


Set-Mailbox -Identity PFProxy -HiddenFromAddressListsEnabled $true

There is no output for this command.

3. Configure user mailboxes to access the legacy public folders.

a. Switch to EX13.

b. Open the Exchange Management Shell.


Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFProxyThere is no output for this command.

d. In the Exchange Management Shell, type the following, and then press Enter.

Get-OrganizationConfig | FL *Public*Review the type of public folders and the mailboxes associated with the remote public folder mailboxes.

4. Review legacy public folders in Outlook®.

a. On CL1, on the taskbar, click Outlook 2013.

b. Under the folder list, click the ellipsis, and then click Folders.

c. In the folder list, expand Public Folders, expand All Public Folders, and review the list of folders.

You may have to wait until the public folders become visible.

d. In the system tray, press Ctrl and right-click the Microsoft Outlook icon.

e. In the menu, click Connection Status.

f. In the Server name column, review the connections. Notice that Outlook is connected to EX07.contoso.com, which is the Exchange 2007 server. This is the connection to the public folders that are located there.

g. Click Close.

h. In the system tray, press Ctrl and right-click the Microsoft Outlook icon.

i. In the menu, click Test E-mail AutoConfiguration.

j. In the Test E-mail AutoConfiguration window, clear the Use Guessmart and Secure Guessmart Authentication checkboxes, and then click Test.

k. Click the XML tab.

l. In the details pane, scroll to the bottom of the results, locate and review the <PublicFolderInformation> tag. Notice the SmtpAddress of the proxy mailbox you configured earlier.

m. Close the Text E-mail AutoConfiguration window.

n. Close Outlook 2013.

Exercise 2: Using Batch Migration to Migrate Public FoldersIn this exercise, you will migrate the organization’s legacy public folders to the new modern public folder structure on Exchange 2013. You will use Windows PowerShell® scripts to create public folder hierarchy documents as well as create a manual document for public folder creation. Throughout the migration, you will test connectivity to the public folders using Outlook 2013 to review end-user experience.


DC1

EX07

EX13

CL1

Tasks1. Review public folder migration scripts.

a. Switch to EX07 and then open Windows Explorer.

b. In Windows Explorer, browse to C:\LabFiles\PFScripts.

These scripts and their associated modules are used for collecting public folder information from Exchange 2007 and moving those public folders to Exchange 2013. The scripts can be downloaded from http://download.microsoft.com by searching for Microsoft Exchange 2013 Public Folders Migration Scripts.

2. Prepare for the migration.

a. On EX07 switch to the Exchange Management Shell.


CD C:\LabFiles\PFScriptsc. For verification purposes at the end of migration, we recommend that you

first take snapshots of your current legacy public folder deployment. In the Exchange Management Shell, type the following, and then press Enter.

Get-PublicFolder -Recurse | Export-CliXML C:\LabFiles\PFScripts\Legacy_PFStructure.xml


Get-PublicFolderStatistics | Export-CliXML C:\LabFiles\PFScripts\Legacy_PFStatistics.xml

e. In the Exchange Management Shell, type the following, and then press Enter.

Get-PublicFolder -Recurse | Get-PublicFolderClientPermission | Select-Object Identity,User -ExpandProperty AccessRights | Export-CliXML C:\LabFiles\PFScripts\Legacy_PFPerms.xml

f. If the name of a public folder contains a backslash \, the public folders will be created in the parent public folder when the migration occurs. Before you migrate, we recommend that you rename any public folders that have a backslash in the name.

Use the following command to find public folders that may contain a backslash. In the Exchange Management Shell, type the following, and then press Enter.

Get-PublicFolderDatabase | ForEach {Get-PublicFolderStatistics -Server $_.Server | Where {$_.Name -like "*\*"}}There should be no results after the command completes.

g. Make sure there is not a previous record of a successful migration. If there is, you will need to set that value to $false. If the value is set to $true the migration request will fail.

Switch to EX13 and the Exchange Management Shell.

In the Exchange Management Shell, type the following, and then press Enter.

Get-OrganizationConfig | Format-List PublicFoldersLockedforMigration, PublicFolderMigrationCompleteVerify that the status of the PublicFoldersLockedforMigration and PublicFolderMigrationComplete properties are False.

h. Make sure there are no existing public folder migration requests.


Get-PublicFolderMigrationRequestThere should be no results output for this command.

i. Make sure there are no existing public folders on the Exchange 2013 servers. If the commands return any public folders, they must be removed before continuing.


Get-Mailbox -PublicFolderThere should be no results output for this command.

3. Generate the CSV files.

a. Switch to EX07 and Windows Explorer.

b. In Windows Explorer, browse to C:\LabFiles.

c. In the files list, right-click PFMigration, point to Share with, and then click Specific people.

d. In the File Sharing window, click Share.

e. In the File Sharing window, click Done.

f. Switch to the Exchange Management Shell.

g. The format for the Export-PublicFolderStatistics.ps1 script is .\Export-PublicFolderStatistics.ps1 <FQDN of source server> <Folder to size map path>.


.\Export-PublicFolderStatistics.ps1 \\EX07\PFMigration\PFStats.csv EX07.Contoso.com

h. Switch to Windows Explorer.

i. In Windows Explorer, open the PFMigration folder.

j. Right-click PFStats.csv and click the second Open in the list to open the csv file in Notepad.

k. Review the last value in the rows. The value represents the current folder size in bytes.

l. Close Notepad.

m. Switch to EX13 and the Exchange Management Shell.

n. In the Exchange Management Shell, type the following, and then press Enter.

CD C:\LabFiles\PFScriptso. The format for the PublicFolderToMailboxMapGenerator.ps1 script is .\

PublicFolderToMailboxMapGenerator.ps1 <Maximum mailbox size in bytes> <Folder to size map path> <Folder to mailbox map path>. The Maximum mailbox size in bytes equals the maximum size you want to set for the new public folder mailboxes.


.\PublicFolderToMailboxMapGenerator.ps1 10MB \\EX07\PFMigration\PFStats.csv \\EX07\PFMigration\PFMap.csv

4. Create the public folder mailboxes on the Exchange 2013 server.

a. On EX13, open File Explorer and browse to \\EX07\PFMigration

b. In the PFMigration folder, right-click PFMap.csv, and then click Open to open the file in Notepad.

c. In Notepad, review the target mailbox name. The target public folders are named Mailbox1, Mailbox2, and so on. The number of mailboxes will be used in the next script to create the public folder mailboxes. For example, if your last public folder is named Mailbox13, you will need to create 13 public folder mailboxes.

d. Close Notepad.

e. Because of the small size of the public folders in this lab, a migration request using this mapping file would migrate all public folders into a single public folder mailbox, named Mailbox1. For a more realistic scenario, you will create a new public folder mapping file. In File Explorer, right-click in the file list, point to New, and then click Text Document.

f. Name the New Text Document to PFMAP_updated.csv

This file can also be copied from C:\LabFiles\Examples\PFMap_Updated.csv to the \\EX07\PFMigration folder.

g. In the Rename dialog box, click Yes.

h. Right-click PFMAP_updated.csv and the click Open.

i. In Notepad, type the following information.

"TargetMailbox","FolderPath"

"PFMB-Hierarchy","\"

"PFMB-CompanyEvents","\IPM_SUBTREE\Company Events"

"PFMB-Europe","\IPM_SUBTREE\Europe"

"PFMB-Europe","\IPM_SUBTREE\Europe\Leases"

"PFMB-Finance","\IPM_SUBTREE\Finance"

"PFMB-PublicAffairs","\IPM_SUBTREE\PublicAffairs"

"PFMB-PublicAffairs","\IPM_SUBTREE\PublicAffairs\NewsRelease-Recent"

"PFMB-Redmond","\IPM_SUBTREE\Redmond"

"PFMB-Redmond","\IPM_SUBTREE\Redmond\Executives"

"PFMB-Redmond","\IPM_SUBTREE\Redmond\Finance"

"PFMB-Redmond","\IPM_SUBTREE\Redmond\Reports"

"PFMB-Redmond","\IPM_SUBTREE\Redmond\Reports\Quarterly"

"PFMB-Redmond","\IPM_SUBTREE\Redmond\Testing"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Audit"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Expenses"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Projects"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Projects\Project Falcon"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Projects\ProjectA"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Projects\ProjectT"

"PFMB-TailspinToys","\IPM_SUBTREE\TailSpinToys\Projects\ProjectX"

j. In the menu, click File, and then click Save.

k. Close Notepad.

l. Switch to the Exchange Management Shell.

m. Create the first public folder mailbox on Exchange 2013.


New-Mailbox -PublicFolder PFMB-Hierarchy -HoldForMigration:$True

n. In the Exchange Management Shell, type each command, pressing Enter after each.

New-Mailbox -PublicFolder -Name PFMB-CompanyEventsNew-Mailbox -PublicFolder -Name PFMB-EuropeNew-Mailbox -PublicFolder -Name PFMB-FinanceNew-Mailbox -PublicFolder -Name PFMB-PublicAffairsNew-Mailbox -PublicFolder -Name PFMB-RedmondNew-Mailbox -PublicFolder -Name PFMB-TailspinToys

o. Verify that the public folders have been created.


Get-Mailbox -PublicFolder5. Create and start the batch migration request.

a. Legacy system public folders such as OWAScratchPad and the schema-root folder subtree in Exchange 2007 will not be recognized by Exchange 2013 and will be treated as bad items, whcih will cause the migration to fail. As part of the migration request, you must specify a value for the BadItemLimit parameter. This value will vary depending on the number of public folder databases you have. The following commands will determine how many public folder databases you have and compute the BadItemLimit for the migration request.

On EX13, in the Exchange Management Shell, type the following, and then press Enter.

$PublicFolderDatabasesInOrg = @(Get-PublicFolderDatabase)


$BadItemLimitCount = 5 + ($PublicFolderDatabasesInOrg.Count -1)


New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX07) -CSVData (Get-Content \\EX07\PFMigration\PFMap_Updated.csv -Encoding Byte) -BadItemLimit $BadItemLimitCount -NotificationEmails [email protected]


Start-MigrationBatch -Identity PFMigratione. In the Exchange Management Shell, type the following, and then press

Enter. Wait until you see the Migration requests appear. Wait approx. 1 minute and you may want to run the cmdlets several times.

Get-PublicFolderMailboxMigrationRequestf. If the Status says “Queued”, type the following, and then press Enter.

Restart-Service MSExchangeMailboxReplicationg. Open Internet Explorer® and browse to https://mail.contoso.com/ecp

h. On the Exchange Admin Center page, sign in as Contoso\Administrator with a password of Pa$$w0rd

i. In the results pane, click the migration tab.

j. On the toolbar, above the migration batch list, click Refresh.

k. Review the new migration batch request created in Exchange Management Shell.

l. Periodically click Refresh until the STATUS of the migration batch reads Synced. This may take 2-5 minutes.

If the status does not update to read Synced, the index may be in a failed and suspended state. From the Exchange Management Shell on EX13, run the following command:

CD C:\Scripts.\FixIndex.ps1It will take several minutes for the index to be updated and become healthy. When it is healthy, the status of the migration batch will update to read Synced.

6. Lock down the public folder on EX07 for final migration.

Until this point in the migration, users have been able to access public folders. The next steps will log users off from the public folders and lock the folders while the migration completes its final synchronization. Users will not be able to access public folders during this process. Also, any mail sent to mail-enabled public folders will be queued and will not be delivered until the public folder migration is complete.


Set-OrganizationConfig -PublicFoldersLockedForMigration $true

b. In the Exchange Management Shell, type the following, and then press Enter

Restart-Service MSExchangeISc. In the Exchange Management Shell, type the following, and then press

Enter.

Get-Service -Name MSExchangeIS -ComputerName EX13 | Restart-ServiceThe Microsoft Exchange Information Store services are being restarted so that the public folder databases pick up the change. Wait for the command to complete.

d. Switch to CL1.

e. On the taskbar, click Outlook 2013.

f. If necessary, under the folder list, click the ellipsis, and then click Folders.

g. In the folder list, expand Public Folders, and then, attempt to expand All Public Folders.

h. Review the Microsoft Outlook dialog box. The public folders have been locked and are not able to be accessed. Click OK.

i. Close Outlook 2013.

7. Finalize the public folder migration.

a. Switch to EX13 and the Exchange admin center.

b. In the migration batch list, click the PFMigration batch.

c. In the details pane, click Complete this migration batch.

d. In the warning dialog box, click yes.

On the toolbar above the migration batch list, periodically click Refresh until the STATUS column readsCompleted. This process may take max. 2 minutes.If the status does not update to read Completed, the index may be in a failed and suspended state. From the Exchange Management Shell on EX13, run the following command:

CD C:\Scripts

.\FixIndex.ps1It will take several minutes for the index to be updated and become healthy. When it is healthy, the status of the migration batch will update to read Completed.

e.

8. Test and unlock the public folder migration.

a. On EX13, in the Exchange admin center, in the feature pane, click public folders.

b. On the toolbar above the public folders list, click Refresh.

Review the list of public folders.

c. Click the public folder mailboxes tab.

Review the public folder mailboxes that were created earlier.

d. Switch to the Exchange Management Shell.

e. In the Exchange Management Shell, type the following, and then press Enter.

Get-PublicFolder -Recurse | ft Identity,ContentMailboxNameReview the output of the command.

f. In the Exchange Management Shell, type the following, and then press Enter.

Set-Mailbox -Identity Administrator -DefaultPublicFolderMailbox PFMB-Hierarchy

g. Switch to CL1.

h. On the taskbar, click Outlook 2013.

i. If necessary, under the folder list, click the ellipsis and then click Folders.

j. In the folder list, expand Public Folders and then expand All Public Folders.

You may have to wait for Outlook to connect to the new public folder mailboxes on Exchange 2013. This process may take several minutes and you may need to close and then reopen Outlook 2013.

k. Expand Public Affairs, and then click NewsRelease-Recent.

l. In the ribbon bar, click New Post.

m. In the new post, in the Subject box, type Hello CEO and then click Post.

n. Verify that the new post was created and then close Outlook 2013.

o. Switch to EX13 and the Exchange Management Shell.

After testing, if the public folder content and hierarchy is acceptable and functions as expected, unlock the public folders for all other users.

p. In the Exchange Management Shell, type the following, and then press Enter.

Get-Mailbox -PublicFolder | Set-Mailbox -PublicFolder -IsExcludedFromServingHierarchy $false

q. Switch to EX07 and the Exchange Management Shell.

r. In the Exchange Management Shell, type the following, and then press Enter.

Set-OrganizationConfig -PublicFolderMigrationComplete $true

s. Switch to EX13 and the Exchange Management Shell.

t. In the Exchange Management Shell, type the following, and then press Enter.

Set-OrganizationConfig -RemotePublicFolderMailboxes $Null -PublicFoldersEnabled Local

9. (Optional) Compare public folder structure, statistics, and permissions.


Get-PublicFolder -Recurse | Export-CliXML C:\LabFiles\PFScripts\Modern_PFStructure.xml


Get-PublicFolderStatistics | Export-CliXML C:\LabFiles\PFScripts\Modern_PFStatistics.xml


Get-PublicFolder -Recurse | Get-PublicFolderClientPermission | Select-Object Identity,User -ExpandProperty AccessRights | Export-CliXML C:\LabFiles\PFScripts\Modern_PFPerms.xml

d. Open File Explorer and browse to C:\LabFiles\PFScripts.

e. In File Explorer, browse to \\EX07\C$\LabFiles\PFScripts.

f. Open and compare each *_PFPerms.xml, *_PFStatistics.xml, and *_PFStructure.xml file.

10. Remove the Public Folder database from Exchange 2007.

a. Switch to EX07 and then open the Exchange Management Console.

b. In the Microsoft Exchange dialog box, click OK to all warning messages.

c. In the console tree, expand Server Configuration, and then click Mailbox.

d. In the work pane, under First Storage Group, double-click Mailbox Database.

e. In the Mailbox Database Properties window, click the Client Settings tab.

f. Next to Offline address book, click Browse.

g. In the Select Offline Address Book window, expand the Name column, click Default Offline Address Book (Ex2013), and then click OK.

h. In the Mailbox Database Properties window, click OK.

i. In the work pane, under Second Storage Group, click Public Folder Database.

j. In the actions pane, under Public Folder Database, click Remove.

k. In the Microsoft Exchange dialog box, click Yes.

l. In the Microsoft Exchange dialog box, review the information, and then click Yes.

m. In the Microsoft Exchange Warning dialog box, review the information and then click OK.

Exercise 3 (Optional): Removing Exchange Server 2007 from the OrganizationIn this exercise, you will uninstall the legacy Exchange Server 2007 from the organization.


EX07

Tasks1. Uninstall Exchange Server 2007.

a. On EX07, in the Exchange Management Console, expand Organization Configuration, and then click Mailbox.

b. In the results pane, click the Offline Address Book tab.

c. Right-click Default Offline Address Book, which is being generated on EX07, and then click Remove.

d. In the Microsoft Exchange dialog box, click Yes.

e. In the console tree, click Recipient Configuration.

f. In the result list, right-click PFProxy, and then click Remove.

g. In the Microsoft Exchange dialog box, click Yes.

h. Close the Exchange Management Console and, if open, close the Exchange Management Shell.

i. Click Start, point to Control Panel, and then click Programs and Features.

j. In Programs and Features, in the programs list, click Microsoft Exchange Server 2007.

k. On the toolbar, click Uninstall.

l. In the Exchange Server 2007 SP3 Setup wizard, on the Exchange Maintenance Mode page, click Next.

m. On the Server Role Selection page, clear the Mailbox Role, Client Access Role, and Hub Transport Role check boxes.

n. Clear the Management Tools check box, and then click Next.

o. On the Readiness Checks page, after the checks complete, click Uninstall.

p. On the Completion page, click Finish.

q. Optionally, you can:

Remove the Exchange database files (*.edb) and storage group log files (*.log).

Remove the setup log files located at %systemdrive%\ExchangeSetupLogs.

Remove the following virtual servers that are created for Exchange 2007 under the Default Web Site in IIS:

o Microsoft-Server-ActiveSync

o OAB

o OWA

exchange migration of legacy public folders to 2013

Documents