We are interested in upgrading some of our solutions to work on Exchange 2016. That’s why we went through the PowerShell documentation from Microsoft and checked what has changed. For general overview of Exchange 2016 changes, please, visit Microsoft TechNet to see What is new. There is a well covered comparison with Exchange 2010 and 2013.
In general, there are very little changes to the command of Exchange Powershell. But there are some things you should be aware of. The first thing is that the Client Access Server role (CAS) is deprecated. It’s included in the Mailbox services. It’s as the aforementioned article states:
Mailbox services include all the traditional server components found in the Exchange 2013 Mailbox server role: the Client Access protocols, Transport service, Mailbox databases, and Unified Messaging. The Mailbox server handles all activity for the active mailboxes on that server.
Client Access services provide authentication, limited redirection, and proxy services. Client Access services don’t do any data rendering and offer all the usual client access protocols: HTTP, POP and IMAP, and SMTP.
This is why Microsoft states
The *-ClientAccessServer cmdlets will be removed in a future version of Exchange. You should use the *-ClientAccessService cmdlets instead.
The *-TransportServer cmdlets will be removed in a future version of Exchange. You should use the *-TransportService cmdlets instead.
There is also a note that some “ActiveSync cmdlets will be removed in a future version of Exchange. You should use the corresponding MobileDevice cmdlets instead.” See more details here. The full list of those command is here:
New Compliance Search cmdlets
There are some new PowerShell cmdlets also:
For more information, please refer to this article.