Question regarding Exchange ActiveSync migration from Exchange 2003

Hello,
I am a bit confused about info about requirements when migrating Exchange ActiveSync (EAS) from 2003 to 2010. Now this question is related to EAS only, forget about other services, such as OWA or Outlook Anywhere, for a while.
Basically, all migration guides state that you have to configure and setup a legacy url for legacy services for co-existence. Based on that, I have had an understanding that Exchange 2010 CAS cannot proxy EAS users that are still on Exchange 2003, but issues
a redirect command to EAS client.
However, this article shows information that, based on my understanding, states that Exchange 2010 CAS DOES proxy EAS clients that are still on 2003: http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx
For migration from 2007 EAS to 2010 EAS the article shows redirecting, but not with 2003.
So my question is: While talking about only EAS, do I need to configure legacy external url/namespace/name resolution or not?
Thanks for answering!

Hello,
I agree with Rajith's suggestion.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Cara Chen
TechNet Community Support

Similar Messages

SPAM rules on Inbox after migration from Exchange 2003 - GFI Mail Essentials

Hello,
Few times ago, we had an Exchange 2003 server with mailboxes which were configured with "rulemgmt.exe" tool (from Microsoft ?) to manage users mailboxes and SPAM redirection in these mailboxes.
GFI MailEssentials (antispam) was installed on a mail relay and once a SPAM was detected, it was redirected in Inbox/SPAM folder on user mailbox thanks to the rule defined by "rulemgmt.exe".
Recently, we did a migration from Exchange 2003 to 2010. Unfortunately, "rulemgmt.exe" doesn't work anymore on Exchange 2010 and it's replaced by a "Transport Rule" which works fine but only to redirect SPAMs in Junk e-mail folder. However,
if I don't set up this transport rule, SPAM redirection still works from mailboxes which were created on Exchange 2003 and e-mails go to Inbox/SPAM as before... For new mailboxes on Exchange 2010, it doesn't work which is normal.
My question is: for old mailboxes from Exchange 2003, where are the SPAM redirection (Inbox/SPAM) information stored? I don't understand how SPAM can be redirected if the information is not stored in Exchange...
The aim is to use Junk E-mail folder with the Transport Rule at the end everywhere and to clean old rules used for Inbox/SPAM.
I contact GFI support but they couldn't help me.
Any idea?
Regards,
DeltaSM

Those old mailboxes probably have old rules still set. You can use the Outlook.exe /cleanrules switch to purge those old rules. This would require that you create an outlook profile for each of those impacted mailboxes.
You can also look at using MFCMapi -
http://support.microsoft.com/kb/2860406/en-us
When that is done, you might want to perform a Clean-MailboxDatabase and then look at the mailbox rules (get-inboxrule). If that does not work for you, could be something else within the mailbox and as such, I would recommend working with MS to get
more info.
DaDougInc

ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
a great guide which has been a big help,
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.
Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
the user exists on Mailbox server EX02.DOMAIN.COM
I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
Thanks.

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Migrate from Server 2003 (no Exchange, single server) to SBS 2011

Are there any Technets or other Microsoft documentation on migrating from Server 2003 (no Exchange, single server) to SBS 2011? I understand it is possible, but I would like confirmation and some documentation before purchasing the appropriate hardware
and licenses.
Thanks,
Doug
Doug Orr

Hi Doug,
In general, the migration is the similar with migrating process from SBS 2003. In addition, also have main
difference.
“The main difference is that you don’t have to remove the source and that you have to follow the migration
instructions as the SBS migration wizard will not launch.”
You can get above description from following similar thread. Please refer to.
Migrate from Windows Server Standard 2003 (not SBS) to SBS 2011
http://social.technet.microsoft.com/Forums/en-US/68790e41-b833-4e81-8200-63852ab9e196/migrate-from-windows-server-standard-2003-not-sbs-to-sbs-2011?forum=smallbusinessserver
Meanwhile, please refer to the following article. It may be helpful.
Step By Step Guide To Migrating To SBS 2011
http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
However, as Robert suggests, would you please confirm specific version of SBS? It may help us to understand
clearly and provide correct information.
Hope this helps.
Best regards,
Justin Gu

Exchange 2010 Log files keep filling up following migration from Exchange 2003

I am migrating from Exchange server 2003 to 2010.
Having only moved one mailbox and set-up Public Folder replication, I noticed that the 20GB Drive allocated for the logs are filling up the entire drive, even before I have time to run my scheduled backup.
As a temporary measure, I have enable circular logging as a workaround.
Q/ Whilst this is not ideal, shall I leave it like this until the Public Folders are fully replicated and all mailboxes moved over?
Q/ What risk am I exposing myself to as a result of using Circular logging (I am running full backups every night).
Q/ Could there be another cause as to why the log files would grow so quick in such a short amount of time?

Hello,
Remember that logs are truncated after successful backups so if you have a lot of data replicated between backups, a lot of logs will be stored on disk.
"Q/ Whilst this is not ideal, shall I leave it like this until the Public Folders are fully replicated and all mailboxes moved over?"
The best option is to run backups to truncate logs. Circular Logging is useful in test and high available deployments as it can cause data loss (loss of data created between backups).
"Q/ What risk am I exposing myself to as a result of using Circular logging (I am running full backups every night)."
The same as mentioned above.
"Q/ Could there be another cause as to why the log files would grow so quick in such a short amount of time?"
Enormous logs generation can be caused by bugs in Exchange and connecting devices, i.e. iPhones can cause quick logs creation in some configurations. If you have latest Exchange 2010 build, it shouldn't be problem.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Migration from Exchange 2003

Hi,
We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
Can Office 2011 connect to Mac mail services? If so, what protocols?
Many thanks,
Ciaran.

We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
What features of Exchange are you using? Push notifications? Calendaring. Sharepoint? Figure out what you want and what you need (and which are two separate lists) and then map that over to what Mac OS X Server, or to what a Mac box with the Kerio Connect package loaded, might provide you.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
That's rather open-ended. It's possible, but there's no single definition of small business mail requirements. Some small businesses can and have, and some might find themselves missing critical features.
Can Office 2011 connect to Mac mail services? If so, what protocols?
iWork does well enough to read and write Office files locally, so I don't have experience with Microsoft Office. The Windows mail clients can certainly access Unix mail servers. As for what connectivity is present within Office, I'm way too rusty with Windows to comment. What used to be the Outlook Express client worked just fine with Unix mail servers. The full-on Office Outlook client was pretty flaky with stuff other than Exchange, but that was some years ago.
Biggest issues with SBS migrations tend to be with shared Address Book, with shared Calendars and with Sharepoint services; if you're heavy users of those features, you might find the Mac OS X Server implementations lacking. Kerio can potentially help here.
Look around the forums for some other folks. This particular SBS migration has been fairly common fodder for discussions.

Calendar Free/Busy permissions being ignored for users migrated from Exchange 2003, fine for new users created on Exchange 2010

I have uncovered a situation where it seems the free/busy permissions are being ignored for users that were migrated from Exchange 2003 to Exchange 2010.
I have the default permissions set to only show Free/Busy Time, not Details. However if I look at the calendar for a users who was migrated from the old Exchange 2003 server, I can see details. If I look
at a newer user who was added directly to the Exchange 2010 server, I (correctly) only see the times and "Free" or "Busy", not the specific details.
I verified the permissions on the migrated mailboxes many different ways (Exfolders, cmdlets, etc) and all signs point to only allow showing Free/Busy Times, but alas, I can still see the Details as well.
My users are using Outlook 2010.

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Cross Forest Migration from Exchange 2007 to Exchange 2013

Hi
Could anybody advice me the steps also the pros and cons for below mentioned environment if we are going for the cross forest migration.
Source
Domain - test.local
Active Directory - Windows 2003
Exchange Server - 2007
Target
Domain - test.net
Active Directory - Windows 2012
Exchange Server - 2013
Also if it is possible ,
How could I remove the source environment including the exchange servers. after the migration ?
Regards
Muralee

Hi Oliver ,
Please suggest us.
In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
Source : Exchange 2007 with sp3 ru 10
Target : Exchange 2013 with cu2 ( new environment yet to be created).
Trust : Forest trust in place (two way )
Domain and forest functional level : 2003 in both target and source
Migration Steps :
Step1 :
We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
in the target forest.
Step2:
Then we are going to use ADMT to migrate users SID'S and password .
Step3:
Then we are going to move the mailboxes with New-moverequest
Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
.Is anything needs to be changed please intimate me .
Thanks
S.Nithyanandham
Hey there,
Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Migrating from Exchange 2007 to exchange 2013 ( special case )

Hello ,
what is the BEST scenario ( fastest , most efficient , most secure in terms of data loss ) , to migrate from exchange 2007 ( one server , all exchange roles installed on this server , 1200 mailbox ) , to exchange 2013 ?
knowing my environment needs to be connected to their mailboxes , 24/7 !
it's very frustrating .
and i have no clue even if this is the right place to post about this , if not please refer me as to where to post .
Also , All my domain controllers are 2008 .

It's fine to post your question here, and you are fine with Server 2008 Domain Controllers - that is a supported scenario.
If you haven't performed such an upgrade and you need to have 24/7 mailbox availability, I would seriously recommend you to duplicate the production environment on a test network and run through the upgrade at least once.
Most people neglect the Outlook clients requirements - they need to be updated and include several specific updates, which allow the automatic reconfiguration of internal clients. If you are preparing for this upgrade, you should be aware that all internal
Outlook clients switch to Outlook Anywhere. Clients that miss these updates will get connectivity problems.
Another common problem is the configuration of the Exchange URL - I mean the Exchange 2013 URL and the modified Exchange 2007 URL that will allow the co-existence. In your case, you definitely need to plan for co-existence - that includes requesting and
installing a new Exchange UCC (Multiple Domain Certificate) on both Exchange servers, configuring Split DNS (or preferably PinPoint DNS zones), and correct timing when replacing the existing Certificate on the Exchange 2007 server. Failure to configure the
correct URL (and it's quite easy to miss one, so triple check them) will get you in trouble.
Once you get through the switchover (switching the mail flow and Client Access through the Exchange 2013 server), move just a couple of test mailboxes and check the result.
Finally, if you are moving the Public Folders, make sure that the lock is really applied before you complete the process. Most people proceed right away and that get's the process stuck. If you can afford it (the mailboxes are already on the Exchange 2013
server at that point), just restart the Exchange 2007 server (after locking the Public Folders) and then complete the Public Folder migration.
Good Luck with the project!
Step by Step Screencasts and Video Tutorials

Can only access emails through OWA after migration from exchange 2007 to 2013

can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..

Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

How to migrate from exchange 2007 to 2013 step by step tutorials please

Hi
I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
We have 800 mailbox in total
Our domain controllers are
Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
I currently only have 1 exchange server 2007, with all the roles on the one server. I would like to keep that same as
well with exchange 2013.
Thanks

Exchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
migration task in more secure way.

Migrating from Exchange 2007 to Exchange 2013 Public Folders coexistence

Hi all, I'm migrating from Exchange 2007 SP3 to Exchange 2013 SP1.
I have an Exchange 2007 server (Client Access, Hub Transport and Mailbox Server) in Site A, mailboxes and Publics Folders
In another Site in Site B, I have already installed (Client Access and Mailbox Server) Exchange 2013 server.
I am migrating test users, the fact is that users who migrated to Exchange Server 2013 Public folders do not see.
How I can make the migrated users from viewing the Exchange 2007 Public Folders duration coexistence?
Is there a "how to" to migrate Public Folders from Exchange 2007 to Exchange 2013?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Is it possible to access the Public Folders in Exchange 2013 during a migration from Exchange 2007 to verify the files are there?

This is a migration from Exchange 2007 to Exchange 2013. We're in the middle of migrating the Public Folders. Is it possible to configure a database to point to the Exchange 2013 public folders so I can verify the data before the final cut?
If so what are the steps to do that? Thanks in advance.

To my knowledge no. It's an all or nothing thing with public folders.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Migration from Exchange 2007 SP3 to Exchange 2010

Hello,
We are planning a single server migration from Exchange 2007 SP3 to Exchange 2010. I'll be building the 2010 server on a 2008 R2 box. My question is, can I make the jump directly to Exchange 2010 SP3, or do I need to install exchange 2010 SP1 first
- migrate from 2007 SP3, and then install SP3 for exchange 2010 later?
Thanks,
Eric

@ Hasan
Dimdik - TAT,
That's not correct at all, you can migrate exchange server 2007 SP3 and RollUp Update 10 minimum to Exchange Server 2013 with minimum CU1.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
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.

Migrating from Exchange to Oracle email

Hi,
has anyone done email migration from Exchange 5.5 to Oracle e-mail (OCS 9.0.4.1) ?
Any inputs ?
Thanks,
Dipak

This forum is for discussions about database migration and the Oracle Migration Workbench. It would be appropriate to post your question to this forum here:
Migration
Donal

Question regarding Exchange ActiveSync migration from Exchange 2003

Similar Messages

Maybe you are looking for