Searching...
Tuesday, 28 February 2017

How to migrate Exchange Server Data from one Service Provider to another?

If you are using Hosted Exchange with a company that provides no Management tools at all. Any time when you need to add a new mailbox or any changes on your mailbox, you have to contact the hosting company to do it for you.  If you are planning to move them to another hosted Exchange service providers like Rackspace or any another then Check below-listed suggestions on the best way to accomplish this even you have almost no control or tools on the current hosting side.

To accomplish this, you should follow this path:

•    Move Exchange data(mailboxes) directly from their current host to Rackspace
•    Then make the necessary DNS changes and
•    Reconfigure the Outlook clients to point to the new server

Solution 1:  Migrate Exchange to Exchange via Inbuilt Exchange utility:  

First solution I would recommend you use Exmerge to export the data out of Exchange into PSTs then import them back to the new server. In this case, you should have sufficient access to run that utility, Or you can also use Stellar EDB to PST Converter to export exchange data to PST file. This tool does not require any permission settings on your account if you have EDB file (Online or Offline); it can convert it into PST format without disrupting Exchange Server Services. Later you can import PST file into Exchange Server.

Let’s consider following points if you are switching to Rackspace

1.    First, change mail storage in Outlook from the server to a PST stored locally on the computer or an in-house server.
2.    Setup Rackspace then test it before you change your MX record.
3.    Change your MX record over to Rackspace
4.    Change all your clients over to Rackspace


Note: Make sure you have turned on Cached Exchange Mode Outlook 2003 or later on all clients

5. Once everyone is pointing at Rackspace, then import PST file to the Rackspace server.

If you use Cached Exchange Mode, it will help you with getting data uploaded.  Here's how:

1. All emails locally saved in OST file for Exchange.  During this time you have local access to the mail even though it isn't connected to Exchange server. You will also receive the NEW e-mail from the server though.

2. As long as Outlook is open and connected, your offline Outlook cache will continue to synchronize with the Rackspace server over RPC over HTTPS (Outlook Anywhere).  You'll see in the bottom right corner of Outlook that folders are synchronizing or "All folders are up to date."

Solution 2: Migrate Exchange to Exchange via Outlook:


You can transfer your Microsoft Exchange data via Outlook by using following steps: Export data into a .PST file

•    Open Outlook and log into Microsoft Exchange mailbox then Select File / Import and Export.
•    Select the Export to a file option. Then Next
•    On the next window, select Personal Folder File (.pst) & then click the Next button.
•    Then choose the Include subfolders check box.of the following and select the Next button:

You will now save this .PST file. The default save location is C:\Documents and Settings\(user name)\Local Settings\Application Data\Microsoft\Outlook\backup.pst. Select the Browse button to select a different location.

After exported your .PST file then you’ll need to add your new Service Provider Microsoft Exchange email account to your email client. & then you can import you pst file to new Service Provider Microsoft Exchange email account.

Move mailboxes from the source server to another are hard enough. Some mailboxes might be corrupt and not migrate. If you want to back up your mailbox locally, you should use “Export data into a .PST file” option.

You can export mailbox data from OST files into PST files for Outlook users, and redirect new mail from their current provider to be delivered to the PST rather than the mailbox. If your OST file is huge & you don’t want to lose your data, in this case, you can use Stellar OST to PST Converter. The software converts large ost file into pst file format. The software also has the option to compress & split large pst file after conversion.

Next to create new profiles in Outlook for the users, and setup the new Rackspace Exchange accounts, connect to the new Exchange server and a new OST will be created in the new Outlook profile.  After checking everything is working correctly then change the MX records on the domain names to point to RackSpace.

Keep in mind to turn on Cached Exchange Mode, that way you can kept the data will be both in Outlook and on the Exchange Server. This way you have less chances of data loss.
Tuesday, 31 January 2017

How to use ESEUTIL utility different switches

Sometimes administrators are faced Exchange server failure issue due to temporary power cut-off or due to something serious Exchange Server issue. No matter what is the reason, when you manage to get the server up again, it may come out that the .edb file has troubles to mount and shows the status called Dirty Shutdown Error. In these scenarios, ESEUTIL will help a lot to fix these issues. ESEUTIL used to fix corrupted Exchange databases, defragment Exchange database, reduce database size & check Exchange Database integrity.
 
Before using ESEUTIL tool, please make sure following steps:

1.    First Check the Application Log detailed events for the startup of Exchange database. Open any error events and use the Microsoft Knowledge Base (http://support.microsoft.com) to look up error numbers listed in the description fields.
2.    Try to restart the server. This is the Best way of clearing out random problems in Exchange Server and getting you back your database in the clean state when you don’t have time to find the root cause of the problem.

The ESEUTIL tool: the ESEUTIL tool has many switches:
 
PS: Before using ESEUTIL tool, first make sure that you have updated the backup copy of database files.

•    ESEUTIL /D – defragment the database files
•    ESEUTIL /R – restore your database
•    ESEUTIL /G – check database integrity
•    ESEUTIL /K – verify checksums in the database
•    ESEUTIL /P – repair corrupt databases
•    ESEUTIL /M – display database files’ headers, logs or checkpoint files
•    ESEUTIL /Y – copy database files and log files in a more efficient way
•    ESEUTIL /C – perform hard recovery of a database


Defragment the database files:

First thing when you are going to perform defragging database file the database should be dismounted (Offline mode) so that user’s database will not be able to access their email during the defragging process.

The second thing, you need some free space to perform the defragging.  (Free disk space equal to 110 percent of the end size of the database)

Generally, defragmentation is not recommended because it only removes white space in the database that later will be filled in with data anyway. So Many Exchange administrators asked for Should We Defrag Exchange Server Mailbox Databases? The Answer is it depends on some reasons: Take a look at Reasons to Defrag Mailbox Databases

•    If there is no additional space available to create a new database for mailboxes migration
•    If you get active alerts for low free space on the storage for the database
 
Steps to Defragment the database files:

•    First start with is to dismount the database: Dismount-Database –Identity <database_name>
•    Run the ESEUTIL tool and /d switch: Eseutil /d <database_name> [options]
•    Mount the database again: Mount-Database –Identity <database_name>

Let’s check how much free space is taken up by the database now. To verify that you can use this cmdlet: Get-MailboxDatabase -Status | ft name,databasesize,availablenewmailboxspace

Repair your Database with ESEUTIL

If Exchange database has been reported in Dirty Shutdown state. If you will check the error, there is the Log required header which informs about the necessary log files.

The missing log files are required to recover the database without any data loss. If this is the case, you can use following command:
ESEUTIL /r <log_prefix> /l <path_to_the_folder_with_log_files> /d <path_to_the_folder_with_the_database>

After this cmdlet being executed, the missing logs will be restored to the database.
Now, check the state of our database one more time, it will show in Clean Shutdown State.
The database can be mounted now. Use this cmdlet to complete the task:
Mount-MailboxDatabase –identity <database_name>

Hard Recovery using Eseutil

Hard Recovery using Eseutil may cause data loss and make it difficult to predict how much data may be lost. This is the reason why the hard recovery should be used only as the last resort when there is no other alternative to recover the Exchange database. In this case, you can use Third Party Exchange Recovery Software. By using these tools, you have the assurance of no data loss.

The process of hard recovery has three stages:

•    Exchange Database repair with ESEUTIL /P switch.
•    Defragmentation of the Exchange database and its reconstruction with the /D switch.
•    Index repair within the database with the IsInteg tool.

Let’s start with hard recovery:

ESEUTIL /P <path_to_the_database>
Then, you need to defragment the database as discussed above.
The final stage is to use the IsInteg tool to repair the database. It repairs mailboxes as well as folders.

To repair the Exchange database, execute the following command:
Isinteg –s <server_name> -fix –test alltests

At the end of an Isinteg fix run, you will check that there are thousands of warnings listed. You don’t need to worry about it. The thing that you need to worry about is not warnings, but errors. After successful completion of Isinteg command, there should be zero errors reported. If there are one or more errors, then you should run Isinteg again & again until you get the error count down to zero. Once the repair has been finished, you are ready to mount the Exchange database.

If still, Isinteg does not decrease the number of errors reported, then you should restore your database from updated backup. One another solution is to use Third Party Exchange Recovery Software. By using these tools, you can recover Exchange database without backup.

Summary

If your Exchange database is damaged, data can be restored from backup or repaired using Eseutil and Isinteg. Always make a backup of your Exchange database and keep in mind that Eseutil and Isinteg utilities cannot guarantee 100% success rate. 
Friday, 30 December 2016

How to Migrate Exchange 2007 to Exchange 2016/Office 365

If you are still using Exchange Server 2007 for any of your email and calendar services, it is better to start planning to move the associated mailbox data and resources to Office 365 or newer version of Exchange. Exchange 2007 support will expire until April 2017. Latest versions of Exchange Server and Office 365 have even more to offer. Users running Exchange 2007 have many methods by which they can easily move Exchange mailboxes to Exchange 2010, Exchange 2013, and Exchange 2016 or migrate directly to Office 365.  

Here is step by step guide which you may follow to start planning your migration of Exchange Server 2007:
Plan to migrate Exchange 2007 to Office 365
Cutover Migration: If your Exchange Server is fewer than 2000 mailboxes, you should use cutover migration method. You can perform a cutover migration by using the Setup wizard, or by using Exchange Admin Center (EAC). With the help of Setup wizard you can only migrating 150 mailboxes. If you can move up to 2000 mailboxes from the EAC. The method is supported for Exchange 2003, 2007 and 2010;
Staged Migration: If you want to migrate more than 2,000 mailboxes, you should opt for staged migration method.
Hybrid Migration: This method is not supported in Exchange Server 2007. If you have Exchange 2010/2013 and more than 150-2,000 mailboxes, want to migrate mailboxes in small batches, you should opt for this method.
Let’s start with cutover method:
Step 1: Planning Migration   
First Open the Exchange Deployment Assistant site, the site cover all migrations scenarios to migrate from Exchange 2007 to Office 365. I am using simple cutover migration method from Exchange Server 2007 that’s why I am using Cloud Only option. Answer all the questions on end state goals and existing setup. After completing all the required steps, it will generate a step by step guide for migration.
Step 2: Test Existing Setup
Now you need to make sure that Exchange 2007 infrastructure supports Outlook Anywhere (RPC over HTTP) and Autodiscover. After that use the guide to verify the Exchange 2007 setup. Once the setup is verified, use the Microsoft Remote Connectivity Analyzer to verify Outlook Anywhere (RPC over HTTP). Also make sure that you assigned the correct account migration permissions to the mailboxes that you are going to migrate. 

•    Open the Microsoft Remote Connectivity Analyzer site.
•    Select the Outlook Anywhere (RPC over HTTP) test then click to Next.
•    Enter all the information that are requested. Also verify that you are using Autodiscover to detect server settings.
•    Now Enter the Verification code.
•    Click Perform Test.
•    Once the test is successful, you can continue to the next step. 
Step 3: Configure Cutover Migration
•    Now Login to the Office 365 Admin Center.
•    Open Exchange Admin Center>>Click Migration.
•    Click on + button and select Migrate to Exchange Online option
•    Now choose Cutover migration>>Click Next.
     Enter on-premises account details>>Click Next.
•    Next Exchange Server & RPC proxy Server Setting have been automatically selected then click on Next
•    Enter name for New Migration Batch then Click to Next button
•    Select a recipient to get a report once the migration process is get completed.
•    You can start the batch automatically or start it later by selecting it in migration dashboard & then click on start button. I am selecting batch automatically option then click on New.
New migration batch will be created and you will see the status to syncing.
You will check the Migration details by clicking View Details under the Mailbox Status
Step 4: Migration Complete
After the migration is done from Exchange 2007 to Office, the sync status is get changed from Syncing to Synced & you will also get a report emailed to you
Plan to migrate Exchange 2007 to Exchange 2016
A direct migration from Exchange 2007 to 2016 is possible only across forests. If you want to migrate directly from Exchange Server 2007 to Exchange Server 2016 in the same domain it can be done by first migrating to 2013 then move to 2016. There is no direct way to migrate directly from Exchange 2007 to Exchange 2016. The Exchange deployment assistant can help you with this. https://technet.microsoft.com/en-us/office/dn756393.aspx
It is better option, you should perform the migration using professional tools like Stellar EDB to PST Converter, which can directly export mailboxes from Exchange Server 2007 to Exchange Server 2016 without any hassle. The software also have option to migrate mailboxes from Exchange Server 2007 to office 365.
Wednesday, 9 November 2016

How to handle Outlook–Exchange connection errors

Microsoft Outlook is quite frequently used in combination with Exchange Server. In fact, the duo makes for the standard emailing platform that most organizations use today. However, often while trying to connect to the Exchange Server through the Outlook client, users face some errors which baffle as well as irritate them. In this article, we’ll be highlighting one such particularly notorious error along with its solution.
 
Problems while connecting Outlook to Exchange

If you’ve been working with Outlook for long, you would definitely have connected to the Exchange Server at least a few times. However, sometimes, the following connection issues crop up which prevent Outlook from connecting to Exchange:

•    For an automatically configured Outlook profile: 
“The action cannot be completed. The connection to the Microsoft Exchange Server is unavailable. Your network adapter does not have a default gateway.”
 
•    For a manually configured Outlook profile: 
“Your Microsoft Exchange Server is unavailable”
 
Why these errors occur?
The reason behind these errors is that, a client computer running Outlook should have a default gateway configured to allow IP traffic to flow in environment thus facilitating connection with the Exchange server. If such a gateway is not configured, Outlook will not be able to connect to its present profile. Even when you try to create a new Outlook profile, the same error will flash.
 
For better understanding, consider a scenario wherein you have an existing profile that’s already connected to the Exchange Server. You somehow lose the setting for your default connection gateway and to verify what the settings were, you click on Check Name in the E-mail Accounts dialog box. Outlook won’t let you achieve the task and you’ll see the following error message:

“Outlook cannot log on. Verify that you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Your network adapter does not have a default gateway.”
 
Even if you ignore the default gateway aspect of the error considering it to be a client-side issue and try to connect Outlook to Exchange through RPC over HTTPS, you won’t be successful. In spite of the network being a private Hyper-V switch and all machines being in a single subnet, the gateway might be required to enable the connection.
So what should one do to resolve this issue?

Steps to resolve the error:
 
As you might have gathered from the description of the error, you’ll need to configure the gateway to resolve this problem. But, doing that is alas, not easy and is not possible on some occasions. Hence, opting for a workaround would be much simpler. This workaround involves adding a DWORD value (named DefConnectOpts) to a registry subkey. Here’s how you can do this:

1.    Go to Start -> Run. In the Open dialog box, type regedit and press Enter or click OK.
2.    Depending upon the version of Outlook you’re using, search for the following registry subkey:
Outlook 2007:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
Outlook 2010:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\RPC
Outlook 2013:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\RPC
3.    In the ‘Edit’ menu, hover on ‘New’ and then click ‘DWORD Value’.
4.    Write “DefConnectOpts” and press “Enter”.
5.    Then right-click on “DefConnectOpts” and click on “Modify” from the pop-up menu.
6.    A “Value data” box will open, type 0 here and click OK.
7.    Quit the Registry Editor.
 
What we actually did by the above procedure is that we disabled the current Outlook version’s connection logic and forced it to use the previous version’s connection logic. So now, the gateway configuration will no longer be validated when we try to connect Outlook to Exchange.

Make sure you backup the registry before modifying it this way and follow the steps mentioned accurately. This is because the above steps modify the registry and serious problems can occur if you do it incorrectly. Such modification directly impacts the Exchange server database (EDB) files which if get corrupt can lead to data loss. Subsequently, to repair corrupt edb you’ll need proficient EDB Repair Software to repair exchange database. Such software can efficiently repair corrupt edb file and protect you from data loss.
 
Conclusion
The issue described in this article is a rare one and it is important to remember that Outlook – Exchange connection can fail due to many reasons. Always be careful while making workarounds through the registry since they directly impact your Exchange database. Backup your registry before modifying it and always keep third-party recovery software at hand to repair exchange database if any disaster happens.
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

Conclusion: 
 
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

Introduction:

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:
 
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.


New-MailboxRepairRequest:

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 xyz@xyz.com -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: https://technet.microsoft.com/en-us/library/ff625226(v=exchg.160).aspx

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.