In modern world where nothing is possible without emails, Microsoft Outlook is an undisputed king when it comes to online communication. For emailing, Outlook is the first choice of every user. We are very well aware of Outlook email client. Well, your favorite Outlook is more than just an email client. It is your personal information manager which contains features more than just emailing, such as task manager, calendar, notes, journal, contacts, and browsing. Outlook is the important part of Microsoft Office, a well-known MS Office suite. It also comes as another application.
It is used widely as a standalone application for emailing. It is commonly used with Exchange Server in large enterprises and organizations for multiple workstations. With Microsoft Exchange Server, one can share mailbox data with each other. Users can also work offline in MS Outlook if internet is not available. It creates copy of its mailbox data on local system, known as Outlook Storage Table (OST). If you are not connected to server, it stores mailbox items in a data file, Personal Storage Table (PST).
Why You Should Convert OST into PST?
It often becomes important to convert OST data into PST. Here are some of the common reasons –
- Mailbox goes inaccessible because of Exchange Server crash. Though you can work in offline mode with OST file, it is not possible to sync with Exchange Server. If you urgently have to access mailbox to make changes, you can convert OST file into PST.
- Regular maintenance needs for Exchange Server are another reason. During the process, you cannot use Exchange Server. It often becomes important to access mailbox which cannot be possible for the maintenance of Exchange Server. To access mailbox items, you can import file into MS Outlook.
- If you switch from one organization, you have to convert OST into PST. Your Outlook account is connected to your company’s server. After few months, you have to resign from the company to join another one. Since you left your company, the administrator has deleted your account. Though you have OST data, you cannot use them without having connection to Exchange Server. In that case, it is better to convert your OST files into PST format to continue using your old data.
- If your important data has recently been removed, you can recover them only with OST to PST conversion.
- Corruption is another major reason behind OST to PST conversion. No OST repair tool is reliable that comes for free in the market to repair your corrupt OST files. So, you have to convert OST to PST files.
Converting OST to PST File Manually – Step by Step Guide
Outlook has Import & Export feature which is known to be the ideal way to export mailbox items.
- On the top of MS Outlook, click File menu, then “Open” and go to “Import”
- When “Import and Export Wizard” is opened, choose “Export to a file”. Then click “Next”.
- Choose “Outlook Data File” in the list and click “Next”
- Choose mailbox folder to export. You can also add subfolders.
- Now you have to define location to save new PST file. Click “Finish” to start process
Within few minutes, process is done.
If you still not able to do this, you can use a third party application like OST to PST Converter tool. There is no technical skill is required to access this application. This tool not only convert ost to pst file as well as recover deleted emails. Go through a Free trial version and use it. Free trial version will show you the preview of converted data. If you feel that tool is working for your then you need to purchase the full version license.
Now a Days Microsoft Exchange Server is the most usable emailing server as compare to other email server. From last two decade Microsoft updated their Exchange Server version from Exchange Server 4.0 to Exchange Server 2013. Every updated version has some new features. So, all organization wants to use the latest version of MS Exchange Server version. The latest updated version helps to improve the performance of our email account.
Here we will guide you, step by step how to Migrate Mailbox from One Exchange Server to Another Exchange Server. But before discuss the procedure of Exchange Server Migration; we’ll know the features of MS Exchange 2010 over 2003, and the key reasons why we do need to migrate the Public Folders of Exchange Server 2003 to 2010.
So first we start with its features, let’s check it-
Features of MS Exchange 2003:
This version of Microsoft Exchange has enhanced disaster recovery, and letting administrators to bring server online rapidly.
This version has the ability to drop inbound e-mail before being fully processed.
Exchange 2003 has enhanced message and mailbox management tools.
It has also added several basic filtering methods such as Intelligent Message filter, Sender ID filtering, Connection filtering, and Recipient filtering.
Features of MS Exchange 2010:
MS Exchange 2010 has many new features like:
DAG(Database Availability Group) which provides database level high availability and accessibility.
CAS(Client Access Server) availability is provided by using CAS arrays.
RPC Client Access, this service facilitates all Outlook clients to access their mailbox database.
Personal Archive feature is available.
Exchange Server 2010 has also added ‘Shadow Redundancy’ feature which protects e-mails messages while they are in transit.
Here are some common reasons when we need to do the migration of public folders in Exchange Server –
- First, sometime it can be seen that clients Outlook versions are not upgraded. So the Outlook 2003 and previous versions require a Public Folder database for storing and distributing the data.
- Secondly, some third party applications require public folders to work.
So, to fix the limitations of previous Outlook versions, we migrate public folders in Exchange Server. Here is the method to migrate private folders which is divided into two steps,
- Copying Exchange 2003 public folders to Exchange 2010, and
- Moving Exchange 2003 public folders to Exchange Server 2010.
Step 1 : Firstly, copy Exchange 2003 Public Folders to Exchange 2010, then
Add the Exchange 2010 server as Public Folder in collaboration with Exchange 2003 server Public Folders and execute the following command:
From the Exchange 2010 server: .\AddReplicaToPFRecursive.ps1 -server “Exchange 2010 Server” -TopPublicFolder “\” -ServerToAdd “Exchange 2010 Server”
# If you want to migrate multiple public folders into MS Exchange 2010 server. Then repeat the above command to all of them.
Now, by using the Exchange 2003 System Manager, copy the Exchange 2003 Public Folder hierarchy & content to Exchange 2010 server. And then execute the following command:
From the Exchange 2010 server: Update-PublicFolderHierarchy -Server “Exchange 2010 Server”
Step 2 : Now move all replicas from Exchange 2003 to Exchange 2010 through “move all replicas” which actually eliminate the Exchange 2003 replicas.
To move all Exchange 2003 replicas to Exchange 2010, this will essentially eliminate the Exchange 2003 replicas. Execute the following command:
From the Exchange 2010 server: .\MoveAllReplicas.ps1 -Server “Exchange 2003 Server” -NewServer “Exchange 2010 Server”
However, in some drastic situation if you find that the migration of public folders between the Exchange 2003 and 2010 is not possible, it may be due to the corruption or damage of public folders. To get rid of this situation, a third party software can be used to prevent the data lose. Here to see the most prominent Exchange recovery software which not only recover Exchange user’s mailbox & data but also repair damaged EDB files and corrupted Mailboxes. You just try the Free Version to Get the Results.