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.

screen-shot-2016-11-05-at-12-28-35-pm

 

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

screen-shot-2016-11-05-at-12-24-15-pm

Stay Tuned with Exchange Blog

https://blogs.technet.microsoft.com/exchange/

 

Notes From Microsoft iGnite 2016 #msignite

Running from Hall A to Hall C and then back to Hall A I needed up walking/running approximately 4 miles (6 km) per day, yeah it was good cardio J

I went there to learn more about on-premises Exchange Server 2016 and Hybrid configuration with Office 365 BUT was not quite impressed though you search the sessions you will find approx. 57 sessions on EXCHANGE but most of the are just Office 365 features and product marketing. It looks like iGnite email related (messaging) content were focused to a specific customer market or in other words they ignored the large enterprise customer running complex exchange environment.

I’d also mention that there were some sessions which I liked most and one of them was just specific to Office 365 but it is related to on-premises stuff (Below is the list of sessions I liked most or in other word 5/5 on the score card).

Challenge cloud encryption myths and learn about Office 365 BYOK plans
Yes, now you can bring your own keys.  Very information session from Jaclynn.

Migrate to Exchange Online via Exchange Hybrid
2nd session of the day for Hybrid.  Tons of information, must watch Tim and Mike did an awesome job.  And yes don’t forget to run the RCW on-premises.

Meet twin sons of different mothers (MVPs and Exchange engineers). It was a very interactive session carried out by Tony Redmond with folks from Product Team (Karim Battish and Jeff Mealiffe) and Exchange MVP (Andrew Higginbotham and Jeff Guillet). The room was full of on-premises Exchange Enthusiast.

The Ultimate Field Guide to Office 365 Groups. Microsoft gave a lot of information at Ignite about future developments for Office 365 Groups. This session provided a counterweight in that it focused on how groups are used in the field. This session was carried out by Tony Redmond and Bejamin Niaulin.

Unplug with the experts on Exchange Server and Exchange Online
Another interactive session. Discussion on on-premises, Modern-Auth, ADFS and Hybrid

 

So to conclude that overall it was a busy event, specially with running from one hall to another (wish they plan it better next year). Other than attending these breakout sessions I got most of questions answered by meeting the product team at the booth, I spent HOURS with them.

 

Office Document Editing using Office Online Server 2016 with On-Prem Exchange 2016

Product covered – Office Online Server 2016 and Exchange 2016 CU2

Summary/Goal – Achieve document editing using a web browser without having desktop version of MS Office 2016

 

Like Office 365 document editing, you can also setup your infrastructure for the on-prem document editing . The end-user does not require desktop version of Microsoft Office.

In this lab, I’m using a 3rd party ssl certificate and all the domain name are FQDN.
Exchange URLS  https://mail.office365sme.com, auto discover.office365sme.com 
OOS Server URL https://oos.office365sme.com 
Friendly Certificate name The Office 365 SME

 

Begin Installation

Office Online Server 2016

If you see the same error as I did then install the particular KB, once installed it will dis-appeared as below

Screen Shot 2016-07-22 at 3.00.49 PM

Screen Shot 2016-07-22 at 4.08.16 PM

 

Now setup your OfficeWebApp Farm as below – As mentioned above I’m using the same url. These are my lab urls–

Screen Shot 2016-07-22 at 4.10.32 PM

It FAILED, because the certificate name was type incorrectly. I ran the same cmdlet agains with the correct Certificate Name ‘The Office 365 SME’

Screen Shot 2016-07-22 at 4.29.04 PM

Setting up Exchange 2016 Server to integrate with Office Online Server 2016

Screen Shot 2016-07-22 at 4.36.06 PM

Verifying the above integration –

https://oos.office365sme.com/hosting/discovery

Screen Shot 2016-07-22 at 5.24.57 PM

 

Viewing / Editing the Document Online via browser on your On-Prem Exchange 2016

Screen Shot 2016-07-22 at 4.37.54 PM

 

Screen Shot 2016-07-22 at 4.38.24 PM

 

Cheers 🙂

Now your on-prem Exchange 2016 offers you the same feature (one of them) as Office 365.

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 – http://www.expta.com/2016/06/exchange-2016-cu2-and-exchange-2013.html (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

Monday, February 19th 2018

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.
pic1
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.
pic3
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.
pic4

 

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

 

6. Click Close when the confirmation message appears.
pic6

 

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).
pic7

 

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

 

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

 

10. Provide the Office 365 credential when prompted.
pic10

 

11. Click Close after the completion of the process.
pic11

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.
pic12
3. Provide the Office 365 login credentials and choose the connecting option; click Next. Click Finish when the connection is established.
pic13
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.
pic14
5. Right-click on the mailbox and select Export Message(s) > PST.
pic15
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.
pic16

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

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

Exchange 2016 Install – Step by Step

This blog post is specially for those who are planning to install Exchange 2016 and wanted to get an idea. There is nothing special installing the Exchange Server 2016 but of course there a a lot of planning involved if you are doing a migration project from Exchange to Exchange Migration or Exchange to O365 or a Hybrid setup.  This install is a step by step (screen shots) for Exchange 2016 installation.  2

The server OS is Windows Server 2012 R2 running on my Hyper-V 2012 R2 Host.
To install the pre-requisites and automate the installation I’ve used Michel de Rooij’s script. I recommend using that script , it save a lot of time.

Screen Shot 2016-04-22 at 5.16.37 PM Screen Shot 2016-04-22 at 10.21.29 AM Screen Shot 2016-04-22 at 10.22.07 AM Screen Shot 2016-04-22 at 10.22.44 AM Screen Shot 2016-04-22 at 10.23.54 AM Screen Shot 2016-04-22 at 10.24.04 AM Screen Shot 2016-04-22 at 10.24.33 AM Screen Shot 2016-04-22 at 10.24.53 AM Screen Shot 2016-04-22 at 10.25.05 AM Screen Shot 2016-04-22 at 10.25.16 AM Screen Shot 2016-04-22 at 10.25.26 AM Screen Shot 2016-04-22 at 10.25.38 AM

Below Error is the DotNet Framework Error. As soon as I manually installed the DotNet Framework 4.5.2 I was able to proceed the installation.

Screen Shot 2016-04-22 at 10.26.19 AM Screen Shot 2016-04-22 at 11.29.22 AM Screen Shot 2016-04-22 at 11.29.32 AMScreen Shot 2016-04-22 at 5.16.37 PM

Screen Shot 2016-04-24 at 12.26.24 AM

Cheers ! Now you have successfully installed the Exchange Server 2016