Category: Exchange 2010

Email Routing in a Hybrid Deployment for O365

comments Comments Off on Email Routing in a Hybrid Deployment for O365
By , August 16, 2019 9:30 PM

What is it ?

If you are migrating your emails to #Office365 and for any reason if you required by your business to route your email via on-premises network infrastructure, this how you want to do this.

Note:
Don’t place any servers, services, or devices between your on-premises Exchange servers and Office 365 that process or modify SMTP traffic. Secure mail flow between your on-premises Exchange organization and Office 365 depends on information contained in messages sent between the organization. Firewalls that allow SMTP traffic on TCP port 25 through without modification are supported. If a server, service, or device processes a message sent between your on-premises Exchange organization and Office 365, this information is removed. If this happens, the message will no longer be considered internal to your organization and will be subject to anti-spam filtering, transport and journal rules, and other policies that may not apply to it.

JAN 14 2020 -One year from today Exchange Server 2010 will no longer be supported

comments Comments Off on JAN 14 2020 -One year from today Exchange Server 2010 will no longer be supported
By , January 14, 2019 3:15 PM

Jan 14 2020 – One year from today Exchange Server 2010 will no longer be supported.

What does end of support 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 support. When Exchange 2010 reaches its end of support on January 14, 2020, 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 2010 will continue to run after this date. However, due to the changes and risks listed above, we strongly recommend that you migrate from Exchange 2010 as soon as possible.

 

What are my options?

We’ve [Exchange PG] created a page (https://aka.ms/Exchange2010EndOfSupport) where we outline options, but in order to stay supported you essentially can;

  • Migrate all mailboxes to Office 365 and remove all Exchange 2010 servers by Jan 2020, making sure any on-premises servers used for administration purposes are on a supported version.
  • Go Hybrid with Office 365, remove all Exchange 2010 servers by Jan 2020 and make sure any on-premises servers are on a supported version.
  • Stay On-Premises and upgrade to a newer version of Exchange Server.

Clearly we think moving to Exchange Online and Office 365 is a good idea. We really do believe that’s where you’ll get access to the most secure and productive software with the lowest TCO. But over and above all of that, and in relation to the subject of this post – it gets you out of the upgrade business. If you migrate fully to Office 365 you really don’t need to worry about these big bang version migrations any more. You just have to make sure you keep a much smaller number of on-prem servers up to date, and you’re good.

If you do want to stay on-premises don’t forget that you cannot upgrade directly from Exchange 2010 on-premises to Exchange Server 2019. You can upgrade to Exchange 2013 or 2016 directly from Exchange 2010 and we recommend you upgrade to Exchange 2016 if you have the choice. It will give you a longer support lifecycle and more features. Given how similar 2013 and 2016 are from a migration standpoint, it’s also just as easy to go to 2016 as it is 2013. So, upgrade to Exchange 2016, and then you have the option to go to 2019 if you want to.

What if I need help?

If you have a complex deployment, or if you just don’t have the time or skills you might need some help. That’s fine, there are plenty of ways to get help.

If you’re migrating to Office 365, you might be eligible to use our Microsoft FastTrack service. FastTrack provides best practices, tools, and resources to make your migration to Office 365 as seamless as possible. Best of all, you’ll have a real support engineer that will walk you through your migration, from planning and design all the way to migrating your last mailbox. If you want to know more about FastTrack, take a look at Microsoft FastTrack.

If you run into any problems during your migration to Office 365 and you aren’t using FastTrack, or you are migrating to a newer version of Exchange Server, we’re still here to help. Here are some resources you can use:

You might choose to engage a partner to help too. We have a great number of partners with deep skills in Exchange, and we’re sure one of them will be able to help you. Start your search here – https://www.microsoft.com/en-us/solution-providers/home

So What Now?

What now? You need to get started if you haven’t already. Time really does fly and Jan 14th2020 is only a year away.

Tick Tock.

Microsoft Tech Summit 2016-2017 is right here

comments Comments Off on Microsoft Tech Summit 2016-2017 is right here
By , February 19, 2017 10:26 PM

 

 

 

 

 

 

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

 

Exchange 2013/2016 Cumulative Updates and Hybrid Environment.

comments Comments Off on Exchange 2013/2016 Cumulative Updates and Hybrid Environment.
By , June 21, 2016 4:23 PM

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

Microsoft Exchange Server Deployment Assistant – Need Some Improvements

comments Comments Off on Microsoft Exchange Server Deployment Assistant – Need Some Improvements
By , May 9, 2016 7:45 AM

[mp_row]

[mp_span col=”12″]

The Exchange Server Deployment Assistant is a web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios.

Screen Shot 2016-04-26 at 9.53.40 PM

Microsoft Exchange Product Team has done a phenomenal job introducing this tool and keeping it updated on regular basis.  While I was working on some scenario I figure there need to be some re-ordering and and couple of new links needs to be added. Hope it make sense to ExchangeTeam 🙂

I’ve selected On-Premises Scenario

Screen Shot 2016-04-26 at 9.55.20 PMScreen Shot 2016-04-26 at 9.55.40 PM

Next I selected
Disjoint namespace – No
Migrate Public Folders – Yes
Edge Co-Existance – No

Next you will see the navigation checklist
Screen Shot 2016-04-26 at 10.17.21 PM

Suggestion #1 Re-Order Service Connection Point (SCP)

The improvement I’m talking about is SCP order should be either in Install Exchange 2016 OR or Should be the 2nd step in Configure services. I think it has to be be the next step right after you install the Exchange Server 2016

configure_scp

 

Suggestion #2 – In Finalize Your Deployment – Add More Steps or link into that section.

Screen Shot 2016-04-26 at 10.21.21 PM

Modify or Remove Exchange 2010, this link only cover the scenario where you have only one mailbox server or mailbox server with Database Availability. It does not cover the details if the legacy Exchange Server 2010 has Database Availability Group. So to cover a DAG scenario those two link are very important. and it has to be part of the deployment assistant in my opinion.

 

 

[/mp_span]

[/mp_row]

Setup your Exchange lab in less than $50 bucks

comments Comments Off on Setup your Exchange lab in less than $50 bucks
By , March 30, 2016 10:19 AM

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. 

Panorama Theme by Themocracy