One week after releasing Exchange Server 2013 Service Pack 1, Microsoft released a fix for a bug after receiving customer complaints.
The bug, which prevents third-party or custom-developed transport agents from working with Exchange 2013 SP1, is caused by invalid XML code in global assembly cache policy configuration files. The company released a new PowerShell script that corrects the formatting error in the built-in Exchange 2013 configuration files that govern transport extensibility.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Microsoft says admins should be able to just run the script if they’re upgrading existing Exchange 2013 installations with third-party agents installed in Exchange 2013 SP1. However, if they’re installing Exchange 2013 SP1 on a new server, it’ll require a few more steps.
Exchange experts have taken notice of the bug and how it affects Microsoft’s image. Exchange MVP Tony Redmond wrote in his blog about how the bug brings Microsoft’s testing processes into question, and this isn’t the first time they’ve been questioned. Back in August, the company’s testing processes were in question when it pulled an Exchange update after revealing it didn’t test the update in its own environment.
We’ll continue to follow additional developments about Exchange 2013 SP1.
Have you had firsthand experience with the bug affected Exchange 2013 SP1? Let us know in the comments below or on Twitter @ExchangeTT.