Exchange 2019 CU2 has been released to the Microsoft download centre! Exchange 2019 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2019 and can be used to install a fresh server or to update a previously installed o… Read the rest “Exchange 2019 CU2 Released”
Exchange 2016 CU13 has been released to the Microsoft download centre! Exchange 2016 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2016 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 h… Read the rest “Exchange 2016 CU13 Released”
Exchange 2013 CU23 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 … Read the rest “Exchange 2013 CU23 Released”
Today is patch Tuesday for June 2019 and contains a security advisory bulletin for Exchange 2010. Due to the way that Exchange 2010 is serviced, security updates are released as a new update rollup (RU). Separate updates were also released for Exchange 2013, Exchange 2016 and Exchange 2019.
This is build 14.03.0461.001 of Exchange 2010, and KB 4503028 has the full details for the release. The upda… Read the rest “Exchange 2010 SP3 RU28 Released”
Earlier on this year you may have noticed a "not found" error page when visiting some of the older TechNet or MSDN blogs. If you were lucky, you would have received the graphic shown below. If not, then you would have had a nice and cryptic result code...
This was due to the blog team removing those blogs which were not moved over to the new TechCommunity. Only product group and team blogs were … Read the rest “So Long and Thanks For All the Fish {Possibly}”
At this point we are now one year away from the end of Threat Management Gateway (TMG) 2010 support. Many of Exchange administrators and architects will need to look at alternative solutions for publishing and securing Exchange, though this should have previously instigated.
TMG 2010 will exit out of extended support on the 14th of April 2020. Please plan accordingly.
Today is patch Tuesday for April 2019 and contains a security advisory bulletin for Exchange 2010. Due to the way that Exchange 2010 is serviced, security updates are released as a new update rollup (RU). Separate updates were also released for Exchange 2013, Exchange 2016 and Exchange 2019.
This is build 14.03.0452.000 of Exchange 2010, and KB 4491413 has the full details for the release. The upd… Read the rest “Exchange 2010 SP3 RU27 Released”
To remove duplicates using PowerShell is exceedingly straightfroward. However, I have a habit of forgetting the cmdlet so parking this here for future reference.
For example, we can use the Get-Unique cmdlet or Select-Object -Unique parameter.
As a simple example:
The Get-Unique cmdlet compares each item in a sorted list to the next item, eliminates duplicates, and returns only… Read the rest “Quick Tip – Get Unique Instances In PowerShell”
After installing Exchange 2013 CU22, you might notice that there is a cosmetic issue with how the update is listed in Add/Remove programs. In the screenshot below, note that Exchange 2013 Cumulative Update 20 is listed, but the version number is not the CU20 version number.
For reference the versions of the relevant CUs are shown below. Note that the above screenshot shows the CU22 version, but th… Read the rest “Exchange 2013 CU22 Shows Incorrect Name In Add/Remove Programs”
When looking at the details of objects in Exchange Management Shell, it is often useful to know when an object was created or modified. In a recent Office 365 engagement, the customer was convinced that one of the other administrators had made an unauthorised change to their environment as there was an apparent recent change to the Exchange Hybrid Object.
The details of the this object can be view… Read the rest “Incorrect or Misleading Exchange Attribute Date”