Microsoft Exchange Server 2016 deployment on Cloud

Overview

Microsoft Exchange Server 2016 brings a new set of technologies, features, and services to Exchange Server, the messaging platform that provides email, scheduling, and tools for custom collaboration and messaging service applications. Its goal is to support people and organizations as their work habits evolve from a communication focus to a collaboration focus. At the same time, Exchange 2016 helps lower the total cost of ownership whether you deploy Exchange 2016 on-premises or provision your mailboxes in the cloud.

1.Smarter Inbox
Exchange 2016 helps you get more done through faster search and an inbox that is more personalized, more helpful, and more intelligent.

2.Simplified Architecture
A simplified architecture, originally forged in the cloud, combines the mailbox and client access roles, so it’s easier to plan and scale your deployments. Streamlined coexistence with Exchange 2013 means easier upgrading.

3.Better Collaboration
With its new approach to attachments that eliminates versioning headaches, plus other enhancements, Exchange Server 2016 makes working together on documents easier.

4.Mobile Productivity
Exchange Server 2016 powers the latest Outlook experiences on phones, tablets, desktops, and the web so you can get more done, wherever you are.

 

Features

Major Features of Microsoft  Exchange Server 2016

1.Faster Searches
Almost 20% of user time is spent in searching items that you already know or have. So MS Exchange 2016 has lent a helping hand there and cut it short for you. Microsoft has researched users’ searching patterns from Exchange Online and used the info to reduce the time you spend in searching by introducing:

  • Quicker searches
  • Helpful search suggestions
  • More accurate and complete results
  • Built-in search refiners

2.Simplified Architecture
Architecture wise too, Exchange 2016 is seeing a major change. The old Client Access server role and Mailbox server role are now combined into the Exchange 2016 Mailbox Server role. Usage-wise you don’t need to worry since it’s the same old multi-server role, just enforced. However, this means that you cannot install dedicated Client Access server roles anymore. Plus, you won’t be able to use Windows NLB anymore if your servers and configured in Database Availability Group. It is now recommended to use a 7-layer solution and a hardware load balancer for load balancing purposes.

3.OWA and Email Attachments
The new version has introduced side-by-side document editing and viewing to make the user experience better, which means that you can now see a sent email in OWA, the reply you are currently writing and the document in read / edit mode, simultaneously. Plus, attaching documents is now easier with the last modified documents from email drafts directly available for inclusion. It is also easier to upload documents to OneDrive and change their permissions on the go. Enclosed attachments are displayed larger, with more descriptive content and are directly editable by the recipient.

4.Storage Improvements
The working of the Extensible Storage Engine (ESE) or the Exchange database engine has been improved and Microsoft now recommends using the ReFS (Resilient File System) instead of NTFS.

5.Storage Improvements
The working of the Extensible Storage Engine (ESE) or the Exchange database engine has been improved and Microsoft now recommends using the ReFS (Resilient File System) instead of NTFS.

6.Access on Mobile Devices
Thankfully (and after much waiting), Outlook is arriving on Windows 10, iOS and Android devices and that too with much better productivity. Key highlights include:

  • 2 tabs for email reading
  • Windows 10 gestures
  • Quick filter to find emails faster
  • Calendar improvements and more.

7.Default protocol – MapiHttp
The default protocol for Outlook clients to connect to Exchange 2016 is MapiHttp. Moreover, Outlook Anywhere has been deprecated. However, you can still use it for Outlook 2010 (SP2 or higher). For MapiHttp, Outlook 2013 SP1 or higher is needed.

8.Extremely easy coexistence with Exchange 2013
This one is obvious. It has already been established that the two Exchange versions are very close together; so naturally, coexistence between the two is very easy. Exchange 2013 Client Access can proxy requests to Exchange 2016 Mailbox and vice versa is directly possible. All you need to do is add Exchange 2016 servers to an existing array of Exchange 2013 Client Access server that is load balanced and continue working as usual. The location of the user’s mailbox won’t matter; everything is fully transparent.

Other Hybrid Improvements
A number of hybrid improvements have also been added to remove Hybrid hassles. These include:

  • Secure mail routing
  • Unified address list
  • Free/Busy calendar sharing
  • Single OWA URL
  • Mailbox move
  • Unified message tracking
  • Cross-org MailTips
  • Multi-mailbox search
  • Additional Features
  • Additionally, new features also include options to use some specific features from the Cloud while staying on-premise. For instance, Advanced threat protection and Predictive coding for eDiscovery.

9.Remain in Control
Exchange lets you tailor your solution based on your unique needs and ensures that your communications are always available, while you remain in control. Move to the cloud overnight, deploy on-premises, or manage a hybrid deployment with mailboxes that are both online and on-premises. Manage powerful capabilities, including data loss prevention and Office 365 Groups Tooltip with requirements for Office 365 Groups, from the easy-to-use, web-based Exchange admin center. Role-based access helps you manage Exchange efficiently and delegate tasks. With Exchange archiving, large mailboxes, and retention policies, your users can keep important data in one place and you can take control of your storage and compliance demands.

10.Protect your Organization
Exchange helps protect business communication and sensitive information, simplifying internal and regulatory compliance. Built-in defenses against viruses, spam, and phishing attacks actively protect your communications. Data loss prevention features identify, monitor, and protect sensitive data through deep content analysis, and Policy Tips in Outlook inform users about policy violations before sensitive data is sent. Your compliance officers can run In-Place eDiscovery across Exchange, SharePoint, and Skype for Business from the eDiscovery Center Tooltip with availability of eDiscovery in select Office 365 plans to identify, hold, and analyze your organization’s data. The data always remains in place, so you never have to manage a separate store of data.

AWS

A) Template Deployment: Please choose appropriate options for deployment of template.

Choose your Domain FQDN and other details for AD deployment which the template does and take a note of the Domain username and password.

After deploying the template which takes about 3 hours, check the Output of the template.

You will get RDGW1ElasticIP and RDGW2ElasticIP

After you connect to one of the RDC of Remote Desktop Gateway you shall be able to connect to the Exchange servers.

If you have used the default values

Exchange Server 1 IP:10.0.0.150

Exchange Server 1 IP:10.0.64.150

Please note that username for EDGE server is Administrator and password is same as what you chose for your domain login.

Please note the below detailed information on how to login to the exchange servers.
RDGW1 and RDGW2 are the Remote Desktop Gateway machines to connect to other machines.
Once you RDC to RDGW1 / RDGW2, you should connect to other machines with Internal LAN IPs
Example:
To access EXCH1 use 10.0.0.150 from inside the Remote Desktop connection of RDGW1
To access EXCH2 use 10.0.64.150 from inside the Remote Desktop connection of RDGW2
Similarly use the Internal LAN ips for connecting to EDGE1 and EDGE2
You can use the AD login to connect to the DC and EXCH servers
Example: Yourdomain\Stackadmin .
Please use the actual values for Yourdomain, Stackadmin and password which you have used when creating the template.
To test, once you login to exchange server EXCH1/EXCH2 go to start and search for Exchange.
Choose the Exchange Administrative Center

Since the certificates are to be set later please choose to ignore the warning,
And login with the stackadmin credentials
Please note For EDGE server user name is Administrator and the password is the password which was set by the user for StackAdmin during template deployment.

For EDGE1 the login will be edge1\administrator and password set for StackAdmin
For EDGE2 the login will be edge2\administrator and password set for StackAdmin

B) RDP Connection: To connect to the operating system of Remote Desktop Gateway:

1) Connect to virtual machine using following RDP credentials :

  • Hostname: PublicDNS  / IP of machine
  • Port : 3389

Username: To connect to the operating system, use RDP and the username is Administrator.(or your domain login)
Password : Please Click here  to know how to  get password .

You can use the AD login to connect to the DC and EXCH servers
Example: Yourdomain\Stackadmin .
Please use the actual values for Yourdomain, Stackadmin and password which you have used when creating the template.
Please note For EDGE server user name is Administrator and the password is the password which was set by the user for StackAdmin during template deployment

C) Other Information:

Once you connect to the RDC of your exchange servers via Remote Desktop Gateway you can access the toolbox and admin panel of exchange server. Go to start and search for Exchange 2016

You shall be able to see server setting as shown below:

 

Topology Diagram AD Exchange 2016 Design

 

Microsoft Exchange Server 2016 deployment on Cloud