Managing Accessibility of OST files through Cloud-based Platforms

Implementing Cloud-based Platform Migration

Cloud-based migration is a next generation migration option that readily reduces the chances of corruption and makes accessibility of files quite easy. As far as OST files are concerned, they are also preferred to be migrated in the same platform without any worries. Doing so makes them all time available back-up of required files. Moreover, the cloud can be accessed from anywhere at any time and can be even used for bulk migration. 

Thus, the required OST files become safe and handy on few clicks. However, few questions protrude while we think of OST files. It relates to “What happens if OST files get corrupt?” “Will it anyhow affect the existence of PST?” If how, then what will be the concerning factors?

To make the picture clearer it must be clear that the initial focus is to rescue the damaged OST files content and try to keep data hierarchy unchanged without any issues. To be answerable in such unexpected circumstances it is necessary to avail some technical assistance from reliable third-party tool. 

Managing spoilt OST files

There is high probability of getting OST files affected by corruption. However, the severity of OST file corruption is beyond the scope of the topic, but its impetus may somehow put a massive effect on entire file structure. 

Implementing Cloud-based Platform Migration

Cloud-based migration is a next generation migration option that readily reduces the chances of corruption and makes accessibility of files quite easy. As far as OST files are concerned, they are also preferred to be migrated in the same platform without any worries. Doing so makes them all time available back-up of required files. Moreover, the cloud can be accessed from anywhere at any time and can be even used for bulk migration. 

Thus, the required OST files become safe and handy on few clicks. However, few questions protrude while we think of OST files. It relates to “What happens if OST files get corrupt?” “Will it anyhow affect the existence of PST?” If how, then what will be the concerning factors?

To make the picture clearer it must be clear that the initial focus is to rescue the damaged OST files content and try to keep data hierarchy unchanged without any issues. To be answerable in such unexpected circumstances it is necessary to avail some technical assistance from reliable third-party tool. 

Managing spoilt OST files

There is high probability of getting OST files affected by corruption. However, the severity of OST file corruption is beyond the scope of the topic, but its impetus may somehow put a massive effect on entire file structure. 


Figure 1 Dialog Box presenting technical issue.

You must be introduced to the dialog box that displays the inaccessibility information. It is not the single note; moreover, there are ample of them that convey the same message in other manner. 

However, assistance from third-party proved to be helpful. Kernel for OST to PST is the most convenient and user-enabled third-party tool, which is often recommended for this purpose. This OST to PST tool simply scans for damaged/corrupt OST files and repairs them keeping OST file hierarchy and data structure unchanged. Moreover, the tool provides an option either to directly migrate the OST files to cloud-based platforms or convert same to PST and other file formats like DBX, MBOX, MSG, EML, TXT, RTF, HTML, MHTML, & PDF.

What takes for restructuring lost OST files?

Kernel for OST to PST makes use of inbuilt QFSCI algorithm to regain the lost file structure of OST files, it also includes resurrection of OST files content. So, to restructure the damaged OST files Kernel for OST to PST makes use of few essential steps, which include selection of concerned OST files, their preview post conversion and their migration/conversion as per user’s choice. The entire process is done within few clicks and conversion/migration entirely depends upon user’s choice.

Cloud-based Migration-User’s choice

Being a choice of next generation, cloud-based migration is being effectively used and recommended by many users.  Kernel for OST to PST provides such option in addition to the conventional methods of saving OST files in other formats. The screenshot of the tool clearly shows the effectiveness of the tool in handling the OST data in conventional process and cloud-based migration that involves email servers, webmails and Office 365.



Figure 2 Screenshot of Kernel for OST to PST presenting different options.


About Kernel for OST to PST

Kernel Data Recovery has designed a more secure way than conventional methods that were quite risky and time consuming. A more dedicated tool – Kernel for OST to PST has been crafted for this purpose. Kernel for OST to PST uses a secure way to convert OST files to other file format. Thus, it brings a clear picture to the user that OST files can be saved in other formats as well with same dedication and precision as it does for PST file format. Even if the obtained files are large in size, then it can be split in required size. For lost OST files Kernel for OST to PST provides ‘Search’ option. The ‘Preview’ option lets user to make sure that entire conversion has been perfectly taken place. This option provides preview of converted items. 

With the below mentioned descriptive figure you can understand the exact functioning of the tool. 


Figure3.Making file selection and uploading.


Figure4.Details of concerned files and different saving option.


Figure5. Saving Path of desired file.

For perfect conversion process to initiate, the user system must have Pentium class processor, minimum 64 MB RAM, 50 MB space for software installation and some space to save results. The tool supports all versions of MS Exchange Server, MS Outlook, Outlook Express, Windows Server and Windows OS. 

Securing OST files-An Ultimate Aim

For secure OST migration to cloud-based platforms it is recommended to take assistance from reliable third-party tool like Kernel for OST to PST. Due to provision of secure migration and conversion, this tool is highly advised. Since cloud-based migration provides effective and convenient access to OST files; therefore, it is regarded as future cloud for MS Outlook users.

You could download the copy from the below location

PowerShell Script to copy Exchange GUID from Office 365 to Exchange On-prem User.

When users are been migrated from On-Prem to Office 365 using some third party tool then the on-prem user object’s Exchange GUID gets rested to “00000000-0000-0000-0000-000000000000" . This will cause problem when we need to move back the mailbox to on-prem for some reason.  Below is the code which helps to validate the On-prem users which Exchange GUID and copy back the Exchange GUID properties from Online mailbox to the Exchange On-prem user.

Set-ADServerSettings -ViewEntireForest 1
"Remotemailbox" > c:\temp\myremotemailbox.csv
get-remotemailbox  -resultsize unlimited  | %{
$upn = $_.UserPrincipalName
$proxy = $_.EmailAddresses.ProxyAddressString
$exchGuid = $_.ExchangeGuid

$mailboxlist = @()
$found = $false
    foreach($pro in $Proxy)
        If($pro -like "X500:/o=ExchangeLabs/*")
        $found = $true
    if($found -eq $true)
        $upn >> c:\temp\myremotemailbox.csv
    if($exchGuid -eq "00000000-0000-0000-0000-000000000000")
        $upn >> c:\temp\myremotemailbox.csv

$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session –allowclobber

$csvimport = Import-Csv C:\temp\myremotemailbox.csv
"userprincipalname,legacyExchangeDN,ExchangeGuid" > c:\temp\rmbresult.csv
Foreach($csv in $csvimport)
$rmaibox = $csv.remotemailbox
$mailbox = get-mailbox $rmaibox | select userprincipalname,legacyExchangeDN,ExchangeGuid
$mailbox.userprincipalname + "," + $mailbox.legacyExchangeDN + "," + $mailbox.ExchangeGuid >> c:\temp\rmbresult.csv

remove-PSSession $Session

$finalRM = Import-csv C:\temp\rmbresult.csv
foreach($final in $finalRM)
$upn = $final.userprincipalname
$eguid = $final.ExchangeGuid
$x = "X500:"  +  $final.legacyExchangeDN

if($upn -ne "")
get-remotemailbox $upn | Set-reMotemailbox -exchangeguid $eguid -CustomAttribute3 "Account Verified for X500-GUID" -EmailAddresses @{Add=$x}


Deploying a Free LoadMaster at Your Exchange 2013 lab – Part 1

In this article series, we will understand the step by step instruction to deploy Kemp LoadMaster for Exchange Server 2013 services in multi- site (Dallas and Pittsburg) lab environment and also configure geo-redundancy between the two AD sites. Where the Kemp LoadMaster load balances the client requests( from internal and internet network) within the AD site and also routes the client request automatically to the available Exchange 2013 servers in other site when one AD site goes down.

Current LAB Setup

Current Lab is built on Microsoft Hyper-V and it is configured with two AD sites Dallas ( network) and Pittsburg ( network). It is also installed with domain controller on each site with the domain name In each of the AD site, one Exchange Server 2013 (multirole) is installed and configured Database Availability Group (DAG01) between them. Below Figure 1.1 has the details of the AD sites, Domain Controller, Exchange nodes and DAG.


Figure 1.1 Exchange 2013 deployed in the lab environment.


LAB Hyper-V Virtual Network Configuration Requirement:

LoadMaster interfaces with both internal network and external/internet network. Hence, Hyper-V needs to configure with two Virtual networks: DMZ Network and Internal Network.

1. DMZ Network: Create a new DMZ Network virtual network of type External network, it should connect to the host Machine network interface card (NIC) and communicates with the external world. Make sure to select Allow management operation system to share this network adapter. The Figure 1.2 has the details of the same. Host machine NIC should be connected to the internet.


Figure 1.2 DMZ Network configuration

2. Internal Network: Create new Internal Network virtual network of type Internal Network. Internal network is isolated network which can communicate within themselves. We will configure all Exchange Servers 2013 guest machines NICs to use internal network.


Figure 1.3 Hyper-V Internal Network Configuration.

A Windows VM is configured as Router with two NICs pointing to internal network. This windows Router will route traffic between two network segment Dallas (10.10.10.x) and Pittsburg (20.20.20.x) within the internal network.

Configuring Kemp LoadMaster in the Exchange 2013 lab

In this part , we will Install and configure LoadMaster on both the AD site in Two-Arm Deployment as defined in the below Figure 1.4. With one NIC pointing the DMZ network and other NIC pointing to the internal network.


Figure 1.4 Kemp LoadMaster deployment and IP address configuration plan

Configuring LoadMaster for Dallas Network

1. Register a new Kemp ID at and download the latest version of Free Kemp loadmaster for Hyper-V


Figure 1.5 Free Kemp LoadMaster Website

2. Extract the KEMP LoadMaster Virtual Machine (VM) file on the Hyper-V server.

3. Start Hyper-V Manager and click on Import VM from the Actions menu then click on Next at the Welcome Screen.


Figure 1.6 Importing LoadMaster Virtual Machine into Hyper-V

4. At Local Folder page, Click on Browse button to specify the Kemp LoadMaster virtual machine and click Next and on Select Virtual Machine page keep the settings as default and click on Next


Figure 1.7 Specify the Folder containing virtual machine to import

5. Choose the option Copy the Virtual Machine (create a unique ID) to make of copy of the VM with the new unique ID and click Next. (This will help us to create multiple copy of the downloaded LoadMaster image)


Figure 1.8 Choose the virtual machine Import type

6. Choose folders paths to store the new copy of the LoadMaster VM and click Next.


Figure 1.9 Choose Virtual Machines files path

7. Then Choose Storage folders path for the new VM and click Next

8. Validate the Summary page and click on Finish to import the Virtual Machine (VM) into Hyper-V console.


Figure 1.10 Completing Import Wizard.

9. To identify the Dallas Load Master in the Hyper-V, rename the newly imported LoadMaster VM to DalKemp.


Figure 1.11 Renaming LoadMaster VM in Hyper-V Manager

10. To configure the virtual network on the DalKemp VM, right click on LoadMaster VM and select Settings. Select DMZ Network for the first VM-Bus network Adapter and Internal Network for the second VM-Bus network adapter and click on Apply. Below Figure 1.12 has the reference details.


Figure 1.12 Configure Network Adapter on DalKemp VM

Connecting to LoadMaster and Activating Free License

1. Boot the DalKemp LoadMaster VM from Hyper-V console

2. Post booting it displays IP Address of the Appliance (in our case it is It is been assigned by the LAB router via External DMZ network. Since, this network is sharing the host NIC and also connected to the Lab router with DHCP Configured.

Note: The Default Username/Password: bal /1fourall


Figure 1.13 DalKemp LoadMaster connection information.

3. To configure the DalKemp LoadMaster, start Internet Explorer and connect to it using the IP address assigned –

4. Provide the Default credentials Username/Password: bal /1fourall

5. Click on Agree to accept the End User Agreement


Figure 1.14 Accepting EULA

6. Select License Type as Free LoadMaster and click on Allow to connect back to KEMP home for license activation.


Figure 1.15 Selecting License Type

7. Use the registered KEMP ID and activate free LoadMaster license.


Figure 1.16 Activating Free LoadMaster License

8. Once activated, it will prompt to reset the default user (bal) password. Once password is changed then re-login back to the VM using new password.

Configuring LoadMaster Network Interface

1. Login to Kemp LoadMaster from Internet Explorer and under Main menu expand system configuration -> interface

2. Select eth0 (Network Interface 0) and validate IP Address – It is been assigned by DHCP and we could use the same on the interface and change it if required. Make sure Use for GEO Responses and Request is checked and this interface will be used to communicate with Pittsburg LoadMaster for geo redundancy.


Figure 1.17 Configuring LoadMaster eth0 Interface

3. Select eth1 (network Interface 1) and assign the IP address from the Dallas internal network segment and click on Set Address. This interface will be used to communicate with internal Exchange 2013 servers in the Dallas and Pittsburg AD sites.


Figure 1.18 Configuring LoadMaster eth1 Interface

Follow the above Instructions: Configuring LoadMaster for Dallas Network, Connecting to LoadMaster and Activating Free License, Configuring LoadMaster Network Interface to import and configure Pittsburg LoadMaster. Configure interface Eth0 with IP address (Pittsburg DMZ network) and Eth1 with (Pittsburg internal network) on it.

With this we are at the end of the part 1 of the article service with Exchange server 2013 installed and configured, Hyper-V networks configured and finally installed and configured LoadMaster in both the AD site. In the next part we will configure the LoadMaster for the Exchange HTTPS/ SMTP Services and validate the same.

Configuring Outlook Anywhere via ARR on IIS 7

If you are trying to configure Outlook Anywhere to route via ARR sever on IIS 7 then you will not be able to connect and you should get error “outlook unable to connect to the Exchange sever.”

in IIS logs you should find the error code 404.13 (which mean content length is too large)


By Default IIS ‘Maximum allow content length’ is set to 30 MB. We just have to reset it to 2 GB(2147483648 byes).

To configure this select the required website and double click  on ‘Request Filtering’


Select ‘Headers’ tab and click on ‘Edit Feature Settings’ then increase the ‘Maximum allow content length’ to 1 GB (1073741824 bytes)


Deploying Microsoft Exchange e-mail Server – Guides, books and Admin deployment documents

Top 5 Microsoft Exchange Server Books by MVPs, Consultants and Expert Administrators

I’ve compiled a list of some of my favorite Microsoft Exchange authors into the top list of books covering

· Deployment

· Architecture

· Configuration

· Deployment

· Sizing

· Load Balancing

1 – Microsoft Exchange Server 2013 Sizing, Designing and Configuration – A Practical Look – 9.99$

By Krishna Kumar

It’s a book on Microsoft Exchange Server 2013, it will be on sizing, designing and configuring with a practical look. It will be based on the practical scenario for different organization with approximately user of 5,000, 10,000, 25,000 and 50,000. It also contain various migration scenario like migration from Exchange 2003, Exchange 2007 and Exchange 2010. It also includes information on Office 365 migration scenario with Exchange 2013.

Copy of the book can be bought from Amazon

2 – Exam Ref 70-341 Core Solutions of Microsoft Exchange Server 2013 (MCSE) 1st Edition – 35.51$

By Bhargav Shukla, Paul Robichaux

Prepare for Microsoft Exam 70-341–and help demonstrate your real-world mastery of the skills needed to deliver effective Microsoft Exchange Server 2013 solutions. Designed for experienced IT pros ready to advance their status, Exam Ref focuses on the critical-thinking and decision-making acumen needed for success at the MCSE level.

Copy of the book can be bought from Amazon

3- Mastering Microsoft Exchange Server 2013 – 35.23$

By David Elfassy

Microsoft Exchange Server 2013 is touted as a solution for lowering the total cost of ownership, whether deployed on-premises or in the cloud. Like the earlier editions, this comprehensive guide covers every aspect of installing, configuring, and managing this multifaceted collaboration system. It offers Windows systems administrators and consultants a complete tutorial and reference, ideal for anyone installing Exchange Server for the first time or those migrating from an earlier Exchange Server version.

Mastering Microsoft Exchange Server 2013 is the complete reference for planning, installing, and maintaining the most popular e-mail server product available.

Copy of the book can be bought from Amazon

4- Microsoft Exchange Server 2013 Unleashed – 35.70$

By Rand Morimoto, Michael Noel, Guy Yardeni , Chris Amaris and Andrew Abbate

Microsoft Exchange Server 2013 doesn’t just add dozens of new features: It integrates multiple technologies into a common, unified communications system that can add value in many new ways. Now, five leading Exchange Server consultants help you deploy Exchange Server 2013 quickly and smoothly–and then efficiently manage, troubleshoot, and support it for years to come. More than a comprehensive, authoritative reference, Microsoft Exchange Server 2013 Unleashed presents hundreds of helpful tips and tricks based on the authors’ unsurpassed early adopter experience with Exchange Server 2013 in real production environments.

Copy of the book can be bought from Amazon

5- Microsoft Exchange Server 2013: Design, Deploy and Deliver an Enterprise Messaging Solution – 37.72$

By Nathan Winters, Neil Johnson, Nicolas Blank

The latest release of Microsoft’s messaging system allows for easier access to e-mail, voicemail, and calendars from a variety of devices and any location while also giving users more control and freeing up administrators to perform more critical tasks. This innovative new field guide starts with key concepts of Microsoft Exchange Server 2013 and then moves through the recommended practices and processes that are necessary to deploy a top-quality Exchange service.

  • Focuses on the Exchange ecosystem rather than just the features and functions of the Exchange product
  • Focuses on scenarios facing real customers and explains how problems can be solved and requirements met
  • Zooms in on both on-premises deployments as well as Exchange Online cloud deployments with Office 365
  • Helps you thoroughly master the new version with step-by-step instruction on how to install, configure, and manage this multifaceted collaboration system

Whether you’re upgrading from Exchange Server 2010 or earlier, installing for the first time, or migrating from another system, this step-by-step guide provides the hands-on instruction, practical application, and real-world advice you need.

Copy of the book can be bought from Amazon

RecoveryFix for Exchange Server Recovery

One of the most important component of the Exchange server is the database and it stores the user’s mailbox with emails, contacts, calendar, tasks, notes etc.

MS Exchange is considered as mission critical application as most of the business transaction happens over email. Hence, it is very important that the database are protected. Exchange server provides multiple native option to protect the database. Exchange backups, multiple database copy, LAG database copy are the common ways to protect database with minimum or no data loss.

In spite of multiple options and complex configuration, there is always a possibility of exchange database getting corrupt and cause a major downtime for the users with data loss. Exchange native tool ‘ESEUTIL’ could be used to fix the database corruption, but in most of the occasions, it take enormous amount of time to fix the corruption. Alternatively, you could restore data from the backups but it is subjected to data loss between the backup time and the restore time.

Lepide software Pvt. Ltd. offers RecoveryFix for Exchange Server Recovery tool, it helps to recover Exchange database from corruption. It works on all version of Exchange database file starting from Exchange 5.5 to latest version of Exchange. It is a very simple, easy and efficient tool.

RecoveryFix for Exchange Server Recovery tool accepts the database file .edb and .stm (for legacy database only) as source files.



Image: Selecting Corrupted database to recover


Operating the software, once the source database file is selected then it provides three different recovery mode options:

1. Automatic Analyze and recover: It is the recommended and fastest mode to restore the corrupted database. It scans through the database, fixes the corruption and lists all the recovered mailboxes in the database. Recovered mailboxes from the database can be exported to the .pst files.

2. Advance Scan: It is selected when database is severely corrupted and ‘Automatic Analyze and Recover’ option fails. This mode performs deep scanning of the database and it takes some time to recover the database. Once the database is fixed, it lists all the recovered mailboxes in the database. Recovered mailboxes from the database can be exported to the .pst files.

3. Rebuild corrupted database: This option reduces unnecessary efforts of exporting the user’s mailbox to .pst file and sharing with the users. It creates/rebuilds a new clean database by fixing the corruption in the database. The new recovered database is ready to mount on the Exchange servers.



Image: Recovery Modes to Recover Corrupted Database


Automatic analyze and recover and Advanced scan are the most common options, when you have bigger database and large number of mailboxes to recover. Once scanning process is done, it proves effective in fixing all the corruption and allows administrator to view/validate the mailboxes and its content.


Image: RecoveryFix for Exchange Server Console

Administrator can save all the recovered mailboxes into .pst file format. These .pst files can be imported into the target user’s mailbox or any other temp mailbox. Administrators can also share the .pst with users and can be accessed through their MS Outlook.

Saving the recovered mailboxes can be done easily by selecting ‘Save’ button from the top ribbon bar. Saving option provides some great flexibility to filter only the necessary emails based on date.

Administrator can easily filter emails based on predefined date or custom date. Finally at the end, one just got to define the path of the destination folder to save the recovered .pst files.



Image: Saving Option to export the .pst



I think it’s a great tool to fix the corrupted Exchange database and at the same time can save your efforts and time. I recommend this tool for all the Exchange Server administrators. You can download the copy of the software from the Recoveryfix Website –

LepideMigrator for Exchange (LME)

Exchange migration involves a lot of effort and time; it is one of the most complex migrations to perform. After doing tons of exchange migration, I realized that not every environment is the same and not every migration is the same. During an exchange migration, everyone’s mailbox will be moved from one version of Exchange to the latest version or to the other organization. With the upgrade of Exchange servers, it is important that client outlook version is also upgraded to the latest level or to the level of Exchange servers. Thus, in a way everyone has to undergo some kind of changes with learning, while adopting a new Exchange environment into the organization.

LepideMigrator for Exchange (LME) is the new latest Exchange migration tool from Lepide which helps in performing a migration from one Exchange Environment to another which is either located locally or another network or even in the Office 365 or Exchange hosted solution in the cloud environment. It supports different migration scenarios, like

· Exchange 2003 / 2007 and Exchange 2010

· Exchange 2003 / 2007 and Exchange 2013

· Exchange 2010 and Exchange 2013

· Migration from any Exchange Server to Office 365

· Public Folder Migration

· Intra-forest Exchange Migration

· Cross-forest Exchange Migration

Given below are a few interesting features of the products.

1. Innovative technique to migrate the large number of mailboxes from source Exchange server to the target which enhances the performance. It can be installed on multiple computers and increase migration volume depending on the requirement. We can also schedule the mailbox move by creating schedule jobs. It provides rich filtering options to filter unwanted email and migrate only necessary email to the target and can also provide the option to undo or rollback the mailbox migration, if necessary.

2. Exchange migration is a time-consuming process which needs a lot of effort and time. To reduce the migration efforts, we can sync the complete source mailbox to the target much ahead of time and just do an incremental sync only before the final cutover. This helps in avoiding any kind of data loss and outage to the users.

3. Report is very important for the migration and helps in tracking migration history and plan for the future migration. Notification helps administrator to notify the status of the migration status with email alerts for the job status, job completion, or job cancelation.

Migrations of the mailbox using LepideMigrator for Exchange is a very easy process and let’s understand on how easy it is to configure and to migrate a mailbox from one forest to another.

Given below is the Setup of my lab

1. Source forest

2. Target Forest

3. Creating DNS forwarding and trust between and

Given below is a step-by-step instruction to perform cross forest migration.

1. Install LepideMigrator for Exchange at the source or target forest. In this scenario, the tool is installed on the source forest It is installed on the Windows 7 machine with outlook client installed

2. To perform the configuration, start the LepideMigrator for Exchange, Right click on All projects -> click on ‘Add Project’ -> provide the name to the Mailbox migration project


3. Then, create the new Job for the mailbox migration and provide the name for the same and click on ‘Next’


4. Connect to the source forest domain control by providing the IP address and administrator credentials. Then click on ‘Next’


5. Select all the necessary required users to migrate into the target domain and click on ‘Next’


6. Input the target domain controller IP address and the admin credentials. Make sure to specify ‘Different Domain’ for cross forest migration scenario and then click ‘Next’. You can also pull down ‘Migrate To’ to select the different options like same domain or office 365.


7. It also provides the filters to include or exclude the message based on date and folder. Click on ‘Next’ to continue


8. Here, we need to map the source mailbox with the target forest mailbox. It provides the option to map the source mailbox to target pre-created mailbox automatically. If not, we could provide the CSV file specifying the source and target mailbox mapping.


9. Another option could also be to create the target mailbox using the tool itself. Select all the source mailbox and click on message icon, then click on ‘Start’.


10. Once the target mailbox is created, then you could see the mapping done automatically for each of the source mailbox with the target. Click on ‘Next’ to continue.


11. Specify option to Skip the Bad item count or if you just want to do only the mailbox content synchronization, and then click on ‘Next’.


12. Specify the email address to receive various notifications for Job start, Job stop, Job completion, mailbox migration start / finish etc.


13. Notification configuration needs the SMTP address and other necessary configurations. Please provide the same and continue with the ‘Next’.


14. Specify the time duration to deny or permit the migration for the specific time period. It is important to make sure that migration is not done at the production hours, which could have the user performance impact. Click on ‘Next’ to continue.


15. Then schedule the migration depending on the requirement and click on ‘Next.


16. Finally, verify the summary details and click on ‘Finish’ to complete the Job creation.


17. It’s now the time to generate the license file and upload it to It generates the generate activation file, download the import it to activate the same.


18. Once the license is activated, we are ready to start the mailbox migration by right clicking on the Job and select the option ‘Start Job’.

Report Console

1. Report console helps to generate the migration statistics report. It helps to analyze the migration details and also to track the status. This report has the complete statistics of the migration performed using the server. It has details of number of jobs, with the domain details and the Exchange version specifications.

To start the report console

2. Start the LepideMigrator for Exchange

3. Click on tool -> click on Report Console


4. Login with the account and password as ‘lepadmin’


5. To understand the details of each of the migration job, click on the Job name. It gets the detailed information with number of mailboxes, total folders, migrated messages and status. Below is the reference screen shot.


6. You could also generate some quick reports in html or pdf file using the options available in the bottom left corner of the LepideMigrator for Exchange tool.



This migration could take some time depending upon factors like the size of the source mailbox, bandwidth, source and target server performance, etc. Migration using a ‘LepideMigrator for Exchange’ is much simpler to configure and manage than a native migration tool. It provides option to migrate the account with SID History and also copy the password from the source to target account, which is very important for the cross forest migration scenario. It also provides option to migrate public folders and also apply the settings like mailbox rights, send as permission, public folder administration rights send on behalf, message delivery restriction, and public folder client permission.

I believe, LepideMigrator for Exchange is a compressive tool to perform migration under various scenario. This tool has all the features to perform end to end migration.

You can find the detailed information about the tool at and  also download the trial version from