Admins were happy after Microsoft introduced a new feature called online mailbox move, where the user mailbox is moved from one Exchange database to another in the same server or to a different database in different server in different site, or even in a remote mailbox move request user outlook connectivity is still untouched and only user required restart his client at the end after the move is complete with Exchange 2007 sp2 or later.
Below is a wonderful TechNet blog which showed me the background process of what exactly happening during this activity in detail with examples, read this to know more
Read here: http://blogs.technet.com/b/exchange/archive/2010/07/19/3410438.aspx
Microsoft did another enhancement with Exchange Server 2013 where the outlook connectivity is happening through RPC over HTPP ( outlook anywhere) and no more the CAS server / CAS Array FQDN is the RPC end point and now its the Mailbox guid and with this enhancement the users are no longer require to restart their outlook after the mailbox is moved or for a *over event the GUID remains the same and the Autodiscover service aligns itself to the changes in the back end and re-direct the connection accordingly .
Review the below Exchange Team blog post for clear details , review the Outlook Connectivity section and also this blog gives you an overview of other enhancements made in the Exchange Server 2013 CAS server role.
Read the post below:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Below is a wonderful TechNet blog which showed me the background process of what exactly happening during this activity in detail with examples, read this to know more
Read here: http://blogs.technet.com/b/exchange/archive/2010/07/19/3410438.aspx
Microsoft did another enhancement with Exchange Server 2013 where the outlook connectivity is happening through RPC over HTPP ( outlook anywhere) and no more the CAS server / CAS Array FQDN is the RPC end point and now its the Mailbox guid and with this enhancement the users are no longer require to restart their outlook after the mailbox is moved or for a *over event the GUID remains the same and the Autodiscover service aligns itself to the changes in the back end and re-direct the connection accordingly .
Review the below Exchange Team blog post for clear details , review the Outlook Connectivity section and also this blog gives you an overview of other enhancements made in the Exchange Server 2013 CAS server role.
Read the post below:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
No comments:
Post a Comment