Comparison and Coherence of Exchange 2016 with Exchange 2010
Those who are looking to migrate over to Exchange 2016 are currently using Exchange 2010. Hence it is important to acknowledge the changes coming in Exchange 2016.
- This is imperative for Exchange 2010 users as Exchange 2016 has several architectural changes. Several features have been added and removed.
- Towards this phase of transitions, all the migrants of Exchange 2010 to 2016 migration would like to know and explore the changes user is likely to face via user point of you. This will update and prepare you to communicate and prepared for new alterations and avoid any outages.
New functions in compare to Exchange 2010
Exchange Management Console:
- EMC will depict very limited tool unlike Exchange 2010. And, Microsoft had noticed the delayed update in EMC and then decided for better Admin console that will be used in Exchange 2016 to manage via GUI.
Exchange Admin Center:
- Microsoft exposes you with Exchange Admin Center in Exchange 2010 in the context of Exchange Control Panel and in Exchange 2013 we received all configurations to EAC. And same continues in Exchange 2016. You are allowed to connect from anywhere to you EAC using a web browser.
- This is one console for all. And the Public Folders are mailboxes hence no separate console are needed. Many GUI features have shifted to Exchange management shell like Queues. Also, EAC refresh is comparatively quicker than Exchange 2010 Exchange management console.
Architecture of Exchange 2016:
- Exchange 2016 reduced to 2 Roles that can’t be installed together. You may have assumed it Mailbox Role and Edge Transport Role.
- Hub Transport, Unified Messaging and Client Access functions have been merged to Mailbox Role. Hence, it is time to say good bye to Hub Transport, Unified Messaging and Client Access Roles.
- Mailbox Server Role is going to permit POP, HTTP, IMAP and SMTP client access protocols. This implies time to say goodbye to RPC and RPC CAS Array.
- The role of Edge the transport role is upcoming in the RTM version. Hence no longer SP1 wait.
The benefits of the Exchange 2016 architecture:
Flexibility to Upgrade:
- Unlike Exchange 2010 we primly have one role hence we don’t have to worry regarding which server role must be patched first.
- We used session affinity In Exchange 2010 for many protocols that is unrequired as we have CAS and mailbox role on the same server.
- In comparison to Exchange 2010, their exist less number of namespace requirements. Only one for protocols and only one for autodiscover are required.
- Outlook may connect only by using Outlook Anywhere with either MAPI over HTTP or RPC over HTTP.
- Mailbox high availability is still offered by Database Availability Group that has reduced failover time.
- The Exchange Store service has been re-scripted in managed code.
- Every Database executes under its own process that permits the isolation of store issue on a single database.
- In Exchange 2016 Information Store consists of 2 processes
- Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe also known as Managed Store.
- The Managed Store is scripted in C# and integrated collaboratively with Microsoft Exchange Replication Service. It offers improved resiliency.
- Managed store might also enable greater granular management of resource utilization and faster root cause analysis via improved diagnostics
- Managed Store manages mailbox databases via Microsoft Exchange Replication Service and that continues to use old and favorite database engine Extensible Storage Engine (ESE). Microsoft Exchange Replication Service is more responsible for mailbox servers service availability.
- Managed Store also empowers faster database failover and enhanced physical disk failure handling.
- Managed store is collaborated and integrated with the search Foundation Search Engine that offers more robust indexing and search.
In Exchange 2010 we need to install certificate per server from Exchange Management Console. In Exchange 2016 you are allowed to install certificate into multiple servers in one go using Exchange Admin Center. You will also note the certification expiry notification in EAC as well.
Enhanced Readiness Checks:
- Readiness checks validations run faster than earlier Exchange setups and it is able to install required windows features.
Easy, Simplified and modern wizard:
- Only needed steps left in the setup wizard.
Office 365 Hybrid
- The Hybrid Configuration Wizard that was included in Exchange 2013 has become a cloud-based application. You are allowed to download and install the Hybrid Configuration Wizard, In Exchange 2016.
The wizard is going to perform function same as Exchange 2013, expect few new merits:
- The Hybrid Configuration wizard may be updated faster to support changes in the Office 365 service.
- Existing wizard can be updated to account for related issues detected when you try to setup and configure a hybrid deployment.
- Enhanced diagnostics and troubleshooting to resolve appearing issues which came while running the wizard.
- The same wizard will be utilized by all configuring a hybrid deployment, in case they are using Exchange 2013 or Exchange 2016.
- Multi-forest hybrid deployments have turned simple when we use Azure Active Directory Connect (AADConnect). And AADConnect introduces management agents which will make it potentially easier to synchronize multiple on-premises Active Directory forests with a present single Office 365 tenant.
Novice New Authentication:
- Hybrid deployments are going to support the new modern authentication model over the Outlook.
- Exchange ActiveSync clients will then be seamlessly redirected over to Office 365 when a user’s mailbox is shifted from on premise to Exchange Online. The mentioned Exchange ActiveSync clients must support HTTP 451 redirect.
Outlook over the Web (OWA was the old name):
- Outlook web app is novice new Outlook over the Web
It is going to support Microsoft Edge, Internet Explorer 11 and current updated version of Mozilla Google Chrome, Firefox, and Safari Browsers.
The following new functions will be appended:
- Platform-specific exposures and experiences over phones for Android and IOS in particular.
- Premium Android exposure and experience for chrome on Android version 4.2 or later devices.
- A novice new single-line access of the Inbox with an optimized reading pane, archiving, emojis, and the ability to undo mailbox actions for example moving a message or removing a message.
Contact linking: Users are allowed to add contacts from their LinkedIn accounts.
- Different new look and new functions, including email reminders for Calendar events, capability to propose a different new time in meeting invitations, birthday calendars and enhanced search.
- Search recommendations and refiners for an enhanced faster search. Search recommendations. Search refiners are going to help a user more easily search the information they’re looking for by offering contextually-aware filters. Filters may consist of date ranges, related senders, and so on.
New distinguish themes:
- With graphic designs 13 new themes.
- Options for individual mailboxes have been revived and renewed.
Pins and Flags:
- This feature allows users to keep necessary emails at the top of their inbox (Pins) and observe or mark others for follow-up (Flags). Pins are usually folder specific, good to use folders to methodically organize emails. Quickly search and manage flagged items with inbox filters or the novice new Task module.
- Performance enhancements in several areas across Outlook over the web, consist of composing messages, creating calendar events, loading messages in the reading pane, startup, search, pop outs and switching folders.
Apps for Outlook:
- Outlook Apps permit users & administrators to extend the abilities of Outlook over the web
- This empowers users to paste a link into messages and Outlook over the web by default automatically generates a enrich preview to give recipients a peek into the contents of the destination. It also works along with video links.
- Hence every link will generate the preview and you have choice to eliminate the preview. Preview is always good to use as it gives the intro of the link.
- You are allowed to use OWA renamed to OOTW in offline mode without internet, In Exchange 2016. This implies you don’t need to however outlook license and you may continue to read and write emails without internet in OOTW. This feature surly going to make you happy.
- This permits you to create offline web applications. And the AppCache enables webpages to cache resources exists locally, including script libraries, images, style sheets, & so on.
- Further, AppCache permits URLs to be served via cached content using standard Uniform Resource Identifier (URI) notation. The following listed web browsers support AppCache and you might use them for OOTW offline mode.
Kindly note this is a key to minimize the office licenses.
- Microsoft Edge
- Google Chrome 44 or later versions
- Internet Explorer 11 or later versions
- Safari 8 or later (only on OS X/iOS) versions
- Firefox 39 or later versions
Backup Support for Modern Authentication for Outlook:
- Exchange 2016 supports and back Active Directory Authentication Library authentication model present in outlook clients on Windows and other OS. ADAL is going to enable 2 factor authentication that helps in securing the data for several security organizations.
MAPI over HTTP
- MAPI over HTTP is the automatic by default protocol in Exchange 2016 that outlook uses to connect and communicate with Exchange server.
- This is more reliable and stable protocol present at the Transport layer of the OSI model that can find higher level transport errors and improve recovery.
- One of the excellent features of this protocol is that it allows pausing and resuming the outlook connection that permits outlook to alter networks and resume from hibernation. They are going to continue to connect using Outlook Anywhere, in case outlook client do not support this protocol.
- If Exchange 2016 id installed in the mixed mode, then you will observe a warning as depicted below while executing Exchange 2016 setup.
- You require to execute the following command to enable it.
Set-OrganizationConfig –MapihttpEnable $true
Now your outlook will display like this.
Collaboration of Document
- Outlook over the web will empower users to link to and share documents saved and stored in OneDrive for Business or in an on-premises SharePoint server in place of enclosing a file to the message. It is very similar to current Office 365 users.
- In case a Word, PowerPoint, or Excel, file saved and stored in on-premises SharePoint or OneDrive for Business is generally included in an email received by a user on Exchange 2016, and the user will now have the choice of viewing and editing that file in Outlook over the web alongside the message (“Office Web Apps vNext” server should be implemented in your on-premises organization to get this function).
- In case you are editing attachment, then user must have an Office client license.
Some more enhancements are coming which are shown below:
- Save a file over to OneDrive
- Upload a file over to OneDrive
- Most currently used lists populated along with both local and online files.
- Exchange 2016 altered the Transport architecture wholly. The brief summary of the changes is depicted below:
- The transport pipeline has many different services, In Exchange 2016: the Transport service, the Front End Transport service, and the Mailbox Transport service.
- Mail routing feature in Exchange 2016 recognizes DAG boundaries also Active Directory site boundaries. And, mail routing has been enhanced to queue messages more directly for internal recipients.
- This feature Exchange 2016 transport dumpster has been enhanced and renamed to Safety Net.
- Safety Net incepted the concept of the Primary Safety Net and the Shadow Safety Net. In case the Primary Safety Net is not present for more than 12 hours, then resubmit requests become shadow resubmit requests, and messages are re-delivered via the Shadow Safety Net.
- Safety Net handles some responsibility from shadow redundancy in DAG environments. And the Shadow Redundancy duplicates email to the Mailbox Server in the 2nd AD site and delay acknowledgement.
- Shadow redundancy do not require to keep another replica of the delivered message in a shadow queue, and while it waits for the delivered message to replicate to the passive replicas of mailbox database present on the other Mailbox servers in the DAG.
- The replica of the delivered message, which is already stored in Safety Net, hence the message can be resubmitted from Safety Net if require.
Check illustration in the flow diagram shown below.
- Connectors The maximum message size, by default for a Send connector or a Receive connector, as mentioned by theMaxMessageSize parameter, has been maximized from 10MB to 25MB. Similar to Exchange 2010 we have send and receive connectors.
- You can fix and set a Send connector in the Transport service of a Mailbox server to direct and route outbound mail via a Front End transport server in the local Active Directory site, by using the FrontEndProxyEnabled parameter of the
Set-SendConnector cmdlet, therefore consolidating how email is routed or directed from the Transport service.
- We may configure FrontEnd Transport or Hub Transport role. And FrontEnd connects over port 25 and Hub Transport connects over port 2525. You may like to bypass FrontEnd hence you need to ensure you sending traffic on port 2525 from spam guard.
- You may continue to use and work on Exchange Edge Transport server. Exchange 2016 comes along with Edge Transport server.
Have a look on Transport architecture picture from shown below :
Prevention of Data Loss:
- Please note DLP has been part of Exchange 2013 success story that is a business standard requirement for several financial org now. DLP has enhanced and added many templates for other countries now. Enhanced DLP in Exchange 2016 can identify, monitor, and protect 80 distinguish kinds of sensitive information.
- The transport rule works at server level and configurable for the entire ORG.
Exchange 2016 is adding following new functions for the transport Rules:
- Now, Exchange transport rules can determine 80 different categories of DLP configuration.
- There is a new different condition “Any enclosure or attachment has these properties, inclusive of any of these words”, has been appended which determines the attachment property for the particular words.
- Such new condition simply and easily integrates Exchange transport rules and DLP policies along with SharePoint Server, Windows Server 2012 R2 File Classification Infrastructure (FCI), or a third-party categorization system.
- There is a new task action appended Notify and alert the recipient with a message. A transport rule might be set to transmit a notification to the recipient with the text mentioned which can communicate the recipient that the message had some challenges, issues and where necessary actions is required.
- There is another new different action Generate or create an incident report and send it to has been updated hence that multiple distribution lists can receive the incident report
- There are few additions in predicates and actions.
In-place Archiving, retention and eDiscovery
The release of Exchange 2016 has appended the following enhancements for In-Place Archiving, retention, and eDiscovery:
Public folder back-up and support for In-Place eDiscovery and In-Place Hold
- Exchange 2016 has coupled and integrated public folders into the In-Place eDiscovery and also Hold workflow. In-Place eDiscovery can search public folders and may put In-Place Hold on public folders, In Exchange 2016.
- We are also permitted to configure a query-based and a time-based hold on public folders. We may only find and place a hold on all public folders at present however, later Cumulative Updates may allow to choose particular public folders to find and place on hold.
- Exchange 2016 has introduced a distinguished novice eDiscovery search tool known as Compliance Search. This tool is able to execute a single search for very huge numbers of mailboxes. There is no set limit on the number of mailboxes, hence all mailboxes can be explored and searched in one search.
- There is no defined limit on the number of searches which can run simultaneously.
- We can execute compliance Search from Exchange Management Shell.
- An administrator or eDiscovery manager should be allotted the Mailbox Search management role or can be a member of the Discovery Management role group to execute the compliance search commands.
- It is a unified hold model that permits you to meet legal hold needs as per the mentioned below scenarios:
- Preserve the outcomes of the query that is also called query-based hold. It permits for scoped immutability throughout the mailboxes.
- Allow and Place a time-based hold to address retention requirements.
- Allow to place a mailbox on indefinite hold. It is the one similar to litigation hold in Exchange 2010.
- Allow and place a user on multiple holds.
- It permits authorized users to search and explore mailbox data across all mailboxes and replicate messages over to a discovery mailbox for review that is similar to Exchange to Exchange 2010 .
- however in Exchange 2016 you may run one query for all mailbox, in Exchange 2010 you require running one query per mailbox. Exchange 2016 In-Place eDiscovery permits discovery managers to execute more efficient searches and hold.
- This Search permits us to search, explore and preserve data through multiple data repositories. You are allowed to perform in-place eDiscovery searches across Exchange, SharePoint 2013, and Skype for Business, in Exchange 2016.
- You are allowed to use the eDiscovery Center in SharePoint 2013 to conduct In-Place eDiscovery search and hold. Off course this search needs federation configuration with SharePoint 2013, and Skype for Business.
Query-based In-Place Hold
- This search permits us to save the outcomes of the query that permits for scoped immutability throughout mailboxes.
Export search results
- Discovery Managers might export mailbox content into a .pst file via the SharePoint 2013 eDiscovery Console. Simultaneously, Mailbox export request cmdlets are no longer needed to export a mailbox to a .pst file.
Keyword statistics Search
- Its statistics are provided on a per search term basis. That empowers a Discovery Manager to quickly take intelligent decisions regarding how to further refine the search query.
KQL syntax Keyword Query Language (KQL)
- Its distinguishlynew feature. Discovery Managers might also use Keyword Query Language (KQL) syntax in search queries. KQL is very similar to Exchange 2010 discovery search’s Advanced Query Syntax (AQS).
In-Place eDiscovery and Hold wizard
- Discovery Managers might use the In-Place eDiscovery & Hold wizard to conduct both eDiscovery and hold operations.
- In case there is no SharePoint, then you are going to have a subset of eDiscovery in the Exchange Admin Center.
- Search throughout the primary and archive mailboxes in Outlook on the web You are not require to run 2 isolated separate searches, “Outlook on the web” may search primary and archive mailboxes in one query.
- Archive Skype for Business content You can archive Skype for Business content from a mailbox, in Exchange 2016. You are also allowed to place Skype for Business content on hold using In-Place Hold & use In-Place eDiscovery to explore or search Skype for Business content archived in Exchange.
Microsoft Rights Management connector:
- We are allowed to get an optional application known as Microsoft Rights Management connector (RMS connector), in Exchange 2016. This helps you improve data protection by connecting over to cloud-based Microsoft Rights Management services.
- Once you implement and configure the RMS connector, it offers continuous data protection across the life span of the information. You might always define the level of protection you require. It is so incredible !
- The EAC consists of auditing functionality which permits us to run reports or export entries from the mailbox audit log and the administrator audit log, in Exchange 2016. The mailbox audit log saves and records whenever a mailbox is viewed by someone other than owner of the mailbox.
- Such thing helps examining who has viewed a mailbox & what they have performed. The administrator audit log saves and records any action or task, depending on an Exchange Management Shell cmdlet, done by an administrator.
- This supports during investigation and troubleshooting configuration challenges, issues and the cause of problems that might be related to security or compliance.
Accessing the administrator audit log
- We can access administrator audit log entries present in the EAC, in place of exporting the administrator audit log as it can consumes up to 24 hours.
- We can access it in case you go to Compliance Management > Auditing and select and click on View the administrator audit log. This is going to display upto 1000 entries on multiple pages.
- The Exchange 2016 has quite strong built-in malware filtering abilities that helps in protecting your network from malicious software transferred via emails. All emails transmitted or received by Exchange 2016 are scanned for malware (viruses and spyware).
- In case malware is found, then the message is deleted. Notifications might be sent over to senders or administrators when an infected message is removed and not delivered. We might choose to replace infected enclosure and attachments with either default or custom messages which notify the recipients of the malware detection.
The Exchange 2016 Recipients managements are as follows:
Group Naming Policy:
- Next, we can generate group naming policy that will permit us to set Distribution Group names as per company policy. This permits us restricting and blocking few words. We can mention a prefix and suffix for the group. In EAC, choose Groups then more and then click on Configure group naming policy.
- You may execute the following command to verify the policy
Get-OrganizationConfig | FL DistributionGroupNamingPolicy
Sharing and collaboration:
- Let us explore the sharing and collaboration improvisations in Exchange 2016.
- These Public Folder mailboxes in Exchange 2016 generally reside in the mailbox database. Hence they can take benefit of the existing high availability and storage advance technologies of the mailbox store.
- The architecture of the public folder uses particularly designed mailboxes to save and store both the hierarchy and the public folder content. There exists no PF Database and No PF replication. Generally, Exchange 2016 uses single-master replication model.
- The creation of the Shared mailbox and administration has improved in Exchange 2016. Now we can generate and create a shared mailbox in single step from Exchange admin center.
- In EAC, go over to Recipients
- Shared Mailboxes to create and generate a shared mailbox.
- We are allowed to use site mailbox to keep the document and emails where emails stay in the mailbox database and documents goes to the SharePoint, in Exchange 2016.
- Site mailboxes enhance collaboration, integration and user productivity by permitting access to both Microsoft SharePoint 2013 documents and Exchange email using the same client interface.
- A site mailbox is functionally composed of SharePoint 2013 site membership (members and owners), shared storage via an Exchange 2013 mailbox for email messages and a SharePoint 2013 site for documents, and a management interface which addresses provisioning and lifecycle requirements.
Look out the below shown diagram.
Integration with SharePoint and Skype for Business
- Exchange 2016 provides great collaboration and integration with Skype for Business and SharePoint 2016.
There are following mentioned benefits of this improved integration:
- Exchange 2016 capable to archive Skype for Business Server 2015 content & it uses Exchange 2016 as a contact store.
- Discovery Managers is capable to run Hold searches & In-Place eDiscovery across Exchange 2016, SharePoint 2013 and Skype for Business data.
Batch Mailbox Moves:
- In Exchange 2013 Microsoft commenced batch mailbox and public folders migration shifts which is going to continue in Exchange 2016. This is designed over Mailbox Replication service migrates with improved management capability. You can also provide a path of csv file to pull the input as well.
The following enhancements come in the batch moves.
- Capability to move multiple mailboxes in huge batches.
- Email reporting alters notification.
- Automatic migrations retry and automatic prioritization.
- Primary and personal archive mailboxes might be shifted together or separately.
- Choice for manual migration request finalization. This permits us to reanalyzed and review a move before we finish it.
- Periodic incremental syncs to perform the changes.
High Availability and Site Resilience:
- Exchange 2016 generally uses DAGs and mailbox database replicas for high availability with single item recovery, lagged database copies, retention policies, and Exchange native data protection. The high availability platform, Information Store and the Extensible Storage Engine (ESE), have been improved to offer a greater availability, easier management & to reduce costs.
Several other enhancements included in Exchange 2016 mentioned below:
- This is among the best function that offers internal monitoring & recovery-oriented functions are tightly coupled and integrated to help prevent failures, proactively retrieve services, and initiate server failovers automatically by default or alert administrators to take action.
- This will also give better end user experience instead of just server and component uptime to help keep the service continuity available.
- The new improvement provide higher availability via enhanced resiliency.
- Support for several databases per disk Exchange 2013 usually supports multiple databases (1 active and other passive copy) on the present same disk. This permits leveraging larger disks in context to capacity and IOPS as efficiently as possible.
- AutoReseed is a magic of reseeding that by default automatically reseed if same size spare disk is present. Hence if a disk fails in the mid night, without bothering you Exchange 2016 will automatically by default reseed your database copy. Auto Reseed first incepted and introduced in Exchange 2013 and then continued over to Exchange 2016.
Automatic recovery from storage failures:
- This function continues Exchange 2010 innovation to permit the system to recover from failures which affect resiliency or redundancy. Moreover to Exchange 2010 bugcheck behaviors, Exchange 2016 also consist of recovery behaviors for long I/O times, excessive memory utilization by MSExchangeRepl.exe, & severe cases where the system is in a bad state which threads can’t be scheduled. This is a super awesome feature.
Lagged copy enhancements
- In Exchange 2016 lagged replicas can take care of itself up to some extent using automatic log play down. Next, the lagged copies are going to play down log files in several situations like single page retrieve/restore or low disk space.
- In case Exchange Server detects that page patching is needed for a lagged copy, the log files will be automatically by default replayed into the lagged copy to conduct page patching.
- Lagged replicas is going to invoke this auto replay function when a low disk space threshold has been achieved & when the lagged replica has been found as the only available copy for a particular period of time.
- Lagged replicas can also leverage Safety Net that makes recovery or activation quite easier.
Single copy alert improvements:
- The single copy alert incepted in Exchange 2010 is no longer an isolated separate scheduled script. Now it is coupled integrated into managed availability components within the system and also a native function within Exchange.
DAG network auto-configuration:
- Database Availability Group networks may be automatically by default configured by the system depending on configuration settings, in Exchange 2016. DAGs might be distinguishing among MAPI & Replication networks then configure DAG networks by default automatically.
Cluster administrative access point not required:
- In Exchange 2013 SP1 we have a choice to create DAG with no IP and cluster administrative access point. And it takes care of multiple issues around IP DAG. In Exchange 2016 Default DAG creation is going to be without IP and cluster administrative access point such that it is suggested to install Exchange 2016 on Windows 2012 R2 or higher.
Exchange Workload Management:
- The Exchange workload is Exchange server functional feature, protocol, or service which has been explicitly declared and defined for the purpose of Exchange system resource management.
- Every Exchange workload utilizes system resources like CPU, mailbox database operations, or Active Directory requests to run user requests or run background work.
- The example instances of Exchange workloads are Outlook on the web, Exchange ActiveSync, mailbox migration, and mailbox assistants.
Exchange 2016 has following two approaches to manage Exchange workloads:
- Monitor and track the health of system resources: Managing workloads depending on the system resources health.
- Control how resources are utilized by individual users: Controlling how resources are utilized by individual users was possible in Exchange 2010 that was called user throttling and this ability has been improved in Exchange 2016.
Discontinued Functions from Exchange 2010 to 2016:
Hub Transport Server Role:
The Hub transport role:
- In Exchange 2016 mailbox role, this role has been merged as transport services.
Client Access Server Role:
- In Exchange 2016 mailbox role, this role has been merged as client access services.
Client Access server role:
- This role has been removed and added Client Access server Services, in Exchange 2016 Microsoft. Mailbox role is the only role left and it does all the task and action.
- This is good amendment but Exchange is going to be no longer able to leverage windows network load balancing and DAG over the same infrastructure that was the choice for small org instead of investing on Load Balancers.
- Rather, Load Balancer are designed and developed to do load balancing that adds much more efficiency to the load balancing.
- There exists virtual load balancers that can be installed like Client Access server role in Virtualization.
Unified Messaging Server Role:
- In Exchange 2016 mailbox role, This role has been again merged as unified messaging
- In Exchange 2016 Exchange Web Services (EWS), Exchange ActiveSync (EAS), and Representational State Transfer (REST) APIs has replaced MAPI/CDO library. In case an application in your company is using the MAPI/CDO library, in Exchange 2016 it requires to move to EWS, EAS, or the REST APIs.
EMC and ECP:
- EMC and ECP are gradually been removed and all controls are coming into Exchange Admin Center. And EAC uses same ECP virtual directory.
- Outlook anywhere is the only way to connect your outlook over to Exchange 2016. MAPI over http is the only default protocol and alternative is RPC over http. Outlook 2013 SP1 or higher back support MAPI over http.
Outlook 2003 and 2007:
- Outlook 2003 and 2007 are not being supported in Exchange 2016. Outlook 2003 was again not supported in Exchange 2013 and in Exchange 2016 outlook 2007.
OWA(OOTW) and Outlook:
- Saying Bye to built-in Spell checker, rather OOTW will be using web browser’s spell checker.
- OOTW no longer comprise of customizable filtered views and no longer supports saving filtered access to Favorites. Customizable filters have also been replaced by fixed filters that might be used to access all messages, unread messages; messages sent over to the user or flagged messages. This is really awesome.
- Custom dates might only set from outlook. And OOTW do not support it.
Chat Contact list:
- To this also its time to say bye, this list used to appeared in the folder list in Exchange 2010 OWA
- OOTW do not support searching folders. This may be added later.
- In Exchange 2016 you are not allowed to link a Send connector to a Receive connector. LinkedReceiveConnector parameter has been eliminated from New-SendConnector and Set-SendConnector.
Anti-spam and Anti-malware:
Anti-spam agent management in the EMC:
- No more GUI management needed for Anti-spam and anti-malware. We are allowed to configure it from Exchange management shell.
Connection filtering agent on Hub Transport servers:
- In Exchange 2016 the Attachment Filter agent and the Connection Filtering agent were not available.
- The only approach to install Connection Filtering agent is to configure it on Edge transport server.
Managed policy and Compliance:
- In Exchange 2010, we all have mainly used managed folders for messaging retention management. In Exchange 2016 managed folders has been gradually removed this has been replaced by Retention Policies and TAGs for MRM.
Port Managed Folder Wizard:
- In Exchange 2010, we have mainly used the Port Managed Folder wizard to generate retention tags depending on managed folder & managed content settings. This functionality is again been removed. In Exchange 2016, the Exchange admin center does not include this functionality.
- We have to give the command New-RetentionPolicyTag with the parameter ManagedFolderToUpgrade to generate a retention tag depending on a managed folder. This might be used to shift the managed folders to retention tag.
Unified Messaging and Voice Mail:
Directory lookups mainly using Automatic Speech Recognition (ASR):
- In Exchange 2010, Outlook Voice Access users are allowed to use speech inputs using Automatic Speech Recognition (ASR) to search and explore for users listed in the directory.
- Speech inputs might have been used in Outlook Voice Access to navigate menus, messages, and other choices. But, we still need to use the telephone key pad to enter their PIN, and traverse to navigate personal options.
- Now in Exchange 2016, authenticated & non-authenticated Outlook Voice Access users are not allowed to search for users in the directory using speech inputs or ASR in any given language. Hence this feature has gone for good.
- Now when callers call into an auto attendant might use speech inputs in many languages to traverse auto attendant menus and find users in the directory.