Migrating Exchange 2007 to Exchange 2010 at a different physical location - Suggestions??

Hello! I have a domain in Canada that is running Exchange 2007. My company wants to consolidate this Exchange and migrate the mail to the USA based Exchange 2010 in NYC. Not only is it migrating from 2007 to 2010, it's also moving locations physically.
Does anyone have any thoughts on how to best approach such a situation?

ok... in addition to sarvesh comments i would also add a checklist based approach .. please follow below link
http://blogs.technet.com/b/mspfe/archive/2014/03/20/checklist-upgrading-to-exchange-2010-from-exchange-2007.aspx this would help you not to miss anything in terms to critical or non-critical aspects.
after checklist i would suggest you give a shot at exchange server deployment assistant which will help you putting your scenario and suggesting the best practices. http://technet.microsoft.com/en-us/office/dn756393.aspx
this guide for planning of migrations also shows the full scenario step by step : http://exchangeserverpro.com/wp-content/uploads/Exchange%20Server%202007%20to%202010%20Migration%20Guide%20V1.0%20-%20Planning%20Chapter.pdf
this is also a step by step graphical representation for the process. THIRD PARTY LINK though.. http://www.petenetlive.com/KB/Article/0000236.htm
Let me know if this helps.
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Similar Messages

Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2

Hi,
We are planning cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2.
Requesting you to please help us out for below scenario.
Source Exchange 2010 SP2:- abc.com
2AD, 2CAS & 2 MBX servers
Database:- 4
Total Users :- 3500
Accepted Domains :- 8
Total Data:- 5TB +
Target Exchange 2010 SP2:- xyz.com
Resource allocated same as above.
Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.
With the guidelines mentioned in
http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-14203 we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into
OWA. It gives error “The Outlook Web App address
https://mail.abc.com/owa is out of date.”
Kindly let us know how to solve this issue.
Kindly let me know if you want any more information from our end.
Thanks in advance.
Thanks and Regards, Shashank Kudi

Hi Shashank,
Do you have certificates properly installed and configured in the target Exchange?
If not, Please configure certificate and import the certificate to the trusted root CA if you are using internal CA cert.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Migrate Exchange 2010 public folders cross forests

Hi,
Due to some Exchange and Active Directory issues (with remnants of old Ex 2003 server), we are going to migrate Exchange 2010 Mailboxes and public folders to a new Exchange 2010 Sp3 server, which is created in a new AD forest.
One thing we still have to decide, which is how to migrate public folders.
Apparently there are 2 ways:
1. To export PF data to PST and then import using Outlook in destination Exchange server
2. To use interorg replication tool to replicate PFs cross forest in target Exchange Server.
I would really appreciate if someone suggests which one is best. We have around 100GB of PF data.
Also, should we migrate Public Folders first? We think that we should move Mailboxes first.
Thanks in anticipation.
Regards, David Johnson

Hi,
Yes, when we decide to migrate from one Exchange server to another server, we need to move mailbox first.
About migrating public folders, both of these two solutions are available, I think that the first one is simpler.
Here is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/exchange/en-US/e3a23acd-efd2-4e51-bf4d-cb94b4b88a9f/exchange-2010-public-folder-cross-forest-replication-tool?forum=exchange2010
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrate OCS 2007 to Lync 2010 - different languages

Hi mates,
I´m going to migrate OCS 2007 to Lync 2010. OCS 2007 is in Spanish language and Lync 2010 will be installed in English.
Is it a problem?? Is possible migrate from Spanish to English??
Thanks.

Hi,
As I know, you can't migration OCS 2007 to Lync server 2010 with different languages.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Migration Exchange 2010 to Exchange 2013 in a different site

Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator

Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator
It is like any other Migration (Same Forest) You just need to make sure that AD is been replicated from Site A (Exchange 2010) to Site B (Exchange 2013).
No Network or replication issue between the sites. Having more than 1 DC on Site B would be good idea.
Once you have all these set, rest of the things are same.
Extend the AD Schema.
Deploy the Exchange Server 2013 CU6
Create the Cert request for 2013.
Install Cert on Exchange 2013.
Configure the Virtual Directories for Exchange 2013.
Test the Coexistence between 2010 and 2013.
Perform the Cutover from 2010 to 2013.
Test the Cutover and start the Test migration phase.
Once the test phase is fine, start the full fledge migration.
Move Mailbox and Public Folder Database.
Cheers,
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

Dear All,
I am starting the migration of Exchange 2010 2 servers (CAS/Mailbox) with DAG no CAS Array to Exchange 2013 with 2 servers CAS array and 2 Mailbox servers with DAG. I read on some blogs that no requirement of CAS array on Exchange 2013. My concern how to
configure NLB on CAS servers for the client to connect.
Please guide and have any deployment guide for this, kindly share.
Thanks

Hi ,
As you said there is no use and meaning of having the cas array in exchange 2013 and also thanks a lot to Microsoft for introducing an single namespace facility in exchange 2013.
My suggestion and Microsoft recommendation should be to go with hardware load balancers for exchange 2013 rather than using the windows NLB and round robin method.
Why we need to go for HLB ?
Disadvantages
of some load balancing methods :
Windows
NLB :-
If you use Windows NLB then it can provide redundancy on server level failure and not on application level.
DNS
round robin :-
In case if we use the windows round robin method for load balancing then it wouldn't provide server level
and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.
Configuring NLB for exchange 2013 :
http://msexchangeguru.com/2013/08/14/windowsnlb/
NLB configurations for exchange 2010 and 2013 will be same.
Configuring round robin for exchange 2013 :
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Advisable method is to have the CAS and MBX roles on the same box if NLB not comes it to play.Because windows failover clustering and NLB cannot be configured on the same box.In exchange 2013 cas role is a stateless server role so there is no need to have
that role on a separate box.
Thanks & Regards S.Nithyanandham

How to Migrate Exchange 2010 to 2013

am planning to migrate my existing Exchange 2010 Environment to Exchange 2013, My Existing setup as follows below.
2MBX Which is part of DAG, 1CAS/1HUB/1Archival MBX . Please advise me how to initiate and complete successfully.
OS : windows server 2008 R2 Ent.
Forest Functional Level : Windows server 2003
Domain Functional Level : Window server 2003
Also we have Gateway for external emails SPAM Filtering.
Thanks, Venkatesh. "Hardwork Never Fails"

You're in the Lync forums, I'd post this question in the Exchange forums:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrgeneral
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Questions about migrating Exchange 2010 to 2013

We currently have two Exchange 2010 servers with roles separated. One local mailbox server without CAS in our building and a CAS with no mailboxes in a remote datacenter.
We plan to migrate to 2013 with two new servers hosting all roles on each and then shut down the 2010 servers. There will be one local and one in a datacenter for Exchange 2013 so that either server could be individually restarted without internal LAN users
losing email access. (We do not want to open network access from the Internet to the onsite CAS). Is it practical to set it up this way?
How do we get the existing certificates (mail, autodiscover, and the local host name etc.) moved from the 2010 to the 2013 to the new servers when I assume they both must be running side by side for at least a short time while mailboxes are moved form 2010
to 2013? Will we need to buy new SSL certificates since the local host machine names for the Exchange server 2013 servers will be new and there will be more than one CAS?

Most of the CAs allow issuing duplicate certificate (as if you are requesting for a new cert) for the servers running same application. If your CA doesn't provide duplicates you can export the certificate and import to Exchange2013. http://msexchangeguru.com/2013/06/29/import-cert-e2013/
In certificate you dont need your internal FQDN. Especially in future you wont be able to add your internal FQDN in your certificate as most of the CAs wont allow you to add internal FQDN.
When you migrate to exchange 2013 you just need to configure the external URLs of Ex2010 in Ex2013 for both (i.e. same URLs for internal and external URLs) and point your common name and autodiscover to Exc2013 as Ex2013 will proxy the requests to your legacy
Ex2010 server. i.e. Your client interface will be Ex2013.
Please check this it will help you configure Split DNS and configure your URLs
http://exchange.sembee.info/2013/install/clientaccesshostnames.asp
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/ GUI
Configure split DNS to resolve external name from internal network.
Keep both Ex2010 CAS and Ex2013 CAS servers till all get logged in atleast once to connect to Ex2013 mailbox automatically.
As your DAG stretched across the data centers make sure
your DAG is in DAC mode.
http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
Please read this as well for details about DAG configured in multiple site
http://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
Ensure you use Exchange2013 SP1 as it is already released and available for download
http://www.microsoft.com/en-us/download/details.aspx?id=41994
Do you have a load balancer in place?
Regarding internet facing it depends. You can configure CAS2013 server in DMZ if you wish to.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Migrate Exchange 2010 to Exchange 2013, Need to defined win 7 users logon to Exchange 2010 & Win 8.1 users logon to Exchange 2013

Hi,
My organization have few win 7 and windows 8.1 clients. Now I want to migrate exchange server 2010 to 2013. And I don't want to remove exchange 2010 from the organization. Because I want to connect win 7 client through exchange 2010 and windows 8.1 user
connect to exchange 2013. Is there any way to define the win 7 users to connect to exchange 2010 and Windows 8.1 users to connect to exchange 2013?
Md. Ramin Hossain

The client connections are proxied to the mailbox servers that hold the mailbox.
You would need to have 2010 MBX servers with the mailboxes for the XP users, and 2013 MBX servers holding the mailboxes for the 7 users. And of course, the appropriate CAS servers.
Realistically, you need to migrate away from Windows XP. It is no longer supported.

Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

Hi guys (and girls)!
Hear me up. The idea is like this:
A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
bostjanc

Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
already answered by PS CL above
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
Just install the Edge Transport Server and make sure you install ADLDS services.
as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
Where Technology Meets Talent

Migrating Exchange 2010 to new hardware - Can't move mailboxes - Access Denied

I have installed Exchange 2010 on new machine, configured connectors, installed certificate, and tested without issue.
When I try to move a mailbox from old exchange server to new exchange server, I get the following error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
TestBox TestMailBox
Failed
Error:
MapiExceptionNoAccess: Unable to make connection to the server. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
Lid: 8600 dwParam: 0x5 Msg: EEInfo: ProcessID: 2640
Lid: 12696 dwParam: 0x5 Msg: EEInfo: Generation Time: 2014-01-02 17:32:11:828
Lid: 10648 dwParam: 0x5 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x5 Msg: EEInfo: Status: 5
Lid: 9624 dwParam: 0x5 Msg: EEInfo: Detection location: 701
Lid: 13720 dwParam: 0x5 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x5 Msg: EEInfo: NumberOfParameters: 2
Lid: 12952 dwParam: 0x5 Msg: EEInfo: prm[0]: Long val: 9
Lid: 12952 dwParam: 0x5 Msg: EEInfo: prm[1]: Long val: 0
Lid: 53361 StoreEc: 0x80070005
Lid: 51859
Lid: 33649 StoreEc: 0x80070005
Lid: 43315
Lid: 58225 StoreEc: 0x80070005
Lid: 50835
Lid: 62321 StoreEc: 0x80070005
Lid: 47987
Lid: 50033 StoreEc: 0x80070005
Lid: 52465 StoreEc: 0x80070005
Lid: 60065
Lid: 33777 StoreEc: 0x80070005
Lid: 59805 Lid: 52209 StoreEc: 0x80070005
Lid: 19778
Lid: 27970 StoreEc: 0x80070005
Lid: 17730
Lid: 25922 StoreEc: 0x80070005
Exchange Management Shell command attempted:
'domain.local/Users/TestBox TestMailBox' | New-MoveRequest -TargetDatabase 'Mailbox Database ######'
Elapsed Time: 00:00:00
I get similar errors when trying to view certificate on other server (old to new or new to old).
When I run: Get-ClientAccessServer | Test-MRSHealth - it retrieves local server info fine, but I get an access denied error trying to retrieve from old server.
I have searched and tried everything I could find to no avail. Any help would be greatly appreciated.
-Frank

1) Are you on a 2008 Server? If so you will need to right click and run as administrator on the EMC/Powershell you are using.
2) Did you Prepare the Legacy Permissions when you did the new Exchange install?
-http://technet.microsoft.com/en-us/library/aa997914(v=exchg.141).aspx-

Exchange 2010 Std. on Esxi 5.0 (suggestions for deployment)

Dear Experts,
Soon we will be starting process of moving from E2k3 to E2k10 and it is going to be on Esxi 5.0. In this regard, I have concerns are there some guidelines to follow for it exchange 2010 virtualization?
- How much size HDD when server holding , HUB, CAS and mailbox role?
- The above three roles on one virtual server are OK?
- Memory assignment for the virtual server
- The exchange DB should be where, on a RDM or as a second HDD to the virtual machine like a D:\ drive
- Edge transport should be on seperate virtual server?
- Backup is possible of exchange DB is on a RDM ?
Any other aspects since it is first time for us going for Exchange virtualization. I found vmware document for this E2k10, but any resource with easy understanding steps and to follow.
If more details are needed from my side, please let me know
Appreciate your responses for this.
Regards,

Hi Wajeeh,
Glad to see you're going down the path to virtualize Exchange 2010 on vSphere. You'll find that VMware has a ton of great resources to help you on this journey right here: http://www.vmware.com/go/exchange
It's very difficult to answer your questions without some context about your environment. When it comes to Exchange 2010 there really are no "generic" sizing guidelines. For example, there really isn't any rule of thumb to say that for 5,000 users you need xx amount of vCPU and yy amount of memory per server. You'll need to do some math from your environment to figure that out.
Thankfully Microsoft provides all of the numbers you'll need to figure out how much CPU and memory you'll need to size your servers. This link does a good job of taking you through some of the math you'll need to understand:
http://technet.microsoft.com/en-us/library/ee712771.aspx
In addition, Microsoft makes a calculator that you can use to plug in your requirements and it will produce the required amount of CPU and memory for your Exchange environment. Take a look here:
http://blogs.technet.com/b/exchange/archive/2009/11/09/3408737.aspx
To answer your other questions:
- Yes, you can combine the Hub Transport, Client Access, and Mailbox Server roles on the same virtual machine. You'll need to size for it so that you can ensure proper performance. See here for more info: http://technet.microsoft.com/en-us/library/dd298121.aspx
- The Exchange databases can either be on an RDM or on a VMDK attached to the virtual machine. It comes down to your requirements and if you're using a SAN based snapshot, backup, or replication tool. If you're not then I would stick wtih VMDK files.
- The Edge Transport server is designed to be at the network perimeter and not joined to your domain. You cannot combine it with other Exchange roles so you'll need to deploy it on a separate virtual machine.
I hope this helps. Read the Microsoft links to get an idea of how to size your environment based on your organization's requirements and that should give you a good start.
Matt
http://www.thelowercasew.com

I have AD and Exchange 2010 installed on different servers. can I control both with powershell from the AD server?

Hi all,
I have a lab env that include: 2 server 2012 with AD DS, 1 server 2012 with Exchange 2010, 1 server 2012 that I will install later Edge server.
I have a script that can build all my AD and Exchange infrastructure . This script was tested on single server that hosted both AD DS and Exchange.
My question is how to run the script let say from one of the AD DS servers and do his magic also on the Exchange server?
momu

Hi,
Take a look at this:
https://gallery.technet.microsoft.com/office/Create-a-new-implicit-5fdafe45
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

Migration exchange 2010 to hosted exchange 2013

Hello,
Tried to search for a good solution for what I need but always redirected to places of office365.
I will explain what i need and maybe you could find me a good solution.
I have several offices that i give IT support. Some of them with exchange 2003 and some with 2007-2010.
I want to migrate their servers to my new hosted exchange 2013 (multi-tenancy).
Is there a way to do CutOver migration?
What are my options?
P.s. All offices are working with calendars so PSTing their mailboxes is out of the question.
Hope you understand what i wanted to do.
Thanks for the help.
Lior.

For what you're planning, a cutover migration would be best. For that I would recommend a tool like Migrationwiz (http://www.migrationwiz.com). You can start the migration in advance, get the data copied
and then do a final incremental move on the cutover date. In addition to the mailbox move, you will want to synchronize the directories and ensure that the legacyExchangeDN property of the source mailboxes appear as proxy addresses of type
X500 on the target mailboxes or else they won't be able to reply to old mail or use Outlook contacts or cached addresses. I don't recall whether MigrationWiz can take care of that for you or not.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Migrating Exchange 2007 to Exchange 2010 at a different physical location - Suggestions??

Similar Messages

Maybe you are looking for