On July 12 th , we announced that Exchange Server 2013 RTM CU2 contained an issue that could result in the loss of public folder permissions when the public folder mailbox is moved between Exchan...
Updated Jul 01, 2019
Version 2.0
Blog Post
Had a lot of issues with the latest update. After installing CU2 on an RTM Exchange 2013 system:
1. The POP service was sending out the wrong certificate. As crazy as that sounds, POP clients were getting the NetBIOS name of the cert rather than the certificate that was assigned the "P" services. Had to =$null the server certificate and edit the ehlo response of the pop service in order to assign the correct cert. This was working fine in RTM and broke in CU2.
2. OWA redirects broke. I believe we now have to manually delete the web.config file and re-set the redirects. That seemed to fix it. Hopefully there is a better answer.
3. The move-mailbox process introduced a new bug. You have to edit the conf file for the migration parameters to avoid processing delays. Someone set the default to timeout 480 times (each timeout taking 2-3 minutes). You have to set this value to 1.
4. During the move process we had to manually verify the log status of each move due to Exchange 2013 not cleaning up the source Exchange 2007 mailbox correctly. Fortunately the log showed that the AD switched correct, so we just cleared the move request for those users manually.
5. Once the update installed, we never could get Exchange 2013 to ever send back to Exchange 2007. We ended up doing a cutover migration of the mailboxes and the mX at the same time. Never did resolve that issue.
6. The public folder replication, of course, had problems. The PF migration always seems to have problems. We ended up just manually exporting and re-importing via the Outlook client.
7. Delegate automatic mailbox assignment appears to have stopped working. The clients do not automatically assign the mailboxes in the Outlook pane after ~60 minutes. Manually adding the mailbox appears to work.
8. Troubleshooting was made very difficult in some cases due to Microsoft now integrating ipv6 into their client, transport, and storage layers. Breaking the standard TCP/IP and/or ISO models really makes troubleshooting IP/NS issues much, much tougher.
There were other various minor issues.
Some questions:
a. The users hate the look and feel of the new OWA. They complain about the whiteness, non-3d look, and general lack of customizability. Adding a little row of "theme" across the top is not sufficient. Is there additional themes and/or color choices planned? Is that coming in SP1 or before?
b. The ECP appears pretty stark and lacks a number of critical features that must be done via PS. The admins really felt it was" a step backward" to go to Exchange 2013 from 2007. Their words. They also felt the ECP wasted half the space on the screen and was "way too white" as well as the OWA. Is the ECP going to be enhanced?
c. Where did all the cool neat GUI tools that were in the old Toolbox go and where is the BPA now? Are they ever coming back to Exchange 2013?
:)
Best,
- S....