It is time to upgrade – End of life Exchange 2007

Exchange 2007 End of Life Roadmap

Do you know that April 11 2017 is the date when Exchange 2007 will no longer be supported by Microsoft.

If you haven’t already begun your migration from Exchange 2007 to Exchange 2016 or Office 365 now’s the time to start your planning.

What does End of Life 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 Life. When Exchange 2007 reaches its End of Life on April 11, 2017, 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 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible.

Benefits of upgrading to Exchange 2016

Simpler and Better Server Architecture – Single Server Role
Better Collaboration
Saving files to OneDrive for Business
Uploading a file to OneDrive for Business.
Most Recently Used lists populated with both local and online files.
Office 365 hybrid
Messaging policy and compliance
In-place Archiving, retention, and eDiscovery
Improved performance and scalability
Auditing
Antimalware protection
Integration with SharePoint and Skype for Business

What are upgrade options?
#1-You can migrate to Office 365
#2- If you don’t want to migrate to cloud then you can upgrade to either Exchange 2010, Exchange 2013 or Exchange 2016.

I still have more questions, where do I get more details?
Follow this url – https://support.office.com/en-us/article/Exchange-2007-End-of-Life-Roadmap-c3024358-326b-404e-9fe6-b618e54d977d

 

 

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. 

NJ Unified Communication UG July Event

Exchange 2003 to 2010 Role Transfer and Removal Challenges

Event : July 17th 2014 – MS Lync

Vendor Intro – First 10 min

Agenda for Exchange  by Prabhat Nigam
Overview-Exchange 2003 vs 2010 changes
Exchange 2003 to 2010 Migration overview
Exchange 2003 Removal Challenges
Exchange 2003 Role Transfers
Best Practices
Summary
A Microsoft LYNC will be sent via email and published here 1 day before the event.

Sizing Your Exchange 2013 and 2010 – NJ User Group Event

Thursday June 19th 2014 at 6:00 PM
—————————————————
This event is part of our monthly user group meeting and topic of the month is Sizing Your Exchange 2013.  So If you

NOTE : Microsoft Exchange team released a new storage calculate which uses MAPI/HTTPS - it has significant impact on hardware resources. Let's find out

Are you in the process of migrating to new ms exchange 2013 and not sure how to design the new server?

Do you have the challenge to come up with the right hardware required for the new Exchange ?

Do you have the challenge whether virtualize it or not?

If answer is yes then join the session and learn how can you design your new exchange.

Check out our Blog  – http://www.njucug.com/blog

Check out our Meetup Site  – http://www.meetup.com/NJ-Unified-Communication-User-Group

 

Basic Steps to setup your very first email system

Move often asked what it need to setup a running/testing email server? What do I need to do after I install the Exchange 2013/2010 Server. Below are some basic steps I mean basic not all. If this is your very first time you will need to set it up before or after you install the Exchange Server 2013/2010 and then follow the instruction on Microsoft TechNet for Exchange Server

#1. Get the Domain name from the registrar e.g. CONTOSO.COM from Godaddy or any domain reseller
#2. Get the Public IP for your Exchange server from your networking team or ISP
#3. Now Ask the registrar to create the DNS Records for you and point them to your internet IP

example your IP is 10.20.30.41 have them create

A  Record mail.contoso.com 10.20.30.41
CNAME  Record autodiscover.contoso.com
CNAME Record owa.contoso.com
MX  Record mil.contoso.com
Add Accepted Domain in Exchange Server
Configure the Email Address Policy
Create a SEND Connector
Install the digital certificate on Exchange (which you bought from Godaddy)
Configure the IIS and SMTP Service on the cert
Set the Virtual directories

When you think everything is configured properly then test it – http://www.TestExcangeConnectivity.com

http://technet.microsoft.com/en-US/library/jj218640(v=exchg.150).aspx