Outlook still pointing to old exchange 2010 server even after mailbox move
I have installed a SBS2011 server that I need to move mail to a dedicated exhchange server. I have installed exchnage 2010 on a dedicated server will all the exchange roles and updated both exchange servers to SP3.
I am able to successfully move a mailbox from SBS to stand alone exchange. However Outlook (on a terminal server) still points to the SBS server.
I know in the past when I have done SBS2003 to SBS2011 migrations that outlook automatically picked up the new server after moving the mailbox.
How can I make outlook automatically pickup the new server? )Without installing/configuring a CAS array, shutting down the old server, doing an outlook repair or recreating the outlook profile.)
I am able to successfully move a mailbox from SBS to stand alone exchange. However Outlook (on a terminal server) still points to the SBS server.
I know in the past when I have done SBS2003 to SBS2011 migrations that outlook automatically picked up the new server after moving the mailbox.
How can I make outlook automatically pickup the new server? )Without installing/configuring a CAS array, shutting down the old server, doing an outlook repair or recreating the outlook profile.)
If you have difficulties and you know your Exchange mail is where you want it, rec-creating the Outlook Profile is very easy to do. Send out clear instructions and have your users do it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Having seen your closure request, I don't think you fully understand what is involved with a CAS Array.
Step 1: Create DNS entry
Step 2: Create CAS Array (new-clientaccessarray)
Step 3: Adjust mailbox database configuration using set-mailboxdatabase
Job done - three minutes at most.
You have said a repair profile is required - that is exactly what is required to do either of the tasks, as I have said. However instead of having the clients pick up the real server address, they will pick up the CAS array address.
I still don't understand why you don't want to create an RPC CAS array? The clients need to be updated to something, so instead of an actual server they go to the CAS Array address. All future profile creations will use the CAS Array address.
As far as I am concerned, there is no reason I can think of why you shouldn't create a CAS Array.
Simon.
Step 1: Create DNS entry
Step 2: Create CAS Array (new-clientaccessarray)
Step 3: Adjust mailbox database configuration using set-mailboxdatabase
Job done - three minutes at most.
You have said a repair profile is required - that is exactly what is required to do either of the tasks, as I have said. However instead of having the clients pick up the real server address, they will pick up the CAS array address.
I still don't understand why you don't want to create an RPC CAS array? The clients need to be updated to something, so instead of an actual server they go to the CAS Array address. All future profile creations will use the CAS Array address.
As far as I am concerned, there is no reason I can think of why you shouldn't create a CAS Array.
Simon.
"Profile repair only is easier for all parties opposed to creating a cas array also."
A CAS array is not an "opposed to" option at all.
Whichever way you look at it, a repair of the profile is required.
Simon.
A CAS array is not an "opposed to" option at all.
Whichever way you look at it, a repair of the profile is required.
Simon.
ASKER
Profile repair only is easier for all parties opposed to creating a cas array also.
Automatically it will get connected to the new mailbox holder