Transport routing in Exchange hybrid deployments

What is centralized transport?

If you already have heavily invested in your on-premise mail gateways and other infrastructure and you plan on moving to Office 365, Exchange Hybrid is the way to go in a long haul. When you have Exchange 2016 configured for Hybrid Setup with Office this where it come. 

So Why Centralized Transport?

It all depends on your business requirements, and if you don’t then you are good with regular setup routing via Office 365 , let’s cloud manage it for you. IF YOU DO HAVE such as regulatory and compliance requirements and even for other purpose where you want you emails MUST  route through your on-premises infrastructure then you need to configure it this way. In this video I will walk you over how does it really work.

Route mail through the on-premises organization for both on-premises and Exchange Online organizations









Outbound Messages from on-premises to Internet recipients


It is time to upgrade – End of life Exchange 2007

Exchange 2007 End of Life Roadmap

Do you know that April 11 2017 is the date when Exchange 2007 will no longer be supported by Microsoft.

If you haven’t already begun your migration from Exchange 2007 to Exchange 2016 or Office 365 now’s the time to start your planning.

What does End of Life mean?

Exchange Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product’s initial release, and the end of this lifecycle is known as the product’s End of Life. When Exchange 2007 reaches its End of Life on April 11, 2017, Microsoft will no longer provide:

  • Technical support for problems that may occur;
  • Bug fixes for issues that are discovered and that may impact the stability and usability of the server;
  • Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches;
  • Time zone updates.

Your installation of Exchange 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible.

Benefits of upgrading to Exchange 2016

Simpler and Better Server Architecture – Single Server Role
Better Collaboration
Saving files to OneDrive for Business
Uploading a file to OneDrive for Business.
Most Recently Used lists populated with both local and online files.
Office 365 hybrid
Messaging policy and compliance
In-place Archiving, retention, and eDiscovery
Improved performance and scalability
Antimalware protection
Integration with SharePoint and Skype for Business

What are upgrade options?
#1-You can migrate to Office 365
#2- If you don’t want to migrate to cloud then you can upgrade to either Exchange 2010, Exchange 2013 or Exchange 2016.

I still have more questions, where do I get more details?
Follow this url –



Software Review: Kernel for Exchange Server Software

Kernel for Exchange Server recovery tool helps Exchange administrators to reduce the time and stress involved in the restoration of corrupt EDB files. The tool employs highly advanced algorithms to perform accurate Exchange mailbox recovery, without changing the folder structure and hierarchy of mailboxes. This tool has a user-friendly interface that helps users in performing effortless EDB recovery and migration.

Kernel for Exchange Server promises to reinstate all the mailbox data including emails, deleted items, attachments, calendar, notes, journals, tasks, appointments, drafts and other items along with their meta data. It offers recovery from EDB files that have become inaccessible due to all types of Exchange Server errors and issues – Jet engine errors, corrupt headers, dirty shutdowns. It will be interesting to know more about the features and working of the tool.

Significant features of Kernel for Exchange Server Tool

  • Offers EDB repair, EDB to PST conversion, and migration to Live Exchange server/Office 365
  • Equipped with a search facility by which users can easily locate EDB files
  • Converts inaccessible EDB files to PST files; also offers facility to split the produced PST files after a specified size
  • Recovers entire Exchange mailbox data without any modification to their structure and hierarchy
  • Recovers and migrates multiple mailboxes in a single cycle
  • Recovers UNICODE characters of languages like Chinese, Japanese and French
  • Preserves data integrity and recovers email meta data & item properties
  • Live Preview facility to verify the details of recovered mailbox items
  • Saves mailbox items in PST, MSG, EML, TXT, HTML and RTF formats
  • Mailbox filtration by date range and item type (with the option to include/exclude filtered items)
  • Generates process analysis report after the completion of the recovery and migration
  • Supports Exchange Server versions 5.0, 5.5, 2000, 2003, 2007, 2010, 2013, 2016

Performing EDB recovery using Kernel for Exchange Server

For evaluation of the tool, user can download the free version from the website directly. However, here we present the analysis using the licensed version. The important steps of using this tool are:

Step 1: Upon launching this EDB recovery tool, its main screen appears. In the ‘Select Source Exchange Database’ dialogue box, the user can select the corrupt EDB/STM files using the ‘Browse’ button. Select the required EDB and click ‘Next’ button to proceed.











Note: User can use the ‘Search’ option to trace the files from a drive or volume, if its exact location is unknown. On using this option, the tool will enlist all the EDBs with their paths.












Step 2: In the next step, user can opt the ‘Standard Scan’ mode (this is the recommended mode). If the intensity of the corruption is low, the tool will produce results instantaneously. However, if the files are severely corrupted, user can use the ‘Advanced Scan’ mode.











Step 3:  After the scanning, the tool produces recovery results in a hierarchical manner in the left pane of the interface as shown in the image below. User can select any of the enlisted files and view their details in the preview pane on the right side of the interface. This helps user in verifying the recovered data before saving it.











Step 4: Save individual items: For individual item restoration, user can select the required items and save them using the right-click menu.  User just has to browse for the destination and mention format (MSG, PST, EML, RTF, TXT or HTML) to save the files.








Step 5: Save in PST

To save required files in PST, user needs to click ‘Save to PST’. Now, the ‘Select Mailboxes’ dialogue box appears. User can proceed with the following steps:

Step 5.1

In the ‘Select Mailboxes’ dialogue box, user can select the mailboxes and their specific folders for recovery. Then click ‘Next’.















Step 5.2: Now the user must browse and select the PST file saving destination. The ‘PST Options’ section allows user to create Unicode PST and also to split PST file after a specified size. User can even define file filtration rules and click ‘Next’ to proceed with the procedure.














Step 5.3: The tool will display a successful file restoration message upon the completion of the procedure.














Step 6: Save to Live Exchange Server/Office 365

To save required files in PST, user needs to click ‘Save to Live Exchange/Office 365’. Now, the ‘Save to Live Exchange/Office 365’ dialogue box appears. User can proceed with the following steps:

Step 6.1

In the ‘Save to Live Exchange/Office 365’ dialogue box, user can enter the Live Exchange Server domain credentials i.e. Domain name, user name and password; then click ‘Next’.














Note: To save required files in Office 365, user needs to choose the ‘Office 365’ option. Here, user can enter the Office 365 credentials i.e. user name and password; then click ‘Next’.















Step 6.2: After entering the required credentials, the tool asks user to map the source mailboxes to the target mailboxes. This can be done manually (by click ‘Mapping’) or using a CSV file (by clicking ‘CSV Export’). After mapping the source mailboxes with the target mailboxes, click ‘Next’.















Step 6.3: Now, filter the files on the basis of Item type and date range and click ‘Next’ to complete the file restoration process.















Step 6.4: The tool will display a confirmation message after successfully saving the mailbox data.












Final words

In conclusion we can say that Kernel for Exchange Recovery tool has the capability to resolve almost all EDB related issues, and recover mailboxes in any situation. It can also migrate mailboxes from EDB to Exchange/Office 365 without much effort. The round the clock technical assistance provided by Kernel support team through email, live chat and phone, is extremely helpful too.

Note: this post content provided by Lepide and is published ‘as-is’ 


Exchange Server 2016 CU3 with Windows Server 2016 – NOT SUPPORTED – Hold On

Microsoft Exchange Product Team published the blog post that Ex2016 CU 3 having issues with Exchange 2016 due to the crashes of W3WP.exe and the work is being done, till then don’t proceed.



TechNet has also published the what other features have been reported for issues on Windows Server 2016.


Stay Tuned with Exchange Blog


Exchange 2013/2016 Cumulative Updates and Hybrid Environment.

Exchange 2016 CU2 and Exchange 2013 CU13 now supports .NET Framework 4.6.1

Today Microsoft Exchange Team made announcement of not one but two cumulative updates, one for Exchange 2013 which is Cumulative update 13 and Cumulative CU2 for Exchange 2016.  With these CU updates .NET 4.6.1 is officially supported now.

I’d like to start with Hybrid Deployment first

Minimum CU For Hybrid environments

So if you are and Exchange 2013 or Exchange 2016 or mix of both then you have no choice EXCEPT  upgrade to either CU12 minimum (.NET 4.6.1 is not supported on CU12) or CU1 at minimum (.NET 4.6.1 is not supported on CU1) respectively. So if you on hybrid and want to be at the upgrade to  .NET 4.6.1 then you have to be on the latest CU Levels.

How to proceed?

Do not install .NET 4.6.1 directly on your existing CU, first you need to upgrade to CU13 for Exchange 2013 and CU2 for Exchange 2016, this is the recommendation as per #msexchange team.

  • Exchange Server 2016 Cumulative Update 2 does include updates to Active Directory Schema

Post CU installation

(these three KB article solves the same issue of course you need separate hot fix for all the OS)

Migration to Modern Public Folder Resolved

The issue reported in KB3161916 has been resolved.

To prevent any installation issue
make sure that Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded to.

SHA-2 Support for Self-Signed Certificates

The New-ExchangeCertificate cmdlet has been updated to produce a SHA-2 certificate for all self-signed certificates created by Exchange. Customers may opt to replace existing non-SHA2 certificates generated by previous releases as they see fit.

Support for Exchange 2010 ???

Exchange 2010 is still not support and will never be as per Jeff Guillet – (read his own comment at the bottom of this post)

For full details checkout #msExchange Team Blog

How to export Office 365 mailboxes to Outlook PST


How to export Office 365 mailboxes to Outlook PST

The online version of Exchange (Office 365) does not have the same EDB to PST conversion features that its on-premise version has. However, there are still a few ways that Office 365 mailbox items can be exported to PST. In this article we will take you through the process using Office 365’s eDiscovery PST export tool and compare it to our approach – Lepide Exchange Recovery Manager.


Using eDiscovery PST Export Tool to export mailbox items to PST

The eDiscovery PST Export Tool is available with all recent on-premises versions (Exchange 2010 and later) and allows you to export the results of an In-Place eDiscovery search to a PST file. Such searches could contain items from mailboxes and public folders, depending on the content sources from the eDiscovery search. The following steps will show you how to configure the In-Place-Hold, search for mailbox items and export them to PST:


1. Login to Office 365, go to Exchange admin center, and click compliance management. Under in-place eDiscovery & hold, click the New (+) button.
Note: Make sure that your account is a member of Discovery Management Role group. Otherwise add this role to the user account you are using. For this, select permissions, and double-click Discovery Management under admin roles. When the Discovery Management window appears, add the user to this group by clicking ‘+’ under Members.


2. Enter a name and description in the in- In-Place eDiscovery & Hold window; click Next. pic2


3. Select the required option under Mailboxes. Click Next.
Note: When Specify mailboxes to search is opted, mailboxes can be added by clicking ‘+’.


4. Under Search query, provide the details for searching the items. Click Next.


5. Under In-Place Hold Settings, provide the duration for which the items are to be retained. Click Finish.


6. Click Close when the confirmation message appears.


7. The generated search gets listed under In-Place eDiscovery & Hold. After the completion of the search, click Preview search results to view the results. To export the results to a PST file, click the downward arrow (Export to a PST file button).


8. Now click Run when the security warning about external application appears.


9. In the eDiscovery PST Export Tool, provide a location for storing the exported PST file. Click Start.


10. Provide the Office 365 credential when prompted.


11. Click Close after the completion of the process.

12. Finally, access PST file using MS Outlook by adding it to an existing Outlook profile.

The alternative – Lepide Exchange Recovery Manager

If using eDiscovery seems a little convoluted, or is taking too long, then you may be better off deploying a third-party solution. Lepide Exchange Recovery Manager allows you to export mailboxes from various sources, including Office 365 to PST files, and makes light work of EDB to PST conversions. It’s user friendly GUI and easy to follow instructions turn what could be a difficult task into a simple one. Below are the steps you need to take to export Office 365 mailboxes to PST using Lepide Exchange Recovery Manager:

1. Launch Lepide Exchange Recovery Manager and click Add Source.
2. In the Add Source window, select OWA/Office 365; click Next.
3. Provide the Office 365 login credentials and choose the connecting option; click Next. Click Finish when the connection is established.
Note: When you choose Connect Multiple Mailboxes option, you can select many mailboxes for export.


4. When the Office 365 mailbox(es) gets added in the Source List, all its content gets displayed in a hierarchical manner.
5. Right-click on the mailbox and select Export Message(s) > PST.
Note: When you export multiple mailboxes, you can select Export Mailboxes option.


6. In the Export in PST window, select the folders that are to be exported and set the filters. Provide the export destination, choose the required options, and click Save. Click OK when the confirmation window appears.

7. The export details are displayed at the bottom of the window after the completion of the process. Click Close.

8. Finally, add the PST file to an existing profile and access it in MS Outlook.


Article Summary

The Exchange Online eDiscovery to PST tool enables you to export mailbox items to PST, but the process isn’t as quick and simple as it perhaps could be. You may find that it makes more sense for you to deploy a third-party solution, like Lepide Exchange Recovery manager, which is likely to speed up the process and give you complete control over Exchange recoveries and mailbox to PST exports.


content provided by Lepide and published as is.

Calendar Sharing in App still not possible. Outlook for iOS and Android – What it has and What is missing.

A year ago Microsoft launched the App Outlook for iOS and Android,  which is a very user friendly app.. This app does a phenomenal job on iOS (I’ve not used it on Android) in terms of composing email, send/receive emails and pretty what you need to stay connected. It has swipe feature , you can swipe RIGHT  or LEFT  to take actions like archive, delete, move, flag, mark as read/unread or schedule. Unlike other email apps, Outlook lets you personalize these swipe gestures to match your unique email habits. It is simple and amazing 🙂 with a – BUT ONLY FEATURE WITH SWIPE (wish they gave drop down menu for swipe), so if you swipe to left it will Archive (enabled by default) and if you swipe right then it will Schedule (enabled by default) it for you.


Outlook for iOs



Customize Your Swipe SettingsswipeoptiniOS



Add 3rd Party Calendar Apps but still lacking to add someone else calendar in your Exchange / O365 Organization

Here you can add 3rd party calendar apps such as Facebook Events etc. I’m surprised here that why Microsoft Office 365 Team was in a rush to put these social media event/calendar App instead of adding the feature to add multiple Exchange calendar which more productive for any type of business. 



Apps Links (I believe this App is still on AWS and stores your password – If you are security freak like me then I’d not recommend, atlas not for you corporate email account)