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?

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)

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/

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

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.

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.

Microsoft exchange 2010 deployment planning guide

Dear All
I am seeking your guidance to accomplish this job.
First i would like to explain my exchange server 2010 oraganization.
1 no mailbox
1 no hub-cas server(both the roles installed in same server)
mailbox role running in physical machine and hub-cas server role running in hyper v machine.
Right now we are planning to deploy same one more setup for create DAG and give HA.
so i need your guidance for hardware requirement,software requirement and license(include future DR purpose) purchasing.
we are having 1500 mailboxes and 5 database.
planning to create NLB with uni-cost on HUB-CAS server.
please let me know if you require more details about my environment.
Parthiban selvaraj

WNLB is not recommended by Exchange Team. I suggest you install all 3 roles on both servers after upgarding RAM and buy a load balancer for load balancing CAS servers. Please check this for load balancers
http://technet.microsoft.com/en-us/office/dn756394.aspx
I would recommend reviewing the Exchange Role Calculator for Exchange (http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx)
after you ran a Get-MailboxReport (http://exchangeserverpro.com/get-mailboxreport-ps1-v1-02-released/) and MessageStats.ps1 (http://blogs.technet.com/b/neiljohn/archive/2011/08/09/user-profile-analysis-for-exchange-server-2010.aspx).
The MessageStats.ps1 and the Get-MailboxReport will give you the averages needed to fill out the sizing that the calculator requires.
After Installing the second mailbox/CAS/HUB server. Configure DAG
http://blogs.technet.com/b/winde76/archive/2011/03/23/step-by-step-create-a-database-availability-group-dag.aspx
Then configure CAS Array
http://exchangeserverpro.com/exchange-server-2010-cas-array/
MAS. Please dont forget to mark an answer.

Installing / Upgrading Exchange 2013 to Exchange 2010 with a o365 Hybrid environment

Hi
I am trying to install a new server with Exchange 2013 on an environment with an existing Exchange 2010 Sp3. Reason for that is that I have a o365 hybrid environment and need to disconnect my on-line and on-premise e-mail connection. I want to completely
run all my mailboxes on o365 no-longer dependent on on-premise exchange but the Exchange 2010 doesn't have a functionality to 'dismantle' the hybrid.. we need to have exchange 2013.
When I try to install Exchange 2013 I get an error message that I need to upgrade my o365 tenant. : my o365 tenant version is : AdminDisplayVersion : 0.20 (15.1.49.12) :IsUpgradingOrganisation : False.
Is there a better way of updating my environment.
Regards

Post the error from setup log for more information.
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.

Activesync URL in Exchange 2010 and 2013 co-existence environment

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks
Set it to the same externalURL as the 2013 ExternalURL .
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Remove Exchange 2010 DC from single server environment coexisting with Exchange 2013

My new Exchange server (2013) has completed all the migration steps including public folders. Mail is working well. I do not use the old DC running Exchange 2010 for any local domain logins or computer control, it is strictly for OWA as is my new Exchange
2013. I went through the uninstall of Exchange 2010 with out error but cancelled it after it said it was ready to uninstall. When I shut down Exchange 2010 server mail no longer is available. What am I missing? I am using same Public IP and different
private (192.168.1.4 new EXchange 2013, 192.168.1.7 for Exchange 2010) I changed these settings in my asa Firewall and that is working with new settings as well. Send and Receive connectors are on new while old one have been deleted. Do my MX records
need to be updated to reflect new server (ex2) as opposed to old server name (ex)?
You can come to Maui for a "Site Inspection" lol!
System Admin

Hi
You need to make sure all your DNS settings are correct with the new server IP as well as autodiscover. Remove any routing connectors between exchange 2010 and 2013.
Not best practice to run exchange on a DC but if you comfortable you have migrated all system mailboxes, user mailboxes and that the settings on your new server match the old one then proceed with the uninstall.
Your ISP will obviously route mail to your firewall as you are doing the NAT from there.

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.

Transport service does not start automatically after upgrade to exchange 2010 SP2 from Exchange 2010 SP1

Hi,
I am trying to upgrade Exchange 2010 SP2 from SP1, but Transport service does not start automatically.
Tried manually start services, it started successfully but again goes down within few seconds automatically.
Reboot server. but no luck.
Any help.
MD

Hi,
I recommend you use event viewer to check if there are any relate event logs. This may help us to find the cause.
In addition, as Amit mentioned, Exchange 2010 SP2 isn't supported by Microsoft, I think upgrading to SP3 is a much more sensible approach.
Thanks.
Niko Cheng
TechNet Community Support

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

Exchange 2010 deployment in Exchange 2003 Environment

Similar Messages

Maybe you are looking for