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

Setup your Exchange lab in less than $50 bucks

This tutorial will guide you on having a full Exchange environment in the cloud following best practices, Basically to setup your Exchange lab in less than $50 bucks – Prior to this lab I had setup a lab at my home running tons of memory and disk storage but getting a live production like lab is not easy to setup where you want to setup the #OWA and #ActiveSync and test these services externally.

Taking advantage of the fact that there are high competition between cloud service providers, After long evaluation and personal testing I picked the cloud provider that will meet all the requirements. So I decided to go with #VPSIE (vpsie). In this post I will not be doing too much technical stuff but I’m going to put the screen capture and how does it look like once you register. Signup-Link — I liked this one not only because of the best pricing  but also they offer Windows server on all their packages with  #SSD (by default in their all offering). For any version of #Exchange #server SSD makes a huge difference.

You many not need to setup a live lab like this for #DAG but for other service yes it does help a lot.

It also gives you the console level access directly from the browser without installing any Java or add-ons which is neat for troubleshooting as well as their live support. Let’ s start by looking at the lab at my domain name in this case is https://mail.O365SME.COM

owa

 

Package selection would be minimal required for this lab environment – Spike package would be sufficient for our lab.

VPsie1

LAB Servers

In this lab I’ve setup only one AD Server and One Exchange 2010 SP3 – You can see the RAM and and the Disk allowed to each.

To protect Active Directory I have set it up on private network while it can only communicate with Exchange over private link – It’s a very bad idea to have AD on public Internet that is definitely not recommended  for any production use.

OS Selection:

I selected Windows Server 2012 R2 Standard edition for this lab – It comes already activated so

pic3

This is the actual look of my account configured for this lab.

VPsie3

 

It took 2 minutes to spin up each of the Windows servers – After Spinning up – I logged in to console to configure AD as the DNS and do basic configurations that we will get to in details.

Console Access – Coolest Feature 

This feature I must mention here which I’ve not seen using #azure (I am not compare with #azure but wish if they offered that feature). Many time it happens what if the server is not accessible  over remote desktop?    I’ve ran into the situation where I lost access to the RDP and I had de-allocate and re-allocate the machine. Reboot the machine a number of times to made it work. Console Feature , let’s you login to the console just like logging in via KVM. It just simply work on the web browser (safari, firefox and IE). Even if you have to change the port for the RDP you can make the changes via console access and RDP on that port.

Another good and important feature is Private IP (I’ll talk about more details later). So even if you have a private ip on you VM you can still access it via console access, you don’t really need a public ip to access that machine.

What you can achieve with this , you don’t have to publish that server on the public ip address. If you were to put an AD server for your Exchange Server then you don’t need a public ip address on that server. You can access that server on the private ip using console access over a browser.

VPsie5

 

The actual console will look like that, Within a browser window – Very neat:)

VPsie4

 

I wanted to keep the cost for this lab at the lower end – So I started with the lower package and then manually added 10GB of SSD storage individually to satisfy exchange minimal storage requirements  :

modify1

 

Exchange is an application that is streamlined by hands-on experience, To actually learn it you need to do it – you could take advantage of their | Free Trial Now |– As we go with more details on the technical part of this setup I need to have some time to put together some topology graph as well as high level architecture overview. 

“Proof of domain ownership has failed” Exchange Hybrid Configuration Wizard Failure #Office365 #MSExchange #ExchangeHybrid

“Proof of domain ownership has failed” Exchange Hybrid Configuration Wizard Failure –  if you are seeing this error even after your DOMAIN VERIFICATION / OWNERSHIP Status is OK in #Office365 you may need to do some extra effort. There are many articles related for the same problem but they all have different or similar scenario but not exactly. So I cam across a TechNet article the other day (I’ve followed many other blogs too) and there one simple step you need to make sure you copy the current TEXT for the Domain Proof.

Let say your Federation Trust keep on failing then you need to follow this

at the Exchange Shell run this

Get-FederatedDomainProof -DomainName contoso.com
Proof-of-Domain

copy all the proof text  ending with ==

and create a new Text Record for that domain- Now if you run the wizard again it will run successfully

FEd-Trust

 

Exchange 2010 – eDiscovery editing will delete your previous search results

If you happen to edit an existing search result in Exchange 2010 eDiscovery you better create a brand new search as there is no SAVE AS  option BUT there is a WARNING that ‘ you will lose your any previous search results’ if click YES your previous search results are gone from discovery mailbox

6

 

Search1 has no content and the contents of Seach2 are being displayed

 

7