• By using this site you agree to the use of cookies for analytics, personalised content and ads.
Servers

Microsoft Exchange 2013 Public Folders Migration Scripts

Language:
English
These scripts are required while migrating Public Folders from Exchange 2010/2007 to O365 Exchange 2013 Public Folders.
  • Note:There are multiple files available for this download.Once you click on the "Download" button, you will be prompted to select the files you need.
    Version:

    15.00.0675.003

    File Name:

    Migration\Export-PublicFolderStatistics.ps1

    Migration\Export-PublicFolderStatistics.strings.psd1

    Migration\PublicFolderToMailboxMapGenerator.ps1

    Migration\PublicFolderToMailboxMapGenerator.strings.psd1

    Date Published:

    09/04/2013

    File Size:

    37 KB

    2 KB

    40 KB

    2 KB

      Use these scripts to migrate public folders from Exchange 2010 or 2007 to Exchange 2013. In order to migrate Exchange 2010 or 2007 Public Folders to Exchange 2013 on O365, we need to analyze the existing Public Folder hierarchy for size to figure out the number of Public Folder mailboxes that are required on O365 and the distribution of folders across mailboxes.
  • Supported Operating System

    Windows Server 2003 Service Pack 2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2

      • Review the Technical Documentation for detailed instructions on performing Public Folder Migration
      • Exchange Server 2010 or Exchange Server 2007 to be installed on the server where the script will be run
      • PowerShell 2.0 or later
    • Script name - Export-PublicFolderStatistics.ps1 Description - This script needs to be run by a local admin on the legacy Exchange server. Run the Export-PublicFolderStatistics.ps1 script to create the folder name-to-folder size mapping file. The output CSV file will contain two columns: FolderName and FolderSize. The values for the FolderSize column will be in displayed bytes. For example, \PublicFolder01,10000. Usage - NOTE - Before running the script, copy the Export-PublicFolderStatistics.strings.psd1 file in the same directory as the Export-PublicFolderStatistics.ps1 script. .\Export-PublicFolderStatistics.ps1 [FQDN of source server] [Folder to size map path] • FQDN of source server equals the fully qualified domain name of the Mailbox server where the public folder hierarchy is hosted. • Folder to size map path equals the file name and path on a network shared folder where you want the CSV file saved. If you specify only the file name, the file will be generated in the current PowerShell directory on the local computer. ------------------------------------------------------------------------------------------------------------------------ Script name - PublicFolderToMailboxMapGenerator.ps1 Description - This script needs to be run by a local admin on the legacy Exchange server. Run the PublicFolderToMailboxMapGenerator.ps1 script to create the public folder-to-mailbox mapping file. This file is used to calculate the correct number of public folder mailboxes required in Exchange Online. Usage - NOTE - Before running the script, copy the PublicFolderToMailboxMapGenerator.strings.psd1 file in the same directory as the PublicFolderToMailboxMapGenerator.ps1 script. .\PublicFolderToMailboxMapGenerator.ps1 [Maximum mailbox size in bytes] [Folder to size map path] [Folder to mailbox map path] • Maximum mailbox size in bytes equals the maximum size you want to set for the new public folder mailboxes. In Exchange Online, the maximum size of public folder mailboxes is 25 GB. • Folder to size map path equals the file path of the CSV file you created when running the Export-PublicFolderStatistics.ps1 script. • Folder To mailbox map path equals the file name and path of the folder-to-mailbox csv file that you’ll create with this step. If you specify only the file name, the file will be generated in the current PowerShell directory on the local computer.

Popular Downloads

Loading your results, please wait...

Free PC updates

  • Security patches
  • Software updates
  • Service packs
  • Hardware drivers

Microsoft suggests

Experience the new and enhanced capabilities.
Try Windows Server 2012 R2
Experience the new and enhanced capabilities.
Free trial