posts - 104 , comments - 115 , trackbacks - 0

My Links

News

Disclaimer: Right here... Github: Code all the things! PS GUI Series: < Coming Soon! > PS Scripts: < Coming Soon! >

Tag Cloud

Archives

Post Categories

Blogs

Forums

Lync

Storage

Tools

Virtualization

Web comics

Issues with CU6 for Exchange server 2013: An update

Databases unexpectedly fail over in a co-existence environment with E2007: This is an issue that has come up after the release of E2013 CU6 recently. The details of this issue are available in the KB article linked below. A fix is also available for this issue from Microsoft Support.
KB:2997209 - Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007

Exchange Online mailboxes cannot be managed by using EAC after you deploy E2013 CU6: This is another issue that has come up after the release of E2013 CU6 recently. The details of this issue are available in the KB article linked below. A script is also available for this issue from Microsoft Support. IF you installed Exchange in an alternate location (other than the default) then you would need to modify the directory path in the script.
KB:2997355 - Exchange Online mailboxes cannot be managed by using EAC after you deploy Exchange Server 2013 CU6

You cannot route ActiveSync traffic to E2007 mailboxes after you upgrade to E2013 CU6: This is an issue that has come up after the release of E2013 CU6 recently. The details of this issue are available in the KB article linked below. A fix is also available for this issue from Microsoft Support.
KB:2997847 - You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6

NOTE: Another issue that we have seen only from some E2013 On-Premises customers who installed fixes for any of the above E2013 CU6 related issues is that “Using OWA, users cannot create new messages or reply to existing messages” – These are mostly installer issues where OWA files are not copying correctly in the new version directory. Ideally the content of these two folders, i.e. “V15\ClientAccess\Owa\prem\15.0.995.31” and “V15\ClientAccess\Owa\prem\15.0.995.29” should be identical, now if for any reason, they are not then it can break the OWA experience like described above. Take these steps if you run into related issues:

  • Backup the contents of “15.0.995.31” folder to a different folder/directory
  • Copy the files and folders from “15.0.995.29” to “15.0.995.31” folder – this should fix the issue …

Print | posted on Tuesday, September 9, 2014 4:02 PM | Filed Under [ Exchange News ]

Feedback

No comments posted yet.
Post A Comment
Title:
Name:
Email:
Comment:
Verification:
 

Powered by: