Move Mailbox from Exchange 2010 to Exchange 2010 (no DAG) - Client Outlook MAPI Profile still lists

Status
Not open for further replies.
M

MiKeDaDoC

Hi Folks,

i just finished migrating our Exchange from 2007 to 2010 using a " temporary" Exchange 2010 Server. the 2007 to 2010 part worked out like a charm, all Mailboxes, PFs and settings are there. so far so good...now I did an Exchange 2010 to Exchange 2010 " migration" ..ok its not a migration... i added another Exchange 2010 Server with the " final-to use" Servername and on the " final-to-use" Hardware to the Exchange Org. Everything seemed to work out. I could replicate (again) all of the PFs from the temp Exchange 2010 to the final Exchange 2010 server and so it was all good for the Mailboxes, now showing up correctly in the Database of the final Exchange 2010 Server...Recieve Connectors, userdefined Banners, Own Domain-certificate....everything is ok.

" Ok where's the problem?" you may ask...

So next step would be to verify that all Outlook Clients (2003 and and some 2007) would update their Exchange Server entry in the Mapi Profile to point to the final Server on first opening, just as they did when first migrating from Exchange 2007 to 2010.

Here is the point: Outlook won't change it. It is still having the Name of the temporary Server in the Mapi Profile regardless of user logut/login and restart of the client or the servers. Don't get me wrong, Outlook will still open the Mailbox without any Error and my Users are able to work with Outlook just as before..as long as the temp. Exchange Server is online. Sure thing, it's name is still in that Mapi Profile.

Workaround: Closing Outlook, changing the Server Name in the MAPI Profile of the client to what it should be, and restart Outlook....Of course Outlook will start and work the same, but now I am able to reboot or even shutdown/uninstall the temp Server. I may even give Outlook the name of the temp. Server and he will (this behaviour is by default) change it to the Name of the final Server....

So why isn't he able to do this in first place? Any Ideas, or is this a bug?! or am I missing something?

Any statement would be nice.

(just don't ask why I'm installing a so called temp. Server instead of migrating only one time from 2007 to 2010 and then use it.)Michael Saldaña IT System-Elektroniker, MCSE-M 2003
 
M

Mark Fugatt

What you need to remember is that in Exchange 2010, the clients do not connect directly to the mailbox role, they go through the CAS role, so it sounds like you need to set the RPCClientAccessServer to point to the new Exchange 2010 server.

Do this via PowerShell

GET-MAILBOXDATA | SET-MAILBOXDATABASE -RPCCLIENTACCESSSERVER <FQDN OF NEW CAS SERVER>Mark Fugatt Premier Field Engineer - Unified Communications Microsoft Services This posting is provided AS IS with no warranties and confers no rights
 
M

MiKeDaDoC

Hey, thanks for the answer,

shortly after posting this I read about rpcclienttaccessserver and changed it, but still the client will connect to the temp. Server.

I will soon try it again with a third Exchange to Exchange move...for now I disabled/uninstalled the temp. Server and created a c-name in dns until I'll change the clients manualyMichael Saldaña IT System-Elektroniker, MCSE-M 2003
 
B

Brian Day MCITP [MVP]

shortly after posting this I read about rpcclienttaccessserver and changed it, but still the client will connect to the temp. Server.

I will soon try it again with a third Exchange to Exchange move...for now I disabled/uninstalled the temp. Server and created a c-name in dns until I'll change the clients manualy

Once Outlook has established a connection it will not update itself unless you move the mailbox again to a different DB or do a " Check Names" in the Outlook profile. The rpcclientaccessserver attribute should preferably be configured before clients are moved to the box.Brian Day, Overall Exchange & AD Geek
MCSA 2000/2003, CCNA
MCTS: Microsoft Exchange Server 2010 Configuration
LMNOP
 
M

MiKeDaDoC

shortly after posting this I read about rpcclienttaccessserver and changed it, but still the client will connect to the temp. Server.

I will soon try it again with a third Exchange to Exchange move...for now I disabled/uninstalled the temp. Server and created a c-name in dns until I'll change the clients manualy

Once Outlook has established a connection it will not update itself unless you move the mailbox again to a different DB or do a " Check Names" in the Outlook profile. The rpcclientaccessserver attribute should preferably be configured before clients are moved to the box. Brian Day, Overall Exchange & AD Geek

MCSA 2000/2003, CCNA

MCTS: Microsoft Exchange Server 2010 Configuration

LMNOP

ok, sounds logical. Will try that on next " Test Move" .Michael Saldaña IT System-Elektroniker, MCSE-M 2003
 
V

Victor Welasco

Hy Guys,

I had the same problem, move-request between Exchange 2010 to Exchange 2010 with diferent RPCCLIENTACCESSSERVER on mailboxdatabase but the client Outlook still on old server. My enviroment is the same lake you, Exchange Migration from Exchange 2007 to Exchange 2010 temp Hardware every thing is OK, after this, I format my Exchange 2007 and Install new Exchange 2010 and move-request from Exchange 2010 (Temp Hardware) to new Exchange 2010 and client Outlook don&acute;t redirect profiles.

It&acute;s a Bug and not correctly yet, I receive this information from Microsoft.

I used the same workaround CNAME on dns server.

Att:

Victor Welasco Santana
 
M

MiKeDaDoC

It&acute;s a Bug and not correctly yet, I receive this information from Microsoft.

Ok, good to know about that. Thank you for that feedback.

Maybe its because I used the same " old" Servername as it was with Exchange 2007 in final Exchange 2010 Installation. (temp. Server got different name)

How was it in your case?Michael Saldaña IT System-Elektroniker, MCSE-M 2003
 
V

Victor Welasco

Yes, I migrate from Exchange 2007 (name SrvExch) to Exchange 2010 temp (SrvExch2010), after I formated my SrvExch and install a new Exchange 2010 with the same Old name used on Exchange 2007 SrvExch.

Att:

Victor Welasco Santana
 
J

jeremybnz

Any update on this issue? am having the same issue, moving mailboxes between multiple 2010 servers and mapi profile not updating unless you do the check name thing on the client...
 
J

jassonxp

HI Mike,

Could you please help me in the step to migrate public folder from exchange 2007 to exchange 2010?

I couldn't replicate & remove public folder on exchange 2007..

Thanks for your help!
 
Status
Not open for further replies.
Thread starter Similar threads Forum Replies Date
B Move mailbox from Exchange 2003 to 2010 Exchange Server Administration 2
M Exchange 2010 SP1 Hosted Mode - how to move mailbox from old organization? Exchange Server Administration 1
B Cross Forest Exchange 2007 to Exchange 2010 Mailbox Move question Exchange Server Administration 15
P Outlook folder path changing automatically when move or delete Item from custom task folder which is installed in Exchange 2010 sared mailbox Using Outlook 1
D How to move an exchange mailbox back from 2010 to 2003 Exchange Server Administration 2
F Exchange 2003 to 2010 Mailbox move Exchange Server Administration 1
M Sync Issues - Syncronization log in Outlook 2007 after mailbox move to Exchange 2010 from Exchane 20 Exchange Server Administration 11
F Exchange 2003 to 2010 Mailbox move Exchange Server Administration 4
D How do I move an Exchange 2003 mailbox to a new Exchange 2010 server Exchange Server Administration 2
A Move mailbox from Exchange 2003 to Exchange 2010 but crossed different forest Exchange Server Administration 2
J Exchange 2010 mailbox move request Exchange Server Administration 9
M exchange 2010 mailbox move Exchange Server Administration 3
O Exchange 2010 move-mailbox fails with MapiExceptionNoSupport Exchange Server Administration 22
T Possible to move a mailbox from Exchange 2003 Forest to a 2010 Forest, even if they are in separate, trusted doamins? Exchange Server Administration 1
A Error 0x86000108 after mailbox move from Exchange 2010 til Exchange 2003 SP2 Exchange Server Administration 3
L How to move an Exchange 2010 Mailbox database to another Exchange 2010 Server Exchange Server Administration 1
L Exchange 2010 SP1 move mailbox to Exchange 2003 fails Exchange Server Administration 3
B Event ID 1100 and 4 When trying to move mailbox from Exchange 2003 to Exchange 2010 Exchange Server Administration 4
H How to move Exchange mailbox items at local server to another providers exchange 2007 server? Using Outlook 1
S Exchange 2003 to Exchange 2010 Move Mailbox Issues Exchange Server Administration 2
M Exchange 2010 Mailbox move error - Property Expression 'Jim Smith' Isn't vaild - FQE=A169C2C1 Exchange Server Administration 3
E Cannot move from Exchange 2007 sp2 mailbox to Exchange 2010 Exchange Server Administration 25
A Exchange 2010 Move mailbox Cross Forest Exchange Server Administration 11
D Move Emails between Folders in Separate Mailbox Outlook VBA and Custom Forms 12
Q VBA Script to move item in secondary mailbox Outlook VBA and Custom Forms 2
J Automatically Move Old Items from a Shared Mailbox to a .PST on a Network Drive Outlook VBA and Custom Forms 1
T Messages no longer move to quote folder on shared mailbox after user adds -D to folder name Outlook VBA and Custom Forms 1
P move mails after send to central mailbox-sent items folder Using Outlook 4
K Outlook Cached Mode - can't create rules to move email to another mailbox Using Outlook 2
H Inter-Org Mailbox move Exchange Server Administration 1
C Mailbox moved 2003 to 2010sp1 but move request screen shows errors Exchange Server Administration 3
B move mailbox- autodiscover Exchange Server Administration 25
K Move mailbox from 2003 to 2010 smtp changed Exchange Server Administration 1
N Outlook - check sent items if messages sent from a specific account move it to another mailbox sent Using Outlook 3
J mailbox move Exchange Server Administration 4
A Outlook2010 - The emails stay in the Mailbox and doesn't move to the Personal folder Using Outlook 3
J move mailbox from 2003 to 2010 Exchange Server Administration 10
D move approval assistant mailbox Exchange Server Administration 4
V After Mailbox move a disconnected Mailbox is left behind in the old Database Exchange Server Administration 4
K The attempt to deserialize the move job from the system mailbox job queue failed. Exchange Server Administration 3
S Move mailbox from 2003 to 2010 in schedule Exchange Server Administration 3
A Move Users Archive To A new Mailbox Exchange Server Administration 1
M Error: This mailbox exceeded the maximum number of corrupted items that were specified for this move Exchange Server Administration 9
A Online Move Mailbox Move Failed Exchange Server Administration 1
C Move or Setup Server-Side Rules for Additional Mailbox Using Outlook 2
R mailbox move from 2003 to 2010 fails. Exchange Server Administration 2
R Should I move this mailbox? Exchange Server Administration 2
M mailbox move request Exchange Server Administration 16
T Move a mailbox to a different user Exchange Server Administration 8
S Mailbox move from exch2003 to exch2010 fail Exchange Server Administration 4
Similar threads


















































Top