Migrating from Shared/Hosted Exchange 2010 to Onsite Exchange 2013

Hi All,
Hoping for some advice regarding a migration project I'm due to run with. A client has their current email data with a 3rd party hosted Exchange platform, this is a completely separate platform from their onsite AD infrastructure.
Platform wise it is built on Exchange 2010 that only really allows OWA/Outlook Anywhere/ActiveSync access. We'd like to migrate this platform to a more dedicated onsite Exchange 2013 platform.
Any software tools or advice appreciated, we're hoping to avoid exporting all the content to PST and manually importing but if this is the only way then fair enough. If there are utilities that may allow mailbox backfilling to suck the data out and in to
the new mailboxes in 2013 that would be awesome.
Thanks in advance!

Hi,
According to your description, my understanding is that you want to migrate mailboxes from the other forest to your forest.
I recommend you refer to the following article to achieve migration:
http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
Thanks

Hi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

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.

Exchange 2010 in a Exchange 2013 Environment

I am trying to install Exchange 2010 in an Exchange 2013 environment which was migrated from Exchange 2007 earlier.
Exchange 2010 sp1 Mailbox and Hub roles installed fine however I cannot install the CAS role. Saw some references to change the OAB to a non exchange 2013 version - however that is the only version we have = OAB 2013.
This is the error I get:-
Error:
The following error was generated when "$error.Clear();
get-OfflineAddressBook -DomainController $RoleDomainController | where { $_.IsDefault } | Enable-OabWebDistribution
" was run: "The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).".
The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:02:15
Finalizing Setup
Cancelled
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Hi,
Please temporary remove all the OAB objects then try re-install the CAS server again.
After installing CAS server, we can re-build the OAB on Exchange 2013.
More details in the following articles:
Remove-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/aa995963(v=exchg.150).aspx
New-OabVirtualDirectory
http://technet.microsoft.com/en-us/library/bb123735(v=exchg.150).aspx
Hope it is helpful.
If the CAS server still cannot be installed, please post the details of setup log.
Thanks
Mavis

Exchange 2010 deployment in Exchange 2003 Environment

Hello,
I have recently installed Exchange 2010 in an Exchange 2003 environment. I need some help migrating all my settings over to Exchange 2010
-- mailboxes, recipient policies, offline address book, free/busy, etc.
I have looked at these following TechNet sheets for assistance, but getting a bit confused:
http://technet.microsoft.com/en-us/library/aa996719.aspx (Exchange 2013 System
Requirements)http://technet.microsoft.com/en-us/library/ee332348.aspx (Upgrade
from Exchange 2003 Client Access)http://technet.microsoft.com/en-us/library/aa998186.aspx
(Exchange 2003 - Planning Roadmap for Upgrade and Coexistence)http://technet.microsoft.com/en-us/library/ee681662.aspx (Install
Exchange 2010 in a Mixed Exchange 2003 and Exchange 2007 Organization)
I have two domain controllers. Exchange 2010 is not installed on a DC, but Exchange 2003 is on one of them. I want to eventually decommission
the Exchange 2003 environment and implement and Edge Server in its place. Exchange 2010 is installed on a Virtual Machine. It's running SP3, the latest service pack. Exchange 2003 is on a physical machine and it's running SP2.
Please help me simplify what exactly I need to do to migrate 2003 configurations over to 2010.
Thank you for you much appreciated assistance.

Hi
I would install a new DC and seize the MSO roles to the highest server. Remember you can install server 2012 but not R2 yet.
You can setup your connectors on exchange 2010 to send/receive mail to the internet. make sure your ISP allows the new server.
You can also setup a routing group connector so that mail flows from EX2003 to EX2010 and vice versa during your transition period.
Remember to replicate your public folders to the new server and if you have a lot of data be patient. Once you happy with everthing then decomission the old DC.
Hello,
All FSMO roles are transferred (not seized) on my Windows 2008 R2 Standard Domain Controller. I transferred all the roles off my Windows 2003 Domain Controller. The W2K3 DC is also my Exchange Server 2003 SP2. I specifically did not want to
install Exchange 2010 on a DC. It's on its own member server.
Should I make the Exchange 2003 Server a Front-End Server when I create a routing group for mail flow to Exchange 2010? I want to eventually implement an Edge. Also, can I have mail flow from the Internet directly to the Hub and bypass the Exchange
2003 mail flow?

Uninstall/Reinstall Exchange 2010 in coexisting Exchange 2003

Hi,
Can we uninstall Exchange 2010 without any affect to Exchange 2003 in the co-existing environment? I installed Exchange 2010 in existing Exchange 2003 and tried to configure for both Exchange exist in our domain. Somehow the Exchange 2010 crashed
and now it cannot start, only stuck in Initializing process. I want to uninstall and then reinstall but I don't know if doing this will cause any problem to the Existing Exchange 2003. Could someone tell me?
Thanks,
Jim

You don't have to uninstall and reinstall server, just rebuild base server with OS with what it had earlier and recover Exchange 2010 with /m:recoverserver switch.
Recover an Exchange Server
I assume you still have Exchange 2010 database backup or original files for restore if needed and this is just OS crash and can not be repaired scenario
Blog:
http://exchangeshare.wordpress.com/

Calendar Sharing between 2 organisation Exchange 2010 SP3 and Exchange online with Federation Trust.

Hi...
Our company is running Exchange Server 2010 SP3 Standart would like to have Shared calendar with organisation running with Exchange online.
We made a Federation trust between organisations and I checked that one certificate was installed and the rule for their domain was created. but when I try to share my calendar I always receive.
"Calendar sharing is not available with the following contacts because of permission settings on your network."
Name I took from GAL or input manually and always same. Forgot to mention that we migrated from Exchange 2003 to 2010 SP3 and all old exchange servers I removed. I tried everything that I know and read and nothing helped.
Hope for your support.
Thank you.

1)I deleted everything and made step by step as indicated in your articles.
2) recreated organisation relationship:
RunspaceId : xxxxxxxxxx
DomainNames : {xxxxxxx.microsoftonline.com, xxxxxxxxx.onmicrosoft.com, xxxxxxx.com}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel : LimitedDetails
FreeBusyAccessScope :
MailboxMoveEnabled : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel : None
MailTipsAccessScope :
TargetApplicationUri : outlook.com
TargetSharingEpr :
TargetOwaURL :
TargetAutodiscoverEpr : https://pod12312.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact :
Enabled : True
ArchiveAccessEnabled : False
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : xxx
DistinguishedName : CN=xxx,CN=Federation,CN=uxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=uxxx,DC=com
Identity : Lxx
Guid : a8xxx
ObjectCategory : upxxs.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass : {top, msExchFedSharingRelationship}
WhenChanged : 27/01/2015 3:23:47 PM
WhenCreated : 26/01/2015 9:41:39 AM
WhenChangedUTC : 27/01/2015 8:23:47 PM
WhenCreatedUTC : 26/01/2015 2:41:39 PM
OrganizationId :
OriginatingServer : xxx.upxxxns.com
IsValid : True
3. Configured Sharing Policies:
[PS] C:\Windows\system32>Get-SharingPolicy
Name Domains Enabled Default
Default Sharing Policy {*:CalendarSharingFreeBusySimple} True False
Lxxx {lxxx.com:CalendarSharingFreeBusy... True True
added my mail box to sharing policy but in the end receive same error
Calendar sharing is not available with the following contacts because of permission settings on your network.
In EventViewer everything seems to be fine....
No errors on policy creation... How can be checked this permission
settings on your network they are on exchange on in DC ?

Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 53361   StoreEc: 0x977
    Lid: 51859
    Lid: 33649   StoreEc: 0x977
    Lid: 43315
    Lid: 58225   StoreEc: 0x977
    Lid: 39912   StoreEc: 0x977
    Lid: 54129   StoreEc: 0x977
    Lid: 50519
    Lid: 59735   StoreEc: 0x977
    Lid: 59199
    Lid: 27356   StoreEc: 0x977
    Lid: 65279
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
   0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName        : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!

Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
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.

Exchange 2010 SP3 cohabitation Exchange 2013 ecp?exchver=15 from external not work

Hi
i have installed an exchange 2013 cohabitation with exchange 2010 for migration. outlookanywere,ecp,owa, autodiscovery...etc are configurered
when i try to connect to the eac or owa internaly its work, but when i try to do externaly https://mail.mydomain.com/ecp?exchver=15
i have error 302, 301 to many redirections
how can i fix this
thanksin advance

Hi,
Generally, status 301 means that the resource (page) is moved permanently to a new location. Please refer to Sneff_Gabor's suggetsion to check the Redirect setting s for OWA and ECP in IIS manager.
Additionally, please provide more information about your issue and collect any error logs for further troubleshooting.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Please Help!! Lists and libraries suddenly blocked just before migrating from SharePoint 2007 to 2010

Hi all,
I took several weeks preparing the migration of a large farm from SharePoint 2007 to 2010 using the system of restore databases and mount site collections. I've built the new farm and I have done several full migration tests to verify that all was well the
day of final migration.
The farm consists of three virtual servers: one with SQL Server 2012 and two with SharePoint Server 2010. Upon completion of the tests we've moved the servers to another network. We have turned on the servers and everything seems to work fine.
Just the day of the final migration I wanted to check the HealtReports list of the Central Administration, and when I wanted to look up an alert, the view window has not shown me anything and ribbon has appeared with all options grayed. Days ago worked fine.
Alarmed by this, I have started to check all lists and libraries in the Central Administration and the same happens. I can not view or change the items, nor add. Neither I can change the properties of the lists or libraries, as if everything was locked. I
tried on the main site collection and same thing happens, and I have tried with several user with Total Control permissions. I have also verified that the site collection was not in ReadOnly mode.
I have restored a site collection from SharePoint 2007 and have migrated successfully to 2010. Before applying visual upgrade I found that the content is also locked. It is as if he had changed anything in the configuration of the whole farm, but I can not
find what. The Event Viewer of the three server shows no errors related to this. The SharePoint LOGS not show anything unusual.
I do not know where to look and urges me to find a solution because the old servers must be out of service soon. I accept any suggestions.
Kind regards.

Finally I answer myself because I've already found and fixed the problem. Before moving the servers in farm to the another network I've unplugged the single SharePoint server from the farm database for to clone it. Apparently
this disconnection removes all the implemented solutions and the farm remains without servers. Reconnecting the servers not re-implements the solutions. When I was about to create a new farm I have seen that all solutions were not implemented,
I have implemented one by one and the system worked again.
If any of you happen reaches you, now you know what it may be due.
Kind regards!! Now I'm a happy man! ;)

Questions about upgrading from Exchange 2010 RTM to Exchange 2010 Service Pack 3

I am preparing to perform an maintenance upgrade on our current Exchange 2010 Server, to Service Pack 3 (and any post-SP3 roll ups), but I have a couple questions about the process.
Current Exchange Server details:
Exchange 2010 Standard
Version: 14.0 (Build 639.21) - from Exchange Management Console
Version: 14.0.702.4000 - from Outook client
Active Directory forest and domain levels: Windows 2008 R2 native
The questions I have are:
1. Can I assume that because it's version 10.0.702.4000 I am on Exchange Server 2010 RTM Update Rollup 4?
2. Can Exchange 2010 Standard RTM be patched directly to Service Pack 3, or would I need to perform incremental patches (i.e. SP1, SP2, etc.) before going to SP3?
3. Do I need to manually perform the AD domain schema prep before applying Service Pack 3, or will the Service Pack 3 update process automatically handle the modifications of the AD schema?

Hi,
Here are my answers you can refer to:
1. Firstly, I’d like to explain , we can use connection status to check our Exchange server version from Outlook client:
http://office.microsoft.com/en-in/outlook-help/determine-the-version-of-microsoft-exchange-server-my-account-connects-to-HA010117038.aspx
And I check my version from both EMC and Outlook client. It’s same.
2. We can directly update RTM version to SP3 , and the update will take an additional 30 minutes or longer per database.
3. Since Exchange 2010 SP3 makes updates to the Active Directory schema, we need prepare AD domain schema. However, it will automatically prepare AD and the domain when you install the update.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Exchange 2010 coexist with exchange 2013

Hi All ,
Planning to have a coexistence scenario in my environment which is mentioned below
Exchange 2010 - ambiguous url in place - OA enabled
For mapi/rpc traffic - mail.domain.in - exchange 2010
For https traffic - mail.domain.in - exchange 2010
mail.domain.in will get resolved in to cas array in exchange 2010 .
After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
Note :
On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
exchange server via exchange 2013 server.
question : I would like to know above mentioned scenario is possible or not ?
On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
All of you tell me your valuable suggestions.
Regards
S.Nithyanandham

Hi,
Going Straight to the point... and answering your question...
The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
As per Exchange Team...
In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
their DNS cache expires after the shared FQDN is moved to CAS 2013.
As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
fix existing Outlook clients with the old value in the server field.
So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
Outlook 2013: 15.0.4420.1017 (RTM or later)
I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx>
Hope it can help you!
Cheers,
Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

This is somewhat of an emergency, since Exchange is down completely for us right now.
I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
The plan was this:
Install Exchange 2013 on another server (Windows 2008R2)
Wait until everything is replicated
Remove the Exchange 2010 server from the organization
Uninstall Exchange 2010
Install Exchange 2013 on the Windows 2012 server
Wait until everything is replicated
Remove Exchange 2013 from the Windows 2008R2 server
But here is what actually happened:
Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
At step 11 of 15 (not sure what that was, though), received this error message:
Error: The following error was generated when "$error.Clear();
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
" was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.".
And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
but stays at 0%. But here is the most immediate issue:
Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
variables with variations on this error:
"...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
netsh (windows exe)
sc.exe (windows exe)
hostname (windows command that returns workstation name)
These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
argument to remove it instead.
At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

Cant open Exchange 2010 mailboxes by Exchange 2013 user, using MFCMAPI tool

Hi,
I
want to create superadmin user, which is capable of accessing all mailboxes in AD.
With
this account, I want to open information store of each mailbox(from MFCMAPI).
I am facing issue, while opening Exchange 2010 user's mbx , if superadmin hosts on Exchange 13 and vice-versa.
I
tried
Get-MailboxDatabase
| Add-ADPermission -user Domain\User -AccessRights GenericAll -InheritanceType All
and
Get-MailboxDatabase
-includepreExchange2013 | Add-ADPermission -user Domain\User -AccessRights GenericAll -InheritanceType All
*This
is not for blackberry
ManojK

Hi Manoj
Mostly looks like permission issue
Check the ACL permission for the account (super admin) by running get-mailboxPermission | FL
Give it extended rights to the (super admin) account which i guess it will not be present which causes this issue to happen
Get-MailboxDatabase | Add-ADPermission -User <service account> -AccessRights ExtendedRight -ExtendedRights
Also try with this KB article last step -
http://support.microsoft.com/kb/2465292
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Configure new exchange 2010 while old exchange 2003 running ?

Hello,
I'm in the process of deploying a new fresh installation of SBS 2011/Exchange 2010 server. Currently
I have SBS2003/Exchange 2003 running. I want to retired the server and replace with the new server. No migration. By doing that, I am setting up the new server SBS2011 name/domain/ip everything the same as the old server and will replace once all the configuration
is completed.
1. Since they both using the same domainname/ip, can I setup the new server Exchange 2011 while the old
server is alive? If yes, how's the process?
2. If I export and import users email in .pst (on user outlook client) and when the new server is put in place alive does it will regenerate the database
in new Exchange 2011?
Thanks in advance =)

For the 1st question, both servers are in different/isolated network. So you were saying yes i can do that correct? will not going to have any issue running both servers having all the same configuration while configuring the new server up?
the 2nd. since i am not migrating, i am planing to export/import user email from outlook client and when i replace the old server with the new server, i setup the user email client and import the .pst back.

Migrating from Shared/Hosted Exchange 2010 to Onsite Exchange 2013

Similar Messages

Maybe you are looking for