Updating changes to exchange2016
The focus on Exchange deployment scripts in this blog post is merely to provide context as to how/why this solution was created.
NOTE: There are code snippets used in these blog posts, but PLEASE do not copy and paste them as that can lead to unexpected results.
Exchange Server 2016 Cumulative Update 2 and Exchange Server 2013 Cumulative Update 13 are available on the Microsoft Download Center. Net 4.6.1 is now available for Exchange Server 20 with these updates. The cmdlet has been updated to produce a SHA-2 certificate for all self-signed certificates created by Exchange.
We fully support customers upgrading servers running 4.5.2 to 4.6.1 without removing Exchange. Net 4.6.1 installation replaces the existing 4.5.2 installation. Creating a SHA-2 certificate is the default behaviour for the cmdlet.
To be clear, the issue of maintaining version control on Power Shell scripts is not unique to Exchange deployments, and as such the solution covered here can be leveraged by/applied to any Power Shell script regardless of its function.
If the Exchange Administrator lacks permissions to update Active Directory Schema, a Schema Admin should execute should be executed prior to upgrading any servers to CU13.
Prepare AD will run automatically during the first server upgrade if Setup detects this is required and the logged on user has sufficient permission.
NET Framework 4.6.2; NET Framework 4.7.1 is currently being tested (4.7 will be skipped), and support for 4.7.1 is expected for the December updates.
Caution: As for any update, I recommend to thoroughly test updates in a test environment prior to implementing them in production.Today we are announcing the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013.