Nearly two years ago, I presented a session called High Availability Design Considerations at TechEd North America 2010. During my session I described the changes we were making around how MAPI con...
Updated Jul 01, 2019
Version 2.0
Blog Post
Very very excited about this! I've had a few networking issues where databases would *over to the secondary data center and would knock my clients offline..this change will now allow me to correct the issue and restore service to the primary without taking clients offline.
I do have one question.. with cross forest Mailbox moves will ecWrongServer be issued after the move is completed to avoid resetting up outlook profiles and OST files? If so, would it be issued by the source server or the new destination server if autodiscover records get changed to the new server? I've always worked around the issue by deleting the registry value 001f662a and then doing an repair profile after autodiscover is changed.