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

Removing Add-ins from Outlook in Office 365 – 3rd Party Data Sharing and your corporate network

Sunday, June 26th 2016

In my last post I’ve talked about installing the 3rd party Add-ins in Outlook for Office 365. As I said there are many Add-ins from embedding google search into Word, printing email as a PDF etc. I’m more concerned about Add-ins in #Outlook because you don’t what these 3rd party reads your data , I mean your email data unless you read each 3rd part’s privacy terms and condition. So if you are concerned about security like me or dealing with a an enterprise environment then these add-ins may not work you. some of them will such as Bing , Google but printing email as print etc may not work.

So I’ll walk through here removing these add-ins

Screen Shot 2016-04-12 at 4.25.53 PM

Office365

Office365

Screen Shot 2016-04-12 at 4.50.56 PM

If you notice that Uber add-ins is not there.

 

Announcing Exchange ActiveSync version 16.1

Sunday, June 26th 2016

Microsoft Exchange has just announced support for EAS Protocol version 16.1 on their blog.

They have introduced three new major capabilities

  1. Improved Keyword Search – Get quicker, more relevant results when searching your inbox. Clients can now perform Keyword Query Language searches (from, to, subject, etc.) by using the new Find command.
  2. Propose New Time – Users have asked for the ability to propose a new time for a meeting while on the go, and we have added full support for new time proposals in EAS 16.1.
  3. Account-Only Remote Wipe – Administrators can now request clients using EAS 16.1 to wipe only Exchange data from a user’s device.

Customers with their mailbox in Office 365 can take advantage of these new features when their favorite EAS client is updated.

How do you know your mailbox is supported with the new EAS Protocol?

As an end user, how can you tell if your mailbox is enabled for EAS version 16.1? The simplest way is to run an “Exchange ActiveSync” test at https://testconnectivity.microsoft.com and look for version 16.1 listed as one of the supported protocol versions (MS-ASProtocolVersions header in the OPTIONS command response) in the test results. Note that you need a valid Office 365 email address and password in order to run that test, and the results are specific to that mailbox only (not the entire tenant).

Checking EAS Version using Exchange Remote Connectivity Analyzer

Office 365

 

Screen Shot 2016-06-14 at 9.20.21 PM

 

Screen Shot 2016-06-14 at 9.20.32 PM

 

Screen Shot 2016-06-14 at 9.21.59 PM

If you see here (above), it show that the my mailbox has the EAS 16.1 version.

How to Check EAS 16.1 on you Mobile Device? 

In my case I’m using iPhone 6.0, and the app below shows that these capabilities are available.

Office 365

 

Outlook APP

If you only OWA APP for Exchange is capable of doing these new feature. Outlook App and iOS default Exchange and Outlook can’t perform these features. I believe #Apple will have to support it. But i wonder why only one OWA APP is supporting EAS 16.1 and why not Outlook APP.

Office 365

Photo 5

In my opinion it would have been  perfect if it supports the native client on iOS which dominate most of the mobile market. I’m not sure about Windows Phone and Android Phones. I believe Apple will get it fixed while I still have to hear from someone if these new capabilities are possible on Windows Phone.

Microsoft Blog URL for EAS 16.1 

And this is how you can also verify your EAS Version of you mailbox using Office 365 Admin Panel

Office365

 

Exchange Server 2013/2016 Components in an Inactive State

Sunday, June 26th 2016

updated – I  made this post more than a year go when I encountered an issue doing maintenance on Exchange Server 2013. Coming from Exchange 2010 maintenance experience it was a quite a different change and for some time I was not sure why the service were not coming backup online. And then it was all related to Exchange 2013/2016 Managed Availability. When I looked it up (only possible via Powershell) I fond that all the services were in InActive State.

You can also use the script to bring the component state back to active state
http://gallery.technet.microsoft.com/exchange/SetExchangeComponentToActiv-874bcd4b

Original post from 08/7/2014
After applying update or patches on Exchange 2013/2016 and bringing back to out of maintenance you notice that server components are still Inactive as shown below.  In a situation like this you need to go extra mile to bring the server as is before maintenance. Below is the set of cmdlet when you put the server on maintenance where requester is calling for maintenance.

cmdlets/ script is bringing the server out of the maintenance but the component state is still Inactive
Set-ServerComponentState $Server -Component ServerWideOffline -State Active -Requester Maintenance
Set-ServerComponentState $Server -Component UMCallRouter –State Active –Requester Maintenance
Resume-ClusterNode $Serve
Set-MailboxServer $Server -DatabaseCopyActivationDisabledAndMoveNow $False
Set-MailboxServer $Server -DatabaseCopyAutoActivationPolicy Unrestricted
Set-ServerComponentState $Server -Component HubTransport -State Active -Requester Maintenance

maint1

In addition to the single components which can be managed individually, there’s also a component called “ServerWideOffline”, which is used to manage the state of all components together, with the exception of “Monitoring” and “RecoveryActionsEnabled”. For this purpose, “ServerWideOffline” overrides individual settings for all other components. It doesn’t touch “Monitoring” and “RecoveryActionsEnabled” because these two components need to stay active in order to keep MA going. Without them, no “OnlineResponder” could bring “ServerWideOffline” back to “Active” automatically. But in this case both Monitoring and RecoveryActionEnabled are Inactive which will not bring the ServerWideOffline back to Active.

 So the server is not 100% functional even though you took it out of maintenance. You will need to perform  the following cmdlet to bring the server in ACTIVE State

Set-ServerComponentState -Component ServerWideOffline -State Active -Requester Functional
Set-ServerComponentState -Component Monitoring -State Active -Requester Functional
Set-ServerComponentState -Component RecoveryActionsEnabled -State Active -Requester Functional

maint2

 

You can also get  the Get-ServerComponentState cmdlet from the Shell to retrieve these settings along with timestamp

maint7

You can also use the script to bring the component state back to active state

http://gallery.technet.microsoft.com/exchange/SetExchangeComponentToActiv-874bcd4b

 

 

How to export Office 365 mailboxes to Outlook PST

Sunday, June 26th 2016

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.

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.

SWIPE LEFT

Outlook for iOs

SWIPE RIGHT

ORight

Customize Your Swipe SettingsswipeoptiniOS

swipeleftsett

swiperight

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. 

calendar

 

Apps Links
https://itunes.apple.com/us/app/owa-for-iphone/id659503543?mt=8 (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)

https://community.office365.com/en-us/w/mobile/owa-for-iphone-and-owa-for-ipad

https://blogs.office.com/2015/01/29/deeper-look-outlook-ios-android/#t07RFZwMsz3xqIOR.97