Friday, 17 August 2018
8/17/2018 04:23:00 am 0

How to Export Exchange 2003 Mailbox to PST Over 2GB

MS Exchange 2003 server amongst its many compatibility features, allows Exchange Administrators to export Exchange database files to a new server or newer file formats. However, while performing the Exchange database migration, they often come across issues like “mailbox over 2 GB” when they run Microsoft suggested Exchange utility Exmerge.exe. The reason is that inbuilt programming Algorithms do not support Export Exchange 2003 EDB to PST for more than 2 GB and shows an error. To handle this gap the best feasible option is to deploy Stellar EDB to PST Converter and migrate mailboxes irrespective of their file size.

Wednesday, 27 June 2018
6/27/2018 10:02:00 pm 0

How to Resolve "ESEUTIL failed with jet error -1811"?

While using ESEUTIL, users can sometimes face unexpected errors which can lead to complete mailbox inaccessibility. Resolving such errors is an uphill task especially since the information that appears along with the error message can be very cryptic. Stellar Phoenix Mailbox Exchange Recovery software acts as a one-stop solution for dealing with Exchange ESEUTIL errors and can play an instrumental role in bringing the Exchange server back online in such scenarios.

Tuesday, 8 May 2018
5/08/2018 10:22:00 pm 0

How to Solve Exchange Information Store Error 1053 on Startup

The Exchange Information Store is a critical server component which, if facing issues, can put the entire lot of server activities on hold. Errors like 1053 on startup can be especially problematic since they can lead to complete inaccessibility of user mailboxes and public folder databases which are parts of the Information Store. Stellar Phoenix Mailbox Exchange Recovery software is a product that can prove to be a worthy asset when trying to combat errors like this.

Introduced in Exchange 2000, the Information Store is primarily composed of mailbox and public folder databases. Exchange Information Store (IS) is a storage platform that is used to manage different types of information within Exchange server. Storage Groups are a critical component of the IS and are comprised of multiple public and private stores. It is in these public and private stores that the actual Exchange databases reside. Depending upon their type, various database components are saved within EDB and STM files. The rich text MAPI database gets saved in EDB file while STM files store streaming data along with the content that arrives from the SMTP source.

Since the health of the IS directly impacts how Exchange server works, even minor issues within it can lead to disasters. Citing the case of one of our clients here, following an Exchange server system update, they constantly faced issues where the IS would not start like it should automatically but instead, it kept throwing various error codes like Exchange server error 451, Exchange server error 452, and Exchange server error 471.
Since the IS wasn’t starting and they weren’t able to gather much information about the error from the event log, the client couldn’t proceed with their regular server activities and badly needed a quick fix. Read on to find out exactly how we helped them to overcome this issue.

Finding the real cause behind IS Error 1053

Understanding why an error happens is crucial in determining its resolution. Here are some probable causes of the Information Store error 1053:

  1. ·    Incompatible .NET Framework installation against the service pack for Exchange Server
  2. ·    Inability of Exchange System Attendant in finding any of its default containers: Exchange Enterprise Servers, Exchange Services, and Exchange Domain Servers
  3. ·      Missing or corrupt jcb.dll file in callback library
  4. ·      Unexpected system shutdown
  5. ·      Incorrectly writing data to the disk

Depending upon what the exact cause for the error is, the next section contains a list of solutions you can try out to fix it.

Solutions to Exchange IS error 1053

Note: The following fixes work to solve Exchange server error 451, Exchange server error 452, and Exchange server error 471. Try the below mentioned solutions one at a time. Move to the next fix if the previous one doesn’t work.

  • ·         Ensure that the latest updated .NET Framework is installed for Exchange
  • ·         Ensure the Exchange Storage Group exists in one of its default containers
  • ·         Copy jcb.dll file from Exchange 2003 SP2 installation disc to “Exchsrvr/bin” folder
·          Follow the below mentioned steps:

1.    Open Windows NT Event Viewer and verify the log for following services:
§  EDB file
§  MSExchangeIS
§  MSExchangePriv
§  MSExchangePub
Note: If the event log shows any other error apart from “Out of the disk” or one that suggests using “isinteg-patch” command, proceed further. Else skip to the sure-shot remedy discussed in the last section.
2.    Shut down all running Exchange services and reboot the server. Restart the server to automatically restart the IS; when that happens the IS will automatically try to restore the database into consistent state.
3.    Make a full online backup of Exchange IS database (including all EDB, STM, and LOG files)
4.    Now initiate a full restore of the backup and ensure that the “Start Services after Restore” option isn’t enabled. When the IS starts, it replays the existing log files bringing the information store to functional state and if this step is processed successfully, you can be sure that no data will be lost.
5.    Go to event log and check the log files for the EDB file. If they contain any message indicating that there was problem while replaying the log files, then open the Mdbdata folder and remove corrupt log files that. Once this is done, restart the IS.
6.    If step5 doesn’t work, initiate a full online backup. Enable “Start Service after Restore” option and select “Erase all Existing data”. This will restore data to the point when backup was last taken.
7.    Note: This step will involve the erasing of existing data in the IS. Hence proceed with caution. If you cannot afford any loss of data, skip to the sure-shot remedy discussed in the last section.
8.    Now start “Exchange Server Administrator” program, click on “Advanced” tab and run “DS/IS Consistency Adjuster”.
9.    If these steps fail to eradicate the error, then the last resort is to wipe the Information Store. To wipe out stores, backup database and delete EDB, CHK, LOG, and STM files.
Note: The process to wipe private and public IS will result in irrecoverable deletion of mailbox data and public folders. To revive the IS without any loss of data, skip to the sure-shot remedy discussed in the next section.

Sure-shot Remedy to Exchange IS error 1053

If none of the above methods work or you wish to avoid any data loss, repair Exchange EDB file using Stellar Phoenix Mailbox Exchange Recovery software. This advanced tool is undoubtedly the most sure-shot way of getting rid of problems like Exchange server error 451, Exchange server error 452, and Exchange server error 471 which stem from Information Store issues like the error 1053. Backed by powerful scanning and repair algorithms, this product helps users repair even the severest of damage and corruption in Exchange EDB files and recover the data saved within them. Find all there is to know about this product here:

Final Words
If the solutions discussed above don’t work, use Stellar Phoenix Mailbox Exchange Recovery to recover the Information Store data. Once the database has been recovered, reset the IS to give things a clean start.
Monday, 24 July 2017
7/24/2017 02:30:00 am 0

How to Export large Exchange mailboxes to PST

Exchange server plays home to user mailboxes for an entire organization. With hundreds of incoming and outgoing emails per day, the size of Exchange mailboxes is bound to exceed its limits. Exporting large mailboxes to PST format is the only way to protect them from inevitable corruption. Stellar EDB to PST Converter is the ideal choice for exporting large Exchange mailboxes to PST format.

For any organization, its database is priceless. All business documents, user mailboxes, and hundreds of other entities reside within it. Thus, every possible measure is taken to safeguard it from damage. But with so much data piling up within the database for years, the size of the Exchange database file (EDB) is sure to exceed safe limits. Lest it turns corrupt, some actions must be taken to reduce the EDB file size. One of the best ways to do it is by converting the EDB file to PST format.

The difficulties of exporting large mailboxes to PST

It sounds simple in theory but exporting data from large EDB files to PST format is practically tricky. There are a lot of methods to do it but the problem lies in the large file size that needs to be converted. Usual methods that work with mailbox export fail when the size of the mailboxes exceeds a certain limit. For example:
  • Microsoft Outlook freezes while trying to export
  • Finding the correct parameter to export using New-MailboxExportRequest is challenging
  • Trying to export mailboxes larger than 5GB with the New-MailboxExportRequest command results in error 0x80040115
Thus, to accomplish the export, some workarounds need to be adopted.

Solutions to the problem

There are several ways to solve the issue:
  • Manual folder-by-folder export through Outlook
  • Exporting to separate PST files for each Exchange folder. However you should take care that each individual PST shouldn’t exceed a size of 20GB
  • Using parameters like “ContentFilter” in conjunction with “IncludeFolders” when executing the New-MailboxExportRequest command
  • Export using an all-in-one (CAS+HUB+MBX) server. For this you’ll first need to move the target mailbox on this server. Thereafter, follow these steps:
  •          a.    Create a share on CAS server
  •          b.    Use PowerShell command New-MailboxExportRequest with the MRS service running on the CAS server to translate information to PST and store it on a UNC path.
  • Split the mailbox using date ranges with the help of Search-Mailbox command and then export each smaller mailbox
  • Use a third-party product to split PST and spawn a new one when the set limit is reached. For example, when the first PST reaches 20GB, spawn a new incrementing PST and start exporting data to it.
 Recommend Third-Party Software

If none of the other techniques work and you need to go with a third-party tool to complete the job, we recommend that you use Stellar EDB to PST Converter. This professional tool extracts all vital Exchange mailbox data such as emails, contacts, attachments, etc. from online as well as offline EDB files and converts it into equivalent Outlook PST format. This handy tool can help you shed some load off old EDB files by converting them to PST format and moving them to local machines. Also, since it supports conversion of online EDB file, you won’t have to dismount the database during the process. It can thus save you from hours of server downtime and loss of productivity.

The Final Word

To avoid EDB files and mailboxes from growing extra-large in size, here’s a suggestion – instead of splitting the mailbox when it gets large, create a new journaling mailbox as the "current one" grows to 10GB.  This way, you won't need to split the mailbox later. Also, you may wish to consider using a separate journaling server and host the journaled mailboxes on it.  In any case, now you know how you can handle “export large mailboxes” problem through reliable third-party software.
Sunday, 14 May 2017
5/14/2017 09:54:00 pm 0

How to recover Exchange Database with log files

Developed by Microsoft, Exchange Server is one of the most widely used mail as well as a calendaring server. This popular messaging platform offers scheduling, emails, and tools for both messaging service and custom collaboration applications. With hands on this renowned application, a user can manage as well as create all communication effortlessly, be it in on the mobile device or at the workplace.
In the Exchange Server, one thing that plays a vital role is Transaction Log Files. It manages the complete changes record that are made in the Exchange Server. All the information i.e. to be inserted into mailbox database is first written in the Exchange Server database. If in case, any detail is missing from the log file, it results in an operation failure issue. And, as a result, a user cannot access mailbox database from EDB files. In short, log files are essential for proper functioning of the Exchange Database.
Let’s now look at how log files help in Exchange Database Recovery - 
How to Recover Exchange Database with Log Files
Prior to executing the Exchange mailbox database recovery, a user needs to examine whether the state of the database is healthy or is in a dirty shutdown. To run this, the user needs to use the following Eseutil/mh command:
c:\program files\exchsrvr\bin>eseutil\mh “drive: \program files\exchsrvr\mdbdata\priv1.edb”

Two Approaches to Recover Exchange Database
•    Soft Recovery
•    Hard Recovery
Soft Recovery
Soft Recovery is the procedure of replaying the transaction log files in a scenario when the database is re-mounted on the server that is suffering from an unanticipated halt.
During this circumstance, the soft recovery process is auto-executed by the Exchange Server through the entire pending transaction log file just by reading the checkpoint file. If in case, this auto process does not work, Eseutil commands are being used.
ESEUTIL / r enn/ L [path to log files] / s[ path to checkpoint file] /d [ Path to database file]/ i
Here r stands for recovery mode, enn for log file name prefix, /l specify path to log file, and /d specify the path to database file (it does not includes the name of the file itself). 
Steps are as follows:
•    Execute Eseutil /mh command.
•    Now, check the health of the database
•    If the state is clean shutdown, then from Transaction logs folder location, migrate all the log files and mount the stores; In case it is in a dirty shutdown state, ensure whether Logs required log files is available or not.
•    Next, check whether the required log files are in a clean state or not. To confirm this, execute Eseutil /ml “Path of the log files\log prefix”.
•    Now, if log files are healthy, use Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database” command and execute soft recovery— eseutil/r.
•    On successful completion of all the commands, mount the stores.

If in case, an error is generated—“Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but the database is missing or does not match attachment info) after n seconds”.  Then just run soft recovery using “/i” switch. This action will override the EDB-STM mismatch and resolve the error. ¬¬

Hard Recovery

Hard Recovery procedure uses online backup to replay log files. If, in any circumstance, the “Last Backup Set” option is set on, then the recovery process can be executed automatically. In this recovery process, there is no need of a checkpoint file as database recovery is performed using restore.env file. Adding more, in the scenario, when “Last Backup Set” option is not enabled, hard recovery is to be executed manually using Eseutil command.

Syntax to execute Hard Recovery:
C:\Program Files\ Exchsrvr\bin.eseutil /cc “ C:\Temp\First Storage Group “_

Here, C:\Program Files\ Exchsrvr\bin.eseutil / indicated Eseutil installed location, C:\Temp\First Storage Group “_ indicates restore.env folder location.

Note: This recovery process will only work on the restored databases from the valid backup. No other Exchange server EDB files can be recovered using it.

Steps are as follows:
•    Go to C:\Temp
•    Check the log restore location
•    Now, open the folder and check for the Restore.env location
•    Now,  use the copy of Restore.env location as well as logs to execute Hard Recovery
•    Go to command prompt
•    Run the Hard recovery from Bin folder using Eseutil /cc “Path of the restore.env containing folder” command
•    After a successful completion, the Restore.env folder will be empty
•    Now, stores are ready to mount

Inevitably, with hands on this manual process, an individual can recover Exchange Database with log files. However, this recovery process is a bit lengthy and is not free from manual intervention. Therefore, it becomes prone to risks. To overcome this, a third-party recovery solution would serve the purpose as it is fully automated and free from manual interference.

Based on experienced and skilled professionals, if a suggestion is to be made then, Stellar Phoenix Mailbox Exchange Recovery is a sure-shot. It is tried, tested, and an approved software solution.

About Stellar Phoenix Mailbox Exchange Recovery
Stellar Phoenix Mailbox Exchange Recovery is an ultimate utility designed to repair corrupt Exchange Server Database Files. This professional solution works in almost all scenarios of data loss, be it corruption, crash, damage, etc. With hands on this software, an individual can quickly repair EDB Files as well as mailbox content such as Calendars, Journals, Contacts, Emails, Attachments, Tasks, To Do List, and much more.

The overall functionality of this EDB Files Recovery tool is simple; three intuitive steps—Select, Scan, and Save. It is fast, easy, reliable, and secure. This do-it-yourself software is highly demands its impressive option sets, improved features, and amazing look & feel. Adding more, it offers you with the flexibility to save the recovered data into varying formats such as HTML, PST, RTF, EML, MSG, and PDF.

This ultimate Mailbox Exchange Recovery software supports PUB.EDB files repairing, Windows 10, 8.1, 8, 7, Vista and Windows Server 12 and 8. Additionally, it is compatible with the MS Exchange Server 2016, 2013, 2010, 2007, 2003, and 2000.

The Way Forward
Nowadays, Exchange is one of the most popular mail servers. This Server is used at a gigantic scale for scheduling, tools, emails, etc. Thereby, it is necessary to ensure proper functioning of the same for increased productivity as well as management. However, just like other utilities, it is also prone to getting corrupt or damaged. Here, Exchange Recovery becomes imperative.

Tuesday, 25 April 2017
4/25/2017 04:07:00 am 0

Exchange 2016 Vs Office 365

In this rapidly evolving world of computing technology, email is considered as a cornerstone of all the modern business. Whether you are small-sized or medium-size businesses, you certainly need not limit yourself to only one email client application.  Therefore, if you are looking forward to switching, then you must have encountered several options to choose from such as Office 365 or Hosted Exchange.

However, from this extensive array of choices, selection of the perfect business email cloud solution may be a bit tricky. An individual can only opt for the right option when they have a clear list of their requirements.  The reason being, every individual has different needs. For instance, the needs of an organization building its IT services from the start will surely be different from the one who are hosting their on-premises email servers for some time and are planning to migrate to the cloud. Adding more, every organization has different industry regulations to follow; depending on them, they may have more or less constraint. Further, as no two business organizations are the same, therefore depending on your organization, you have other issues at hand as well.

Therefore, to help you with the selection of the ideal option for you, we have compared Exchange 2016 with Office 365 - the two best options for business email hosting. Based on this analysis, you can easily bid goodbye to all your apprehensions.

Let’s now have a quick look at the Exchange Server.

Core of Hosted Exchange and Office 365 Email System

It is essential to know about the Exchange server as both Hosted Exchange and Office 365 are two cloud offers that are based on this platform. Regardless of the option you choose, the email system potentially runs on the same platform. 

Exchange Server Power

Exchange Server amounts to almost 51% of global business mailboxes. It includes both on-premise and cloud deployment deployments internationally. The reason for this acknowledgement is its past two decades journey in which it has evolved as the most reliable and efficient business email solution.  Thousands of organizations use the Exchange Server irrespective of their size.

With each new upgradation, Microsoft Exchange Server has made our life easier and convenient by bringing the functionalities that are more topical. Adding more, every new version has also improved the platform stability in comparison to the previous one. Further, thanks to its public cloud trend, it is being delivered as the Software-as-a-Service model. Owing to which some businesses have moved their email service into the multi-tenant infrastructure of the provider and eventually have decreased the IT overhead.

Exchange 2016 Vs Office 365

If change control and stability are in your mind, then Hosted Exchange is the right option for you. Choose this email system to plan your upgrades and changes at the desired pace.

Offers Manifold Choice

With hands on the Hosted Exchange, you get the flexibility to choose the version to run on. You can easily select different Exchange environments as per your convenience. Before deployment, security updates, as well as service packs for the environment are also tested to ensure there is no outage or other concerns.

Comprehensive Migration Assistance

Throughout the migration process, you will be assisted by the provider’s support to ensure carefully planning for the upgrade and smooth transition to a newer environment. Further, depending on the provider, the migration process might not cost you anything. Currently, three Exchange Server platform versions—2016, 2013, and 2010 are supported globally.

First Comes First: Email

When you buy Hosted Exchange, the main service you get is Email.  The size of its mailbox is always unlimited. You can choose only Outlook or Webmail, and you can prefer both. Even you can choose from varying bundles so that you also have other services included.  It also allows you to add Office applications such as PowerPoint, Excel, Word, Outlook, OneNote, and Publisher. In short, here you are completely free to decide.

Other Benefits of Hosted Exchange Server

•    Allows business to utilize Microsoft applications and services such as web application platform
•    Delivers personalized experience to both parties— Enterprise as well as Individuals
•    You can easily set the limit of email boxes size with the help of individual administrating Exchange Server.
•    Allows an individual to ensure where your data is exactly stored

If innovation is driving your business, then Office 365 is the perfect option for you. Choose this email system if you want to be in the lead in terms of new technologies.

Offers a Wide Range of Apps

With Office 365, you will surely have a lot to play with.  Exchange Online of the service provided by them, Email is not their core service. In general, Office 365 is the set of products that includes collaboration as well as productivity applications. The applications it includes are  - Business Intelligence tools (Power BI with Excel), email (50GB per mailbox), Microsoft Office Suite (Excel, Word, etc.), personal and shared files storage (SharePoint libraries or OneDrive), and other exciting services (Yammer, Sway, Skype, etc.). It is available with thousands of plans; you can easily select the one that meets your requirements.

Delivers Trust

Office 365 usage makes you sure that you are running the latest software version. The benefit of this is that you instantly get all new features and enhancements. Further, it also includes new Exchange Server releases. Regardless of the device that you are using, be it MAC, PC, tablet or smartphone, all updates, service packs, application upgrades, and security updates are automatically pushed. Therefore, you can also delay the installation process based on your personal choice.

Offers Free Upgrades

They only charge regular monthly fees. Apart from this, there is no chargeable fee for upgrades.

Other Benefits of Office 365

•    Offers BlackBerry support and integrated experience
•    Delivers security certifications as well as compliances
•    No involvement of third-party hosting organization
•    Enables the Active Directory process management tool as well as legal archiving capabilities
•    Includes features such as Lync Online to provide internal office communication support

How Can I Migrate My Mailbox to Any of Hosted Exchange and Office 365?
By now, you have a clear overview of both Hosted Exchange and Office 365. Also, you now know that your selection is entirely based on your business needs and corporate culture. Depending on this, you would have been able to narrow down your preferred choice to the best business email platform.  Here, the concern is how to migrate.

Solution—EDB to PST Converter

Irrespective of whether you are choosing Office 365 or Hosted Exchange 2016, in both the cases, you need to migrate your data items.  To perform this action, you require a converter that converts your EDB data items into PST Files.

Say a Big No to Blind Selection

As there is no dearth of EDB to PST converter in the market, however, to avoid the damage or worst scenarios, we have sorted out one of the best solutions that is supported by an organization having an experience of over 23+ years in the data recovery segment.  The name of this excellent performing tool that has marked a strong foothold is Stellar EDB to PST Converter.

Brief Synopsis of Stellar EDB to PST Converter

Stellar EDB to PST Converter is a professional dedicated solution intended to convert both online and offline Exchange Server database files to PST Files and directly export offline Exchange mailboxes to Live Exchange/ Office 365. Using this handy conversion tool, you can easily extract all critical Exchange mailbox data including attachments, contacts, emails, etc.  Once you are done with conversion, you can import the PST Files and can regain a hold of your data.

With its selective conversion feature, you can easily convert any specific or multiple files.  Further, features such as multiple files conversion, all mail components extraction, online as well as offline conversion, etc. make Stellar EDB to PST Converter the first choice. 

Unique Traits of Stellar EDB to PST Converter

•    Supports selective conversion
•    Supports Unicode EDB File Conversion
•    Preserves the original integrity of the files
•    Permits Mailbox preview prior conversion
•    Promises one go quick conversion without glitches
•    Supports accidentally deleted offline mailbox restoration
•    Includes options to Save as well as Load Scan information
•    Grants permission for particular mail search in offline EDB
•    Supports conversion of EDB File into EML, HTML, MSG, RTF, and PDF format
•    Ensures extraction of all mail components within the Exchange database files


While the Hosted Exchange offers you stability, Office 365 offers you innovation. In other words, while the former option allows you to control the changes and upgrades, the latter option keeps you abreast with new technologies. Based on the above-stated analysis, you can effortlessly choose the best practice.  After selection, you require a software that allows you to migrate your EDB mailbox and other data content to PST Files or exports them to Live Exchange or Office 365. For this, we recommended one of the top-performing software— Stellar EDB to PST Converter which we have discussed at length.
Tuesday, 28 February 2017
2/28/2017 10:08:00 pm 0

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
1/31/2017 09:44:00 pm 0

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 ( 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

Stellar Phoenix Microsoft Exchange Recovery Software is the best Alternative of Eseutil command to repair corrupt Exchange 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.


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
12/30/2016 11:09:00 pm 0

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.
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
11/09/2016 01:25:00 am 0

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:
Outlook 2010:
Outlook 2013:
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.
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.