Outlook Client CAS server does not change after users are moved to new database

Hi,

Since we moved to new office I have a very strange problem.  When I move a user from one database to another the Outlook does not change the CAS server.  I have to go manually change it.  This used to work without any issue, users used to get a pop up in Outlook that said they need to log off and log back and everything was fine.  Any idea where I should be start looking?

By the way I am running exchange 2010 SP2, with Rollup 4.

Thanks
FundFireAsked:
Who is Participating?
 
EEhotlineConnect With a Mentor Commented:
This might help you fix it:

http://clintboessen.blogspot.com/2011/10/outlook-2007-sp2-does-not-redirect-to.html

Also, You should also be using a CAS Array, even with a single server.

That way  we do not have to change the RPC Client access server parameter on the DB - just re-point the A record.  And since this will be a name that is only on your internal network and different from the server name, it will not impact HUB.

Generally, autodiscover will automatically populate the RPClientAccess on Outlook. If it does not work after the migration, we can recreate the problematical outlooks’ profiles except deleting the A record for the old CAS server.

For more information about RPC Client Access connectivity issues:

http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx

http://blogs.technet.com/b/exchange/archive/2010/05/20/3409978.aspx

http://blogs.technet.com/b/exchange/archive/2012/03/28/demystifying-the-cas-array-object-part-2.aspx

 Hope it can help you.
0
 
EEhotlineCommented:
Do you have a CAS Array?
0
 
FundFireAuthor Commented:
No.  Because the servers are in the different network.
0
 
FundFireAuthor Commented:
Thanks.

The issue was really NETWORKig.  We did not have ports open enough.
0
All Courses

From novice to tech pro — start learning today.