Our developers have just found a solution to the problem with transport agent failures caused by Exchange Server 2013 SP1 update further described in this post. Microsoft is currently working on an official fix, but if you need a workaround right now, you can resort to instructions from our KB article.
The problem stems from improper formatting of assembly redirection policy files, which makes them unrecognized as valid XML files. Removing one invalid comment line from two config files located in the GAC folder fixes the problem.
Please note that we strongly recommend that you back up these config files before you make any changes.
Let us know in the comments or contact us directly if you have any questions.
EDIT: Microsoft has just officially confirmed that the issue is caused by SP1: support.microsoft.com/kb/2938053
No more than 30 days from now the CodeTwo team will be crossing the Big Pond to take part in the Microsoft Exchange Conference (MEC) 2014 – the world’s number one event for all things Exchange Server and Office 365 related.
This year MEC will be held in Austin, Texas between March 31st and April 2nd. We will be there the whole 3 days, talking to developers, Exchange admins and IT experts, presenting our newest solutions for Exchange and of course… giving away free t-shirts!
So, if you’re in Texas around the end of March, make sure to drive up to Austin and meet us at MEC 2014. See you there!
Note that this applies only to CodeTwo Exchange Rules 2013 or CodeTwo Exchange Rules PRO installed on Exchange 2013.
Please be advised that installing the Service Pack 1 update on Exchange 2013 has been reported to cause transport agent failures (for more information see this TechNet thread). It has been just confirmed that upgrading to SP1 with CodeTwo software being installed may stop the Exchange Transport Service on a given server.
Due to the above, we recommend putting off the installation of SP1 until the problem is resolved. Chances are that Microsoft will release an update that fixes the issue in a few days. Nonetheless, we are currently working on our own fix that should be available soon. Please check back on our blog for future updates – we will post an update as soon as we know more about the issue.
If you have any questions, please contact our Support Team directly. We are sorry for any inconvenience caused.
For more information, please consult this article:
UPDATE: The workaround is now available here: http://www.codetwo.com/kb/codetwo-and-exchange-2013-sp1
We have just released an update of CodeTwo Exchange Rules PRO and CodeTwo Exchange Rules 2013, 2010 and 2007. The latest version of the application solves the problem with adding disclaimers to emails sent from OWA after updating Internet Explorer to version 11, resulting from the new browser file format MSHTML11 .
We recommend that all users of CodeTwo Exchange Rules PRO, CodeTwo Exchange Rules 2013, 2010 and 2007 download the update and re-install the program on their servers. To install the update, please download the latest version of software from our website and launch it on the server. The old version of the program will be replaced with the new one and all previous settings will remain unchanged.
If you have any additional questions, please contact our Technical Support Team – we are available 24 hours a day from Monday to Friday.
Download CodeTwo Exchange Rules PRO 18.104.22.168.
Download CodeTwo Exchange Rules 2013 1.4.5
Download CodeTwo Exchange Rules 2010 2.4.5
Download CodeTwo Exchange Rules 2007 3.4.5
Learn more about updating CodeTwo software
Contact our Technical Support
We know exactly how difficult it can be to perform complete migration in an Exchange-to-Exchange scenario. Things get even more complicated when the source and destination servers are located in separate forests, or when it comes to migrating from Exchange 2003 directly to Exchange 2013. Having all these difficulties in mind, we developed and launched our Exchange Server migration tool back in May 2013. Our goal was to deliver software that can be helpful for an administrator performing Exchange Server migration. What we came up with is a migration tool that allows for quick and hassle-free mailbox migration between Exchange Server forests. It also comes in handy during intra-organizational migrations of users’ mailboxes and while migrating from Google Apps to Exchange.
Download free migration guide
Migrating Exchange Server isn’t just about moving/copying mailbox data. Especially when upgrading to Exchange 2013, an administrator has to take care of many other things, like hardware setup, server infrastructure design, new Exchange Server installation and configuration and so forth. Bearing all that in mind, our Exchange Server specialists teamed up with Konrad Sagala (Microsoft Exchange Server MVP) to create a PDF migration guide covering all the difficult aspects of upgrading to Exchange 2013. Our goal was to give you as much useful information as possible about migration planning and making a smooth transition to Exchange 2013. Did we succeed? Find out yourself!
Continue reading ‘Exchange 2013 migration guide and checklist – free PDF download’
Many companies rely on Microsoft Exchange Server’s public folders to store shared data, archive documents and collaborate on projects. At the same time, the native capabilities of Exchange Server do not allow users to view Exchange public folders on mobile devices. This wouldn’t be a major issue, if not for the fact that smartphones, tablets and other handhelds are gradually replacing laptops and desktops as primary workplace devices.
Luckily, CodeTwo has a solution: CodeTwo Exchange Sync. An application which allows you to automatically synchronize Exchange public folders with users’ personal mailboxes, making the public data instantly available on users’ mobile phones. Owing to this, Exchange tasks, contacts, calendars, and other outlook items, can be viewed and modified via devices running on iOS, Android, Windows Phone, or any other system supporting Active Sync protocol. Continue reading ‘How to make Exchange public folders accessible from your iPhone, iPad, Android or Windows Phone’
We have just released an update to CodeTwo Email Signatures – our email signature standardization tool for Office 365, Google Apps and hosted email. The new version (1.2.9) includes 4 minor improvements:
- The option to insert web located pictures into a signature has been restored for OWA, Office 365 and Google Apps policies.
- Shortcuts to Administration Panel and Client Apps now include the program’s name.
- The error message text in case the server connection cannot be established has been clarified.
- Changes in OWA policy settings (e.g. Automatically append a signature to outgoing messages) are now immediately updated to users’ accounts.
For more information about CodeTwo Email Signatures version history visit this page.
The update is free for all CodeTwo Email Signatures license owners. We recommend that users update their installations of the program, by downloading the latest edition and installing it on top of their current edition. Keep in mind that, after the update, client MSI packages will have to be generated and deployed anew.
If you have any questions, make sure to contact us. We are open 24 hours, 5 days a week.
Download CodeTwo Email Signatures 1.2.9
Control Office 365 and Exchange users’ Out of Office settings
CodeTwo Office 365 Migration has just been featured by J. Peter Bruzzese in his InfoWorld column as one of his three favorite tools for migrating to Office 365. That’s awesome news for us and a third great review of this new product that supports mailbox migrations from Exchange 2013, 2010, 2007 and 2003 and from Google Apps for Business.
We are seeing a lot of traffic to our website these days especially for products that support Exchange-to-Exchange migrations but Microsoft cloud email system migrations do not fall behind. Both of our migration tools are being constantly developed to deliver new features and to improve overall stability. New releases are due soon.
Learn more about the product and how to migrate to Office 365 for free.
And thanks, J. Peter Bruzzese!