Posts tagged: Exchange 2010

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.

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. 

Exchange 2010 – eDiscovery editing will delete your previous search results

comments Comments Off on Exchange 2010 – eDiscovery editing will delete your previous search results
By , July 24, 2014 6:47 AM

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

 

 

Reset Exchange 2010 Virtual Directories via GUI

comments Comments Off on Reset Exchange 2010 Virtual Directories via GUI
By , April 24, 2013 10:00 PM

Whenever there is an issue to talk about troubleshooting OWA which results in resetting  the virtual directories I have always seen the PowerShell version of it but how easy to do it via GUI. so why not to do it 🙂

Goto Exchange — Server Configuration — Client Access – Right Click the Client Access Server and follow the steps below

reset-virtual-dir-1

reset-virtual-dir-2

reset-virtual-dir-3

reset-virtual-dir-4

reset-virtual-dir-5

DO NOT FORGET TO RUN iisrest /noforce on the CAS Server/Servers

Cheers:)

 

Configuring Exchange 2010 CAS HA with Kemp VLM – 7 Steps Only

comments Comments Off on Configuring Exchange 2010 CAS HA with Kemp VLM – 7 Steps Only
By , April 7, 2013 11:12 PM
NJ Unified Communication User Group

NJ Unified Communication User Group

Few weeks back  I wrote an article on Exchange 2013 CAS HA with Kemp which was very interesting to not only to share with the community but also configuring it on my virtual lab. And now this time I have done the same thing but using Exchange 2010 CAS servers. It didn’t really take much time as it has to follow same steps and same concept except this time I had to use Layer7 option to make it work. I will show step by step how easy it is to setup and how quickly you can have your Exchange Environment Highly Available.

In my last lab I was suing Windows Server 2008 HyperV and this time I am using Windows Server 2012 Hyper. I do not have words to explain the experience but all the VMs are amazingly fast and gives awesome performance. If you have not tried then you must give it a try. So upgrading to Hyper 2012 was another experience and VHDs are now VHDX.  So let me show you the STEP BY STEP CONFIGURATION OF EXCHANGE 2010 CAS HIGH AVAILABILITY USING KEMP VIRTUAL LOAD MASTER

So if you run Exchange 2010 and want to make it HA without buying extra hardware Windows Server Hypver 2012 is the way to go.

It took me exactly 7 steps.
Make sure your individual CAS server fully functional and the DNS is configured appropriately.

ex2010-01

 

ex2010-02

ex2010-03

 

 

 

 

 

ex2010-04

 

ex2010-05

ex2010-06

 

ex2010-07

 

ex2010-08

ex2010-09 ex2010-010

 

Cheers 🙂

 

 

 

A closer look at the DG Properties in Exchange 2010 Vs Exchange 2007

comments Comments Off on A closer look at the DG Properties in Exchange 2010 Vs Exchange 2007
By , July 14, 2012 11:36 AM

Exchange 2007

Exchange 2010

Panorama Theme by Themocracy