Friday, 21 October 2016

How to Export Exchange 2016 Mailbox to PST

Some of my blog readers have asked the question how to export and import Exchange 2016 mailboxes to PST. So I decide to post quick way to do it.  Users want to export Exchange EDB mailboxes to Outlook PST for many reasons, some for Exchange backup, some for relocate to different organization etc.
Note: You can use either Third Party EDB to PST Converter or Powershell Command or EAC to import Exchange Mailbox to PST. PowerShell and EAC are time consuming and require an in-depth knowledge of cmdlets. These procedure also disturb the ongoing process of Exchange Server. In following case Third Party EDB to PST is best suited for you!!

Here are all steps How to use Exchange Management Shell & EAC to export Exchange mailbox to a PST quickly and efficiently.

By default, not all users can export Mailboxes to PST files. For using Exchange Poweshell Commands & EAC, first you have to grant permission Mailbox Import Export role to the group that the account you’ll be performing the import/export action with. After making this change, you have to logon again to the Exchange server to activate user role changes. You have to grant the following permission, where you want to import and export PST files:

•    For import PST files : Read permission

•    For export PST files: Read/Write permission

Let’s start with EAC:

Now click on Permissions –> admin roles
Open the properties of the group to assign the Mailbox Import Export permissions.
Roles>>Mailbox Import Export role:
Now Add the role:
Now log out of the EAC then navigate to recipients –> mailboxes, right click on a user’s mailbox and now you will see the options: Export to a PST file
Note: If you don't grant permission, you will receive an error that Exchange server is unable to establish a connection to the PST.
Exchange Management Shell
To assign this role to a user, you can use the New-ManagementRoleAssignment command:

New-ManagementRoleAssignment –Role "Mailbox Import Export" –User "<user name>”
If you want to assign the Mailbox Import Export role to the Administrator account, use following command:

New-ManagementRoleAssignment –Role "Mailbox Import Export" –User "Administrator"

Now logon again to the Exchange server to activate this change.

After logging on again, go to PowerShell and execute the following command:  

New-MailboxExportRequest -Mailbox <user> -FilePath \\<server ABCD>\<shared folder name>\<PST name>.pst

The export request will be queued, and the MRS (Mailbox Replication Service) will pick up the request and start exporting the Mailbox to a PST file.

You can create more than one mailbox export request per mailbox, and each mailbox export request must have a unique name.

By default, Exchange Server generates up to 10 unique names for a mailbox export request. If you want to create more than 10 export requests, you need to specify a unique name.

Third Party Tools:  

If you want a simpler way to export Exchange 2016 mailboxes to pst file, you can use Stellar EDB to PST Converter to export online as well as offline Exchange mailbox to PST. 

The advantages of Stellar EDB to PST Converter Software are:

•    Convert all mail components of EDB file to PST
•    Can Convert multiple EDB files as well as Archive mailboxes to PST
•    Convert EDB file to Live Exchange Server and Office 365
•    Can save EDB file in five other file formats: EML, MSG, RTF, PDF, & HTML
•    Supports all version of MS Exchange.
•    conversion EDB file of any language to PST
•    Also recover accidentally deleted EDB file

PowerShell is time consuming and requires in-depth knowledge of Poweshell Commands. If you are not aware of these commands, there are also the Risk of data loss. If you’re looking for a simpler way to export mailboxes, then solution Stellar EDB to PST converter is best suited to you!!
Thursday, 13 October 2016

How to repair corrupt database in Exchange 2016


As we all know sometimes Exchange users noticed corruption issues with Exchange Server 2016 like database process terminate unexpectedly, users unable to access their mailbox data, corruption also cause database switchover and failover problem etc. As a remedy, there are various options available to fix corruption like PowerShell commands, third party tools, Restore from backup etc. You can face following scenarios if your database get corrupt: 

•    Exchange Information Store Service is not start
•    Missing Exchange database files(edb)
•    Database shows in “Dirty Shutdown” state
•    No free disk space on database 
•    While database is in Clean Shutdown state, significant logical corruption exists causing the database to dismount.
Let’s have a look of different methodologies:

Backup Available: Restore the Exchange database from backup
Exchange Server provides a plug-in for Windows Server Backup to backup of Exchange data. If you have updated Windows Server Backup use following steps to restore your database:
First Start Windows Server Backup>>Local Backup.
Now click Recover… to start the Recovery Wizard.
Select one of the following step:

•    If back up is on the local server, select ServerName>> Next.
•    If backup is on another server/computer, select Another server>>Next
•    Now ‘Specify location type page. If select Local drives>select the drive containing the backup on the Select backup location page>>Next.
•    If Select Remote shared folder, and then click Next. Enter the UNC path for the backup data on the Specify remote folder page, and Next.
Now Select Backup Date page will open, select date and time from here>>then Next.
On the Select Recovery Type page, select Applications, and then click Next.
On the Select Application page, verify that Exchange is selected in the Applications field.
Note: Also check the application components of the backups from “View Details” options. If you have most recent backup then don’t use option of roll-forward recovery of the application database.

From this option Specify Recovery Options page, specify where you want to recover the data, and then click Next: There are two recovery operations available: 

•    Recover to original location Use this option to restore the Exchange data original location.
•    Recover to another location Use this option restore individual databases to specified location Browse to specify the location. 

After completion of restore process, manually moved data files back to their original location, or mounted somewhere else in the Exchange organization. When you restore a database to another location, you will notice that the restored Exchange database will be in a dirty shutdown state. After the completion of restore process, you will need to manually put the database into a clean shutdown state by using Eseutil.exe.
On Confirmation page, review the recovery settings, and then click Recover.
On the Recovery Progress page, you can view the status and progress of the recovery operation.
Click Close after completion of recovery process.

If No Backup Available: If you have updated backup, you can easily restore the Exchange 2016 database using Windows Server Backup. But that may not be the case always. If you don’t have backup or backup is available but is get corrupt. In this case, database cannot be recovered through Windows Server Backup. You can use New-MailboxRepairRequest command to recover corrupt database.


This command use to detect & repair mailbox corruptions. You can repair a specific mailbox or a full database using this command. This command detects and fixes the following types of mailbox corruptions:

•    Search folder corruptions 
•    Aggregate counts (reflect incorrect values)- (AggregateCounts)
•    Folder views (returning incorrect contents)- (FolderView)
•    Provisioned folders(incorrectly pointing to parent folders- (ProvisionedFolder)

Parameter 1: 
This Parameter use to detect and repair all folder views for the mailbox
New-MailboxRepairRequest -Mailbox -CorruptionType FolderView

Parameter 2:

This Parameter use to detect and report on ProvisionedFolder and SearchFolder corruption
New-MailboxRepairRequest -Mailbox xyz -CorruptionType ProvisionedFolder,SearchFolder -DetectOnly

Parameter 3:

This Parameter use to detect and repair AggregateCounts for all mailboxes on mailbox database XYZ-DB01.
New-MailboxRepairRequest -Database XYZ-DB01 -CorruptionType AggregateCounts

Parameter 4: 
This Parameter use to detect and repair all corruption types mailbox and archive.
New-MailboxRepairRequest -Mailbox xyz -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview -Archive

Parameter 5: 
This Parameter creates a variable that identifies xyz mailbox and then uses the variable to specify the values for the Database and StoreMailbox parameters to create a request to detect and repair all corruption types.
$Mailbox = Get-MailboxStatistics xyz
New-MailboxRepairRequest -Database $Mailbox.Database -StoreMailbox $Mailbox.MailboxGuid -CorruptionType

Many more parameters are available, check it from here:

Third Party Tools
This cmdlet takes a quite long time to repair corrupt Exchange database. There are many third party tools available online that speeds up repair process and doesn’t affect Exchange databases availability. Stellar Phoenix Mailbox Exchange Recovery is one of the finest tool to repair corrupt Exchange server database. The software also export recovered edb files to a Live Exchange server. The software supports MS Exchange Server 2016, 2013, 2010, 2007, 2003 etc.
Remember that if you perform recovery on different version of Exchange database like 2013, 2010 then the steps will be different. Please ensure that you know what you are doing.
Sunday, 17 July 2016

Recovering items deleted from Public Folders in Exchange 2013

Public folders are the feature of Exchange server which is used to share mailbox and related folders with others Exchange server users within the organization. The key purpose of the public folder to take advantage of high availability of data, so that a user or selected users in a group can access the folder on the same network who are using the same email client. 
Thursday, 16 June 2016

How to Export Lotus Notes Mail Items to Outlook PST

Microsoft's email client Outlook is an easiest way for email communication which comes with the ability to provide high end data security along with simple interface that make it the most popular email client across the globe. This write-up is for Lotus Notes users who are looking to migrate their Lotus notes mails to Outlook. In order access NSF file data into Outlook, initially you need to convert NSF file format into PST format, as due to different file structure NSF files doesn’t open into Outlook.
Tuesday, 31 May 2016

Restore Exchange 2016 Mailboxes with "New-MailboxRestoreRequest"

There are several ways to restore mailboxes (soft-deleted, disabled or disconnected) in Exchange server 2016. Either you can restore mailbox using Windows server backup, with recovery database,  or using Exchange server cmdlets New-MailboxRestoreRequest.
Wednesday, 18 May 2016

How to Perform On-Premises Exchange to Office 365 Migration

With the world moving towards the cloud revolution, many organizations are stuck at the Exchange vs Office 365 decision. For any company, migrating thousands of mailboxes (with loads of data accumulated over the years) from on-premises email setup to a cloud based environment is no cakewalk. There are technical aspects to be dealt with, management aspects, cost frontiers and the need of experts in the area. Losing a little information during the process is just not an option.

Thursday, 7 April 2016

How to Resolve Error "Outlook.ost is in use and cannot be accessed!"

Exchange account holders who access their mailboxes locally through MS Outlook are pretty well familiar with OST files. An OST file is created automatically when Cached Exchange Mode is turned on.
Wednesday, 30 December 2015

How to Restore Inaccessible Mailboxes From the EDB File, Which Fails to Mount

While working with MS Exchange Server, you need to mount the database file to access the user mailbox folders. There are various users’ mailbox folders, which contains user mailbox items including emails, messages, attachments, notes, journal, tasks, etc. At times, you might fail to mount the exchange folder.
Thursday, 17 December 2015

The Thinking Behind Lotus Notes to MS Exchange Migration

Let me first start by affirming that this post is in no way intentional to convince you to switch Lotus Notes to Exchange. I very well know that the world is divided into two (equivalent?) camps: one for Microsoft Exchange and the other for IBM Lotus Notes. And it appears that they are constantly battling with each other to prove that their particular platform is much better than the other. You can just Google (or Bing) for “Exchange Server vs. IBM Lotus Notes” and you will be surprised to know some of the interesting facts about these two platforms.

In fact, as an MS Exchange-minded person; let me begin by revealing you some features I like about IBM Notes: it is flexible. In last few years, I have seen some relatively good solutions that were made with (and around) IBM Lotus Notes. As far as my experience goes, there is not much that it won’t let you to modify (or overwrite). It also comes with some useful features like recurring meetings with sporadic dates (a feature that everyone wants to see in MS Outlook!). And in some good way, I like the flexibility and uncomplicatedness of the file structure: each mailbox is a database in its particular right and signified by a single file (nsf) that you can put at anyplace you wish to: including NAS storage.

My main point here is that both platforms have their qualities and unique selling points. Don’t try to compare them: it can’t be done.

Why do people migrate?

I cannot disregard the statistic that during the last few years I have perceived my share of migrations to Microsoft Exchange. Why is that?

As a consultant, you get to hear the roughest stories. Occasionally it look as if that any reasons is good to move away from Lotus Notes: “Cost”, “Interoperability”, “Manageability”, “Following the market”, “the CEO doesn’t like the client” and my favourite “I want my new mail to appear on top”. From the above-mentioned reasons, I consider “Manageability” to be the origin of all evil (from IBM’s point-of-view at least). I don’t know the exact numbers, but the amount of experienced Lotus Notes administrators must have been falling (quickly!)…

All in all, every single migration starts with a motive. There has to be a reason. If you can’t catch a reason to migrate then simply don’t.

In my individual judgment, there are numerous aims why a lot of corporations are switching from Lotus Notes to Exchange Server. First of all, IBM Lotus Notes is not a messaging platform; rather it is an application/development platform that provides mail abilities. And while Lotus Notes does a good job at handling email communication. But MS Exchange (in my opinion) basically handles it better.

Manage the expectations!

There is no doubt that MS Outlook provides a great value to the users, but at the same time you must face the fact that some things are not credible with this email client.

It is always expected to lose some data in migration.  There are always one or more emails that have been residing in the user’s mailbox for many months which are untouched by the user or there might be a chance that those mails are corrupt. Even though, the user no longer remember that mail or mails, but still there is a chance that they will make your life difficult while performing migration. So, you must prepare yourself to face this situation.

Do I discourage migrating to Exchange/Outlook from Lotus Notes? No, not at all! Though it is possible that your efficiency might get hurt during the first couple of weeks once the migration is done completely but we typically see a great escalation later with a lot of pleased faces as a consequence.

To coexist or not?

Definitely not! (Until and unless you are having a convincing plan to do then) Anything other than mail flow among both platforms should be sidestepped at all cost! If you still go for coexistence, you will have to bear huge amount in operating both. And moreover it will create complications. That is somewhat you don’t want to face: adding complication to something that is already complicated.

Most of the time, we only perceive coexistence set up in situations where the old (Lotus Notes) environment remains to live on for a while (maybe waiting for its apps to get transformed into SharePoint, who knows?)


Am I asking you to use a migration tool? Yes. If you are looking for an ‘easy and swift’ method to migrate from one side to the other and want to perform the migration in a right way, I’m quite sure using you a professional tool would be a good option.

Final Words

In this post, I have only scratched the surface of what a migration consist of. I haven’t spoken about all facts nor have I spoken about all the diverse options and tools. But I hope that – for those planing to switch or already have made the choice – this post can throw some insights and inspirational considerations.

Rest assured: I perceive a lot of these migrations come to an happy ending; generally the ones where a lot of time was consumed on examining, scheduling and authenticating… ;-)

Just summon up: migrating from Notes to MS Exchange is more than only changing a system. Try to look at it in a universal way:  it is also about altering your operations, even more important: your conviction.
Thursday, 10 December 2015

How To Fix "Generic LSE Failure" Error in Lotus Notes

Lotus Notes is one of the most widely used e-mail application programs used in present era. It executes all the mail operations like e-mailing, programming, calendaring, scheduling, etc which are performed by all common e-mail application programs like MS Outlook, Outlook Express etc. Lotus Notes database comprises of NSF files as its data files.