27 มกราคม 2554 15:46
I have succesfully (somewhat!) migrated from Exchange2003/2007 Environment to Exchange 2010 loadbalancing environment. Actually the load balancing works (using VM from loadbalancer.org) and everything concerning DAG works.
When moving a mailbox from the old Exch2007 server to the Exch2010 servers the outlook profile doesn't get updated to point to the new CAS array I have defined. If I manually make the change to the profile, everything works, so I guess that it is a relatively small issue I have here :)
This: "Get-MailboxDatabase DB|fl RpcClientAccessServer" return the correct CAS-Array on all of my DB's
As far as can see in one of the other answers I might be using this to solve it, but I am not sure:
Anyone who knows what i am doing wrong/missing here?
Best regards Jorgen
27 มกราคม 2554 17:19
i believe it would need some user intervention from outlook to switch to new exchange server, once the mailbox move is complete
if you test email autoconfiguration from outlook do you get exchange server 2010 urls ?. if not the user AD attributes replication has yet not completed
- ทำเครื่องหมายเป็นคำตอบโดย JorgenD1 31 มกราคม 2554 9:08
27 มกราคม 2554 18:18
Well, when I upgraded from Exchange 2003 to Exchange 2007 no intervention was needed, and I don't think that it was necesarry in my test environment.
It is not possible for me to check for the AD attributes because Outlook not will start. Outlook states that "Exchange is not ready and you should wait 30 minutes". I have waited 30 minutes without any change. But off course you might have a point in that AD not has had the time to replicate.
I will try and move a mailbox to night and see if it is accesible tomorrow morning.
"I'l be Back!"
27 มกราคม 2554 20:54
If you already have mailboxes on the Exchange 2010 platform and then configure the CAS array afterwards, then Outlook will NOT update to use the new name. That is documented on Technet. You have to repair the Outlook profile to get the name updated.
If you had configured the CAS array before you moved any mailboxes, then when the clients connected for the first time, they would connect to the CAS array host.
The CAS array doesn't replace anything. It is just an additional way of connecting. Therefore the address Outlook was using originally, which is actually the address of the CAS server (all clients now go through CAS) still works and is still valid.
There is no way to get Outlook to update without doing a repair of the profile, or moving the mailbox to another Exchange server and then moving it back.
Simon Butler, Exchange MVP
Blog | Exchange Resources
31 มกราคม 2554 9:11
You where completely right. I just had to wait for AD to fall into place before opening Outlook.
Now i just move mailboxes at night and in the morning the outlook profile has been auto configured so that it points to the new CAS array.
Thanks for helping:)
30 เมษายน 2555 4:39
well thanks for all your replies,
my setuation is, i configured ex2010 with casarray and dag and then i moved all mailboxes
then the users started their outlook and worked fine, after one week they requested to change the casarray name because it was too long "outlookcasarray", so we changed the name to "exchange" then the users get disconnected to the exchange ..
now how i will let the clients take the new name of casarray????
is it the only way is by repairing the outlook? they are 600 users :(
30 เมษายน 2555 5:20
what if i returned the settings back to the old casarray would it work?