Updates for all versions of Exchange Servers are now available on the Microsoft Download Center. First ever update for Exchange Server 2016, Cumulative Update 12 Exchange Server 2013 and Exchange Server 2007 and Exchange Server 2010 Update Rollups are available for the customers to download and patch.
More Details and Download Links,
As always remember to test these updates to validate the compatibility with existing environment and the integrations if any.
Microsoft Exchange team is announcing the availability of Update Rollup and Cumulative Updates for Exchange Server 2007 SP3, Exchange Server 2010 SP3 and Exchange Server 2013.
Each of the following links will lead you to the respective pages for more detail and download.
Exchange Server 2007 SP3
More Info Link:- Update Rollup 14 for Exchange Server 2007 Service Pack 3
Exchange Server 2010 SP3
More Info Link:- Update Rollup 7 for Exchange Server 2010 Service Pack 3
Download Link:- Update Rollup 7 For Exchange 2010 SP3 (KB2961522)
Exchange Server 2013
More Info Link:- Cumulative Update 6 for Exchange Server 2013
Download Link:- Cumulative Update 6 for Exchange Server 2013 (KB2961810)
Share you experience, which will be helpful in planning and executing the updates.
Update from other blogs:
There are few issues observed of applying the CU6 for Exchange 2013, please read carefully and understand if your scenario has any simlarity with it.
The above script to be applied post the installation of CU6.
As active sync, one of the common technologies used for mobility of email, is used very widely now a days. So it is very important to know the volume of Exchange 2003 Active Sync (EAS) usage.
EAS logs a lot of data in IIS about what’s going on, but parsing out this will be a huge headache. To analyze the data we can use the Log Parser tool from Microsoft.
Download Log Parser tool from below link:
We can use SQL scripts to work with the Log parser tool to generate the hit ratio of EAS usage.
Note – We should enable the IIS W3C Extended Log File Format.
The output will also give you the details of user alias name of the users who are currently using the Exchange Active Sync feature. This way the EAS usage report can be generated.
As you aware, the receive connectors are created on server identity, and we might end up in creating similar receive connector in multiple servers for redundancy/disaster recovery purposes. You can easily export and import the RemoteIPRages from one connector to other by just following the following simple steps,
First of all, create the receive connector on the server where you want to import the RemoteIPRanges (relay IPs). Ensure you do the necessary settings for the receive connector properties, as we only import the remoteIPRanges not all configurations’.
new-ReceiveConnector -Name 'connector_name' -Usage 'Custom' -Bindings '0.0.0.0:25' -RemoteIPRanges 'x.x.x.x' -Server 'new_server_name'
Now, we have to export the RemoteIPRanges values from the other server that we need to import to this newly created receive connector.
Get-ReceiveConnector "EXH2\ connector_name" | fl remote*
If the result is truncated as seen in the above figure, you can set the value $FormatEnumerationLimit to display the complete list. The default value for this variable is 16. Set the value to a higher limit, or as shown below to get the complete list.
Now execute the Get-ReceiveConnector "EXH2\ connector_name" | fl remote* cmdlet to get the complete the list of IP addresses allowed for realy.
Copy the details into a notepad and format it by removing any additional space between the coma and the next IP address. This will look like below,
The input value also can contain the ranges as you may noticed, not only single IP addresses. Now you all set to import the data to the newly created Receive Connector, execute the below command (in the snapshot, I used separated IP ranges).
Set-ReceiveConnector -Identity "EXHDR1\ connector_name" –RemoteIPRanges 10.10.10.1,10.10.10.3,10.10.10.101-10.10.10.125
That’s it, you have now imported the complete list of relay IPs to the newly created receive connector. This way is really useful when you have more number of IPs individually allowed to relay emails through a receive connector.