Sep 20, 2018 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.
Exchange Server 2019 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 2019 helps lower the total cost of ownership whether you deploy Exchange 2019 on-premises or provision your mailboxes in the cloud.
Choose the section below that matches the version of Exchange that you're upgrading from. If you want to know about features that have been removed or replaced in Exchange 2019, see What's discontinued in Exchange Server.
For more information about deploying Exchange 2019, see Planning and deployment for Exchange Server.
What's new when upgrading from Exchange 2016 to Exchange 2019?Security![]()
Performance
Clients
What's new when upgrading from Exchange 2013 to Exchange 2019?Exchange 2019 architecture
Today, CPU horsepower is significantly less expensive and is no longer a constraining factor. With that constraint lifted, the primary design goal for Exchange 2019 is for simplicity of scale, hardware utilization, and failure isolation. With Exchange 2019, we reduced the number of server roles to two: the Mailbox and Edge Transport server roles.
Unified Messaging (UM) has been removed from Exchange 2019. Other than that, the Mailbox server in Exchange 2019 includes all of the server components from the Exchange 2013 Mailbox and Client Access server roles:
The Edge Transport role is typically deployed in your perimeter network, outside your internal Active Directory forest, and is designed to minimize the attack surface of your Exchange deployment. By handling all Internet-facing mail flow, it also adds additional layers of message protection and security against viruses and spam, and can apply mail flow rules (also known as transport rules) to control message flow.
For more information about the Exchange 2019 architecture, see Exchange architecture.
Along with the new Mailbox role, Exchange 2019 now allows you to proxy traffic from Exchange 2013 Client Access servers to Exchange 2019 mailboxes. This new flexibility gives you more control in how you move to Exchange 2019 without having to worry about deploying enough front-end capacity to service new Exchange 2019 servers.
ClientsOutlook on the web (formerly known as Outlook Web App)
Outlook Web App is now known as Outlook on the web, which continues to let users access their Exchange mailbox from almost any web browser.
Note
Supported Web browsers for Outlook on the web in Exchange 2019 are Microsoft Edge, Internet Explorer 11, and the most recent versions of Mozilla Firefox, Google Chrome, and Apple Safari.
The former Outlook Web App user interface has been updated and optimized for tablets and smart phones, in addition to desktop and laptop computers. New Exchange 2019 features include:
MAPI over HTTP
MAPI over HTTP is now the default protocol that Outlook uses to communicate with Exchange. MAPI over HTTP improves the reliability and stability of the Outlook and Exchange connections by moving the transport layer to the industry-standard HTTP model. This allows a higher level of visibility of transport errors and enhanced recoverability. Additional functionality includes support for an explicit pause-and-resume function, which enables supported clients to change networks or resume from hibernation while maintaining the same server context.
Note: MAPI over HTTP isn't enabled in organizations where the following conditions are both true:
While MAPI over HTTP is now the default communication protocol between Outlook and Exchange, clients that don't support it will fall back to Outlook Anywhere (RPC over HTTP).
For more information, see MAPI over HTTP in Exchange Server.
Document collaboration
Exchange 2019, along with SharePoint Server 2019, enables Outlook on the web users to link to and share documents that are stored in OneDrive for Business in an on-premises SharePoint server instead of attaching files to messages. Users in an on-premises environment can collaborate on files in the same manner that's used in Office 365.
For more information about SharePoint Server 2019, see New and improved features in SharePoint Server 2019.
When an Exchange 2019 user receives a Word, Excel, or PowerPoint file in an email attachment, and the file is stored in OneDrive for Business or on-premises SharePoint, the user will now have the option of viewing and editing that file in Outlook on the web alongside the message. To do this, you'll need a separate computer in your on-premises organization that's running Office Online Server. For more information, see Install Office Online Server in an Exchange organization.
Exchange 2019 also brings the following improvements to document collaboration:
Office 365 hybrid
The Hybrid Configuration Wizard (HCW) that was included with Exchange 2013 is moving to become a cloud-based application. When you choose to configure a hybrid deployment in Exchange 2019, you'll be prompted to download and install the wizard as a small app. The wizard will function the same in previous versions of Exchange, with a few new benefits:
In addition to Hybrid Configuration Wizard improvements, multi-forest hybrid deployments are being simplified with Azure Active Directory Connect (AADConnect). AADConnect introduces management agents that will make it significantly easier to synchronize multiple on-premises Active Directory forests with a single Office 365 tenant. For more information about AADConnect, see Integrating your on-premises identities with Azure Active Directory.
Exchange ActiveSync clients will be seamlessly redirected to Office 365 when a user's mailbox is moved to Exchange Online. To support this, ActiveSync clients need to support HTTP 451 redirect. When a client is redirected, the profile on the device is updated with the URL of the Exchange Online service. This means the client will no longer attempt to contact the on-premises Exchange server when trying to find the mailbox.
Messaging policy and compliance
There are several new and updated message policy and compliance features in Exchange 2019.
Data loss prevention
To comply with business standards and industry regulations, organizations need to protect sensitive information and prevent its inadvertent disclosure. Examples of sensitive information that you might want to prevent from leaking outside your organization include credit card numbers, social security numbers, health records, or other personally identifiable information (PII). With a DLP policy and mail flow rules (also known as transport rules) in Exchange 2019, you can now identify, monitor, and protect 80 different types of sensitive information with new conditions and actions:
To learn more about DLP, see Data loss prevention in Exchange Server.
In-place Archiving, retention, and eDiscovery
Exchange 2019 includes the following improvements to In-Place Archiving, retention, and eDiscovery to help your organization meet its compliance needs:
For more information, see Messaging policy and compliance in Exchange Server.
Microsoft Exchange SecurityImproved performance and scalability
In Exchange 2019, the search architecture has been redesigned. Previously, search was a synchronous operation that was not very fault-tolerant. The new architecture is asynchronous and decentralized. It distributes the work across multiple servers and keeps retrying if any servers are too busy. This means that we can return results more reliability, and faster.
Another advantage of the new architecture is that search scalability is improved. The number of mailboxes you can search at once using the console has increased from 5k to 10k for both mailboxes and archive mailboxes, allowing you to search a total of 20k mailboxes at the same time.
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.
Choose the section below that matches the version of Exchange that you're upgrading from. If you want to know about features that have been removed or replaced in Exchange 2016, see What's discontinued in Exchange Server.
For more information about deploying Exchange 2016, see Planning and deployment.
What's new when updating from Exchange 2016 RTM to Exchange 2016 CU1?
When you update to Exchange 2016 Cumulative Update 1 (CU1) from Exchange 2016 RTM, you'll get the following new features:
What's new when upgrading from Exchange 2013 to Exchange 2016 RTM?Exchange 2016 architecture
Today, CPU horsepower is significantly less expensive and is no longer a constraining factor. With that constraint lifted, the primary design goal for Exchange 2016 is for simplicity of scale, hardware utilization, and failure isolation. With Exchange 2016, we reduced the number of server roles to two: the Mailbox and Edge Transport server roles.
The Mailbox server in Exchange 2016 includes all of the server components from the Exchange 2013 Mailbox and Client Access server roles:
The Edge Transport role is typically deployed in your perimeter network, outside your internal Active Directory forest, and is designed to minimize the attack surface of your Exchange deployment. By handling all Internet-facing mail flow, it also adds additional layers of message protection and security against viruses and spam, and can apply mail flow rules (also known as transport rules) to control message flow.
For more information about the Exchange 2016 architecture, see Exchange 2016 architecture.
Along with the new Mailbox role, Exchange 2016 now allows you to proxy traffic from Exchange 2013 Client Access servers to Exchange 2016 mailboxes. This new flexibility gives you more control in how you move to Exchange 2016 without having to worry about deploying enough front-end capacity to service new Exchange 2016 servers.
ClientsOutlook on the web (formerly Outlook Web App)
Outlook Web App is now known as Outlook on the web, which continues to let users access their Exchange mailbox from almost any web browser.
Note
Supported Web browsers for Outlook on the web in Exchange 2016 are Microsoft Edge, Internet Explorer 11, and the most recent versions of Mozilla Firefox, Google Chrome, and Apple Safari.
The former Outlook Web App user interface has been updated and optimized for tablets and smart phones, in addition to desktop and laptop computers. New Exchange 2016 features include:
MAPI over HTTP
MAPI over HTTP is now the default protocol that Outlook uses to communicate with Exchange. MAPI over HTTP improves the reliability and stability of the Outlook and Exchange connections by moving the transport layer to the industry-standard HTTP model. This allows a higher level of visibility of transport errors and enhanced recoverability. Additional functionality includes support for an explicit pause-and-resume function, which enables supported clients to change networks or resume from hibernation while maintaining the same server context.
Note: MAPI over HTTP isn't enabled in organizations where the following conditions are both true:
While MAPI over HTTP is now the default communication protocol between Outlook and Exchange, clients that don't support it will fall back to Outlook Anywhere (RPC over HTTP).
For more information, see MAPI over HTTP in Exchange 2016.
Document collaboration
Exchange 2016, along with SharePoint Server 2016, enables Outlook on the web users to link to and share documents that are stored in OneDrive for Business in an on-premises SharePoint server instead of attaching files to messages. Users in an on-premises environment can collaborate on files in the same manner that's used in Office 365.
For more information about SharePoint Server 2016, see New and improved features in SharePoint Server 2016.
When an Exchange 2016 user receives a Word, Excel, or PowerPoint file in an email attachment, and the file is stored in OneDrive for Business or on-premises SharePoint, the user will now have the option of viewing and editing that file in Outlook on the web alongside the message. To do this, you'll need a separate computer in your on-premises organization that's running Office Online Server. For more information, see Install Office Online Server in an Exchange 2016 organization.
Exchange 2016 also brings the following improvements to document collaboration:
Office 365 hybrid
The Hybrid Configuration Wizard (HCW) that was included with Exchange 2013 is moving to become a cloud-based application. When you choose to configure a hybrid deployment in Exchange 2016, you'll be prompted to download and install the wizard as a small app. The wizard will function the same in previous versions of Exchange, with a few new benefits:
In addition to Hybrid Configuration Wizard improvements, multi-forest hybrid deployments are being simplified with Azure Active Directory Connect (AADConnect). AADConnect introduces management agents that will make it significantly easier to synchronize multiple on-premises Active Directory forests with a single Office 365 tenant. For more information about AADConnect, see Integrating your on-premises identities with Azure Active Directory.
Exchange ActiveSync clients will be seamlessly redirected to Office 365 when a user's mailbox is moved to Exchange Online. To support this, ActiveSync clients need to support HTTP 451 redirect. When a client is redirected, the profile on the device is updated with the URL of the Exchange Online service. This means the client will no longer attempt to contact the on-premises Exchange server when trying to find the mailbox.
Messaging policy and compliance
There are several new and updated message policy and compliance features in Exchange 2016.
Data loss prevention
To comply with business standards and industry regulations, organizations need to protect sensitive information and prevent its inadvertent disclosure. Examples of sensitive information that you might want to prevent from leaking outside your organization include credit card numbers, social security numbers, health records, or other personally identifiable information (PII). With a DLP policy and mail flow rules (also known as transport rules) in Exchange 2016, you can now identify, monitor, and protect 80 different types of sensitive information with new conditions and actions:
To learn more about DLP, see Data loss prevention in Exchange 2016.
In-place Archiving, retention, and eDiscovery
Exchange 2016 includes the following improvements to In-Place Archiving, retention, and eDiscovery to help your organization meet its compliance needs:
For more information, see Messaging policy and compliance in Exchange 2016.
Video screenshot by Michelle Starr/CNET AustraliaIn high school science classes, students are encouraged to memorize the first 20 elements of the periodic table. Called simply 'The New Periodic Table Song (In Order),' it's a chemical adventure that romps along to a section of ' (otherwise known as the Can-Can music) from Jacques Offenbach's opera 'Orpheus in the Underworld.' High school learning game. There are other methods employed at the university level for all 118 - many students swear by mnemonics.When it comes to tremendously catchy fun, though, a new song by has them all beat. It goes, appropriately, at a fast gallop, but listen a few times, and you'll soon find yourself confidently singing along.Best periodic table song ever.(Source: ).
Improved performance and scalability
In Exchange 2016, the search architecture has been redesigned. Previously, search was a synchronous operation that was not very fault-tolerant. The new architecture is asynchronous and decentralized. It distributes the work across multiple servers and keeps retrying if any servers are too busy. This means that we can return results more reliability, and faster.
Another advantage of the new architecture is that search scalability is improved. The number of mailboxes you can search at once using the console has increased from 5k to 10k for both mailboxes and archive mailboxes, allowing you to search a total of 20k mailboxes at the same time.
What's new when upgrading from Exchange 2010 to Exchange 2016 RTM?Exchange admin center
Exchange 2016 provides a single unified management console that allows for ease of use and is optimized for management of on-premises, online, or hybrid deployments. The Exchange admin center (EAC) in Exchange 2016 replaces the Exchange Management Console (EMC) and the Exchange Control Panel (ECP) that were used in Exchange 2010 (but the name of the EAC virtual directory is still 'ECP'). Some EAC features include:
For more information about the EAC, see Exchange admin center in Exchange 2016.
Exchange 2016 architecture
Today, CPU horsepower is significantly less expensive and is no longer a constraining factor. With that constraint lifted, the primary design goal for Exchange 2016 is for simplicity of scale, hardware utilization, and failure isolation. With Exchange 2016, we reduced the number of server roles to two: the Mailbox and Edge Transport server roles.
The Mailbox server in Exchange 2016 includes all of the server components from the Mailbox, Client Access, Hub Transport, and Unified Messaging server roles in Exchange 2010:
Like previous versions of Exchange. the Edge Transport role is typically deployed in your perimeter network, outside your internal Active Directory forest, and is designed to minimize the attack surface of your Exchange deployment. By handling all Internet-facing mail flow, it also adds additional layers of message protection and security against viruses and spam, and can apply mail flow rules (also known as transport rules) to control message flow.
The Exchange 2016 architecture provides the following benefits:
For more information about the Exchange 2016 architecture, see Exchange 2016 architecture.
Setup
Setup has been completely rewritten so that installing Exchange 2016 and making sure you've got the latest product rollups and security fixes is easier than ever. Here are some of the improvements we've made:
For more information, see Planning and deployment.
Office 365 hybrid
The Hybrid Configuration Wizard (HCW) that was included with Exchange 2013 is moving to become a cloud-based application. When you choose to configure a hybrid deployment in Exchange 2016, you'll be prompted to download and install the wizard as a small app. The wizard will function the same in previous versions of Exchange, with a few new benefits:
In addition to Hybrid Configuration Wizard improvements, multi-forest hybrid deployments are being simplified with Azure Active Directory Connect (AADConnect). AADConnect introduces management agents that will make it significantly easier to synchronize multiple on-premises Active Directory forests with a single Office 365 tenant.
Exchange ActiveSync clients will be seamlessly redirected to Office 365 when a user's mailbox is moved to Exchange Online. To support this, ActiveSync clients need to support HTTP 451 redirect. When a client is redirected, the profile on the device is updated with the URL of the Exchange Online service. This means the client will no longer attempt to contact the on-premises Exchange server when trying to find the mailbox.
I have also shown a proof that is available in the installation video, so don’t get worried, this file is 100% working and free from virus, so don’t hesitate before downloading this file from my website. Download euro truck simulator 2008.
Messaging policy and compliance
There are several new and updated message policy and compliance features in Exchange 2016.
Data loss prevention
Data loss prevention (DLP) capabilities help you protect your sensitive data and inform users of internal compliance policies. DLP can also help keep your organization safe from users who might mistakenly send sensitive information to unauthorized people. DLP helps you identify, monitor, and protect sensitive data through deep content analysis. Exchange 2016 offers built-in DLP policies based on regulatory standards such as personally identifiable information (PII) and payment card industry data security standards (PCI), and is extensible to support other policies important to your business. With a DLP policy in Exchange 2016, you can now identify, monitor, and protect 80 different types of sensitive information. For more information, see Sensitive information types in Exchange 2016. Additionally, the new policy tips in Outlook 2016 inform users about policy violations before sensitive data is sent.
To learn more, see Data loss prevention in Exchange 2016
Mail flow rules (transport rules)
You can use Exchange mail flow rules (also known as transport rules) to look for specific conditions in messages that pass through your organization and take action on them. For example, your organization might require that certain types of messages are blocked or rejected in order to meet legal or compliance requirements, or to implement specific business needs. Mail flow rules are similar to the Inbox rules that are available in Outlook. The main difference between mail flow rules and Inbox rules is that mail flow rules take action on messages while they're in transit as opposed to after the message is delivered. Mail flow rules also contain a richer set of conditions, exceptions, and actions, which gives you the flexibility to implement many types of messaging policies.
These features are new to mail flow rules in Exchange 2016:
For more information, see Mail flow rules in Exchange 2016.
Azure Rights Management connector
The Azure Rights Management connector (also known as the Microsoft Rights Management connector or RMS connector) is an optional application that helps you enhance data protection for your Exchange 2016 server by connecting to the cloud-based Azure Rights Management service (also known as Microsoft Rights Management or Azure RMS). Once you install the RMS connector, it provides continuous data protection throughout the life span of the information and because these services are customizable, you can define the level of protection you need. For example, you can limit email message access to specific users or set view-only rights for certain messages.
For more information, see Deploying the Azure Rights Management connector.
In-place Archiving, retention, and eDiscovery
Exchange 2016 includes the following improvements to In-Place Archiving, retention, and eDiscovery to help your organization meet its compliance needs:
For more information, see Messaging policy and compliance in Exchange 2016.
Auditing
Exchange 2016 includes the following improvements to auditing:
Antimalware protection
The built-in malware filtering capabilities of Exchange 2016 helps protect your network from malicious software that's transferred by email messages. All messages sent or received by your Exchange 2016 Mailbox server are scanned for malware (viruses and spyware) by using the built-in Malware Agent. If malware is detected, the message is deleted. Notifications may also be sent to senders or administrators when an infected message is deleted and not delivered. You can also choose to replace infected attachments with either default or custom messages that notify the recipients of the malware detection.
For more information about antimalware protection, see Antimalware protection in Exchange 2016.
Mail flow and the transport pipeline
How messages flow through an organization and what happens to them has changed significantly in Exchange 2016. Following is a brief overview of the changes:
Recipients
Administrators can now use the EAC to create a group naming policy, which lets you standardize and manage the names of distribution groups that are created by users in your organization. You can automatically add a prefix or suffix to the name of the distribution group when it's created, and you can block specific words from being used in group names. For more information, see Create a Distribution Group Naming Policy.
For more information about recipients in Exchange 2016, see Recipients.
Sharing and collaboration
Exchange 2016 includes the following enhancements for sharing and collaboration:
Integration with SharePoint and Skype for Business
Exchange 2016 offers greater integration with SharePoint and Skype for Business. Benefits of this enhanced integration include:
For more information, see Plan Exchange 2016 integration with SharePoint and Skype for Business.
ClientsOutlook on the web (formerly Outlook Web App)
Outlook Web App is now known as Outlook on the web, which continues to let users access their Exchange mailbox from almost any web browser.
Note
Supported Web browsers for Outlook on the web in Exchange 2016 are Microsoft Edge, Internet Explorer 11, and the most recent versions of Mozilla Firefox, Google Chrome, and Apple Safari.
In Exchange 2016, the former Outlook Web App user interface is updated and optimized for tablets and smart phones, in addition to desktop and laptop computers. New Exchange 2016 features include:
Offline Outlook on the web
Internet Explorer 11 and Windows Store apps using JavaScript support the Application Cache API (or AppCache) as defined in the HTML5 specification, which allows you to create offline web applications. AppCache enables webpages to cache (or save) resources locally, including images, script libraries, style sheets, and so on. In addition, AppCache allows URLs to be served from cached content using standard Uniform Resource Identifier (URI) notation. The following is a list of the browsers that support AppCache:
MAPI over HTTP
MAPI over HTTP is now the default protocol that Outlook uses to communicate with Exchange. MAPI over HTTP improves the reliability and stability of the Outlook and Exchange connections by moving the transport layer to the industry-standard HTTP model. This allows a higher level of visibility of transport errors and enhanced recoverability. Additional functionality includes support for an explicit pause-and-resume function, which enables supported clients to change networks or resume from hibernation while maintaining the same server context.
Note: MAPI over HTTP isn't enabled in organizations where the following conditions are both true:
While MAPI over HTTP is now the default communication protocol between Outlook and Exchange, clients that don't support it will fall back to Outlook Anywhere (RPC over HTTP). RPC (RPC over TCP) is no longer supported.
For more information, see MAPI over HTTP in Exchange 2016.
Document collaboration![]()
Exchange 2016, along with SharePoint Server 2016, enables Outlook on the web users to link to and share documents that are stored in OneDrive for Business in an on-premises SharePoint server instead of attaching files to messages. Users in an on-premises environment can collaborate on files in the same manner that's used in Office 365.
For more information about SharePoint Server 2016, see New and improved features in SharePoint Server 2016.
When an Exchange 2016 user receives a Word, Excel, or PowerPoint file in an email attachment, and the file is stored in OneDrive for Business or on-premises SharePoint, the user will now have the option of viewing and editing that file in Outlook on the web alongside the message. To do this, you'll need a separate computer in your on-premises organization that's running Office Online Server. For more information, see Install Office Online Server in an Exchange 2016 organization.
Exchange 2016 also brings the following improvements to document collaboration:
Batch mailbox moves
Exchange 2016 makes use of batch moves. The move architecture is built on top of MRS (Mailbox Replication service) moves with enhanced management capability. The batch move architecture features the following enhancements:
For more information, see Manage on-premises mailbox moves in Exchange 2016.
High availability and site resilience
The high availability model of the mailbox component has not changed significantly since Exchange 2010. The unit of high availability is still the database availability group (DAG). The DAG still uses Windows Server failover clustering. Continuous replication still supports both file mode and block mode replication. However, there have been some improvements. Failover times have been reduced as a result of transaction log code improvements and deeper checkpoint on the passive databases. The Exchange Store service has been re-written in managed code. Now, each database runs under its own process, which isolates store issues to a single database.
Exchange 2016 uses DAGs and mailbox database copies, along with other features such as single item recovery, retention policies, and lagged database copies, to provide high availability, site resilience, and Exchange native data protection. The high availability platform, the Exchange Information Store and the Extensible Storage Engine (ESE), have all been enhanced to provide greater availability, easier management, and to reduce costs. These enhancements include:
For more information about these features, see High Availability and Site Resilience and Changes to high availability and site resilience over previous versions.
Managed Store
In Exchange 2016, Managed Store is the name of the Information Store processes,
Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe . The new Managed Store is written in C# and is tightly integrated with the Microsoft Exchange Replication service (MSExchangeRepl.exe ) to provide higher availability through improved resiliency. In addition, the Managed Store allows more granular management of resource consumption, and has improved diagnostics for faster root cause analysis.
The Managed Store works with the Microsoft Exchange Replication service to manage mailbox databases, which continue to use the Extensible Storage Engine (ESE) database engine. Exchange 2016 includes significant changes to the mailbox database schema that provide many optimizations over previous versions of Exchange. The Microsoft Exchange Replication service is also responsible for all service availability related to Mailbox servers. These architectural changes enable faster database failover and better physical disk failure handling.
The Managed Store uses the same search platform as SharePoint Server 2016 to provide more robust indexing and searching when compared to Microsoft Search engine that was used in previous versions of Exchange.
For more information, see High Availability and Site Resilience.
Exchange workload management
An Exchange workload is an Exchange server feature, protocol, or service that has been explicitly defined for the purposes of Exchange system resource management. Each Exchange workload consumes system resources such as CPU, mailbox database operations, or Active Directory requests to execute user requests or run background work. Examples of Exchange workloads include Outlook on the web, Exchange ActiveSync, mailbox migration, and mailbox assistants.
There are two ways to manage Exchange workloads in Exchange 2016:
For more information about these features, see User workload management in Exchange 2016.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |