Exchange 2013/2016 Installation will be BLOCKED If?

Yes this will happen in Jun ’18 release of Exchange cumulative update and after that If your system does not meet requirements which included .NET Framework 4.7.1 it would not allow to you install either exchange 2013 or Exchange 2016.

So make sure in the next few months you do testing in your lab environment and make sure it goes through you change management process (if any) and get the system ready. This is major update. At this point it not clear how or what will happen if you have existing Exchange 2013/2016 without .NET Framework 4.7.1 and new Servers installed after June ’18 with .NET 4.7.1.

I will update this post as soon as I hear back from Exchange product team, till then stay tuned.

Exchange Team Blog

Released: December 2017 Quarterly Exchange Updates

 

Recent Release

KB articles that describe the fixes in each release are available as follows:

Reminder for Hybrid

In hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., 2013 CU19, 2016 CU8) or the prior (e.g., 2013 CU18, 2016 CU7) Cumulative Update release.

Microsoft Tech Summit 2016-2017 is right here

 

 

 

 

 

 

Are you ready for another exciting event with fresh content?
MS Tech Summit is  a TWO DAY  free technical event.

Am I attending – Yes I’m attending the D.C. event
Why Am I attending – If you remember Microsoft iGnite had very first event like this in D.C. 4-5 years ago and then later it became the only event (combined TechEd, MEC etc) for IT Pro and Dev.

Are there any Microsoft Exchange Related Topics? Yes there are a number interesting labs

 

Why Attend? still not sure

Well it has
Keynote from Julia White
Ask the experts
Technical Session

 

 

 

 

 

 

 

 

 

 

 

 

 

Over  all this event has everything for everyone who is practicing either SharePoint, Exchange, Office 365, Lync or Skype for Business.  I’m expecting this event to have fresh content developed from last years’s iGnite and Now.  See there!

https://www.microsoft.com/en-us/techsummit/washington-dc.aspx

 

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.

 

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

Wednesday, January 17th 2018

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.

 

Exchange Server 2013/2016 Components in an Inactive State

Wednesday, January 17th 2018

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