Exchange 2003 will migrate to Exchange 2010 or Exchange 2013

Hi,
Exchange server is on exchange 2003 on windows 2003 R2.
I had an architecture of parent & child domain controllers, Where parent company is closed Down. But we have an additional Domain Controller
of parent DC in our premise.
Due to this fact exchange organization is also unavailable & cannot make modification on my exchange server configurations (Global Settings, such as changing recipients attachment restrictions, everything is grayed out).
Is there any way where we can have staged migration. I mean can I keep old & new server running together & keep few users on new Exchange organization & rest of them be on an existing server itself. (I tried testing this too, but email delivers
to mailbox store, so, it checks a name & say “Mailbox not available”)
If I create a new domain environment, I have challenge of migrating users (This I can achieve with ADMT, but actual story starts with mailbox migration)
Real pain is, I have more than 500 users, can I achieve direct migration over a weekend. (few are POP & OWA users, around 50)
Can anyone help in this please.
Imran

So, you have exchange 2003 which is inaccessible! Database files .EDB and .STM is there, but Mailboxes are not available.
And you are planning to create new environment (As you don't have any other option).
This is a cross forest migration. Which exchange you are planning to install in new environment? I would suggest 2013.
The only available option you have (As current environment is Inaccessible), Export the PST from EDB files.
Create Mailbox on Exchange 2013 and Import the PST.
Do you have Public Folder Database?
If yes, apply the same process on it.
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.

Similar Messages

After Migrating from Sharpoint 2010 to Sharepoint 2013 list filter options changed

Hi All,
After migrating from SP 2010 to SP2013 i found list View filter option is changed and filter is not working Pls help its really urgent.... you can check field 1 and field 2 in following screen shot.
Prasad kambar

Hi ,
According to your description, my understanding is that your list filter cannot work after Migrating from SharePoint 2010 to SharePoint 2013.
For your issue, please check your log files for any issues. Also you can refer to the blogs for troubleshooting SharePoint 2013 migration:
Firstly try running Test-SPContentDatabase on your source database for any issues -
Test-SPContentDatabase - http://technet.microsoft.com/en-us/library/ff607941.aspx
Troubleshoot site collection upgrade issues in SharePoint 2013 http://technet.microsoft.com/en-us/library/jj219648.aspx
Verify database upgrades in SharePoint 2013 -http://technet.microsoft.com/en-us/library/cc424972.aspx
And please have a look at your custom solution on your site.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Migrating from SP 2010 to SP 2013

I m new to sharepoint and our new project requirement is to migrate the contents from SP 2010 to SP 2013. we r not going to use any tools , so if we go manually what would be the approach to migrate the custom data to the next version. there is lot of custom
data like features, event recievers, webparts that we have to take care of . do we have to code them again or what .
in depth reply or even some forums link will do . thanks

Check out
http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=124
All customizations will have to be tested again though, you can't expect them to work correctly. I would start by creating a list of customizations that have to be upgraded and still need to be supported
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Change GUIDs when migrating from SP 2010 to SP 2013?

When migrating custom list schema from SP 2010 to SP 2013, do I need to change the GUIDs for all the fields or can I use them as is?
Thank you!

Hi,
After migrating SharePoint 2010 to SharePoint 2013, all the GUIDs of the sites and lists would change.
If you just wanted to use the list in the site, it would have no impact on the lists, all the custom lists would work well.
However, if you have some functions or solutions based on the GUIDs of the lists, you should change all the GUIDs for all the solutions.
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Mixed environment migration (OCS\Lync 2010 to Lync 2013) retaining BES Integration

Hi All,
I have an existing OCS 2007R2 and Lync 2010 environment which contains BES Collaboration for Enterprise IM on Blackberry devices. I want to migrate this environment to Lync 2013 whilst retaining the BES integration. Understanding that tri-existence is not supported
I've been going through the process of decommissioning all of my legacy OCS servers, which I have now completed, in readiness for starting the Lync 2013 deployment and prepping AD.
Here's my issue - The BES collaboration service was integrating with an old OCS CWA server. I removed the CWA server and migrated the Collaboration service to a new server so that I could configure it to directly communicate directly with the Lync 2010 pool,
however I still needed to install OCS components on the new server in order to achieve that integration. Now I've run the final step of Merging the OCS 2007R2 Topology with the Lync 2010 topology in preparation for deleting the BackCompatSite, the old OCS
servers have gone, but the new Collaboration server has now appeared as a trusted application server within the BackCompatSite. I've done an LDIFDE export of the RTC Service container and have had a look through the contents. I can see that the new BES Collaboration
server is there and that it has an msRTCSIP-TrustedServerVersion value of 4, whereas all the Lync 2010 values are 5, which I'm guessing is what the Lync Topology is using to establish that the BackCompatSite needs to be populated with that Trusted Server entry.
So my question is this - What do I need to do in order to successfully remove the BackCompatSite entry and migrate my environment to Lync 2013 whilst retaining integration with BES and keeping the Enterprise IM service service running on Blackberry devices?
Here's some options that I've thought about - Using ADSIEdit to remove the Trusted Server Application for the new BES Collaboration server so I can merge the Topology and delete the BackCompatSite, although will this break the Enterprise IM service? Temporarily
changing the value of the msRTCSIP-TrustedServerVersion for the Collaboration server from 4 to 5, merging the Topology, deleting the BackCompatSite and then changing the msRTCSIP-TrustedServerVersion back to 4 afterwards? Over a weekend\out of hours, removing
the BES Collaboration server and service altogether, going through the Topology merge\BackCompatSite deletion and then reinstalling the Collaboration service?
Has anyone else gone through this process, or got any advice\experience to pass on before I start working through my list of options?

I've asked this question several times:
Does the 2007 R2 CWA server count as tri-coexistence?
I've asked that both in MCM rotations and directly of people on the PG and the answer is always something along the lines of "nope, it's a trusted app server and not a pool". When I've run into this issue in other deployments, we simply left the backcompatsite
in the deployment into production.
I've never found the above as a publically approved statement just something I've asked previously and been told is OK to do. This is one of those situations that will work but was most likely not tested.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

QuickEdit disabled after migration from SP 2010 to SP 2013

Hi,
I have a custom list. In SP 2010, I was able to use the Datasheet view to enter multiple data. I migrated the site to SP 2013, and the custom list, the Quick Edit is disabled.
I recreated a Datasheet view, but still it is not showing.
How to enable the Quick edit mode?
Thanks

Hi Venkatzeus,
You may try below steps.
Use or create a view that uses the Default view style for the list. To edit the selected view, follow these steps:
On the affected list, click the LIBRARY tab on the ribbon, and then click Modify View.
In the Style section of the Edit View page, click
Default, and then click OK.
OR
Go to the list settings> Advanced settings page
Scroll down and Under quick edit options just choose "Yes" and then click OK.
Let me know if it works for you.
Regards,
Amol

Trouble with publishing topology. Migration from Lync 2010 standard to 2013 standard.

Hi,
I have a problem with "Microsoft.Rtc.Applications.Testbot". When I publish the topology I receive an error, I've found many solutions to my problem. One of the best descriptions
I've found here: http://lyncme.co.uk/microsoft-lync-server-2013/unable-to-publish-topology-a-trusted-server-with-the-type-mcxinternal-and-fully-qualified-domain-name-fqdn/
I'm going to do the same method, but I do not understand whether I should remove both entries or only one. If I delete the record 2010, will the 2010 lync continue to work?

Hi Alan,
Lync is not that dependent on what is stored in Active Directory, and the topology builder should recreate any missing entries when it is rerun. I don’t think this operation is a high risk
for the deployment as a whole, but do be careful when using ADSI edit, it’s all at your own risk.
Here’s a similar case for your reference.
https://social.technet.microsoft.com/Forums/lync/en-US/01404c0c-ba63-4471-a5b2-8e110be451e3/lync-server-2013-topology-builder-errors-global-activation-?forum=lyncdeploy
Hope it can be helpful.
Best regards,
Eric

User migration from Lync 2010 to Lync 2013

We have Lync 2013 pool co-existence with Lync 2010 pool. Need to move users based on their AD Group membership. In a particular AD group, only few of the users are enabled for LYNC 2010, not all users. How to get the list of only Lync enabled users in AD
group and move them on to Lync 2013 by PowerShell script?
Thanks in advance for your help
Tek-Nerd

When I ran the below command
Get-ADGroupMember Mygroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
on my Lync 2013 server, got the below error message...
At line:1 char:46
+ Get-ADGroupMember MyGroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
+
~~~~~~~~~~~~
Unexpected token '-UserEnabled' in expression or statement.
At line:1 char:59
+ Get-ADGroupMember MyGroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
+
~~~
Unexpected token '-eq' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordExcep
    + FullyQualifiedErrorId : UnexpectedToken
Tek-Nerd

Lync 2010 to Lync 2013 migration - Dialin conferencing

While migrating from Lync 2010 to Lync 2013, i have stopped all services on the Lync 2010 servers to make sure all is okay and everything is working fine with Lync 2013.
Nevertheless, when someone on Lync 2013 schedule a meeting, and someone dial one of the PSTN Dialin conference number and enter the conference ID, this scenario is not working.
If i start the Lync 2010 front end services, then the previous scenario works.
So i did something else. I have scheduled a meeting and i change the meeting options to get a new conference ID. this makes the conference work over dial in pst number while Lync 2010 services are down.
This means:
- When someone (Lync 2013 user) schedule a meeting, the default conference ID that is generated, requires the existence of Lync 2010 services for a PSTN Dial in user to connect
-When someone (Lync 2013 user) schedule a meeting and change the meeting options to get a new conference ID, then the PSTN Dial in user can connect even if all Lync 2010 services are down.
Any clue?
ammarhasayen

i have found it. moving the conference directories from Lync 2010 to Lync 2013 solves the whole thing.
ammarhasayen

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

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)

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 to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
Many thanks.

Hi,
You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
Kindly mark this as answer if it fulfill your requirements. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

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 2003 will migrate to Exchange 2010 or Exchange 2013

Similar Messages

Maybe you are looking for