2003 to 2010 Exchange upgrade

We are in the process of 2003 to 2010 Exchange upgrade so that they coexist in the same environment what I don’t seem to be able to find is as follows.
Question can users still access the old 2003 OWA web page after the upgrade integration of 2010 so we don’t have to configure all mobile devices in one hit, or do all users now have to use the new 2010 OWA webpage? In a nutshell will both OWA servers work
side by side?

Hi WillWheatcroft,
Exchange 2010 is smart enough to proxy/redirect requests.
Please read this
https://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Regarding OWA
Add a new DNS entry e.g. legacy.domain.com (in both Internal DNS server and external DNS server) which is pointing to Exchange2003
Add that name in the certificate.
Configure redirection or silent redirection.
Please read this http://blogs.technet.com/b/sjimmie/archive/2010/07/09/owa-coexistence-with-legacy-versions.aspx
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.

Similar Messages

Migration Exchange 2003 to 2010 routing connector

Hello
At least we deside to migrate from 2003 to 2010 Exchange now i'm preparing and stuck around one question.
In our Exchange 2003 organization we have couple backend servers and one frontend on which OWA is installed.
OWA server placed to second routing group others backend server in first routing group.
Roitung group connected to each other by connector.
So the question - when i install CAS Exchange 2010 he asked me with which Exchange 2003 server i want to create connector - which server i should choose? Backend or Frontend which placed in different RG?

It doesn't really matter, it is a connector between your 2010 and 2003 servers.
You can choose the backend servers as it will reduce one hop in your case. Do make sure that you make the connector redundant by adding atleast two 2003 and 2010 servers as source and target servers in both connectors.
There will be two connectors - one from 2003 to 2010 and another from 2010 to 2003.

Upgrading Exchange Server 2003 to 2010 to 2013 is worth???

Hello there, I am planning to upgrade about 30 users from exchange server 2003 to 2010 and finally to 2013. Is it worth to upgrade in this way because this steps are hard and very time consuming. What if, if I just copy all the user mailboxes directly to
exchange server 2013 and configure 2013 as a new exchange server and decommission old exchange server 2003?
How to copy user mailboxes to fresh exchange server 2013?
Please help me out.
Thankx

Yes, Export the PST from User Mailbox and Import it into Exchange 2013 Mailbox. But the problem is, you can't install Exchange 2013 in your current Exchange 2003 environment.
Only option is to install Exchange 2010 first and migrate all the users to Exchange 2010. Also Replicate the Public Folders too(If you are using)
Decommission Exchange 2003 entirely. Install Exchange 2013 SP1 and Migrate the User to Exchange 2013.
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.

Exchange 2003 to 2010 migration mailflow issue

Hello,
I have a server 2003 w/ exchange 2003 that we are upgrading to 2010 to support Outlook 2013.
So we installed a windows 2008 server and exchange 2010. We followed a guide to help with the different steps and didn't have problem or error until now.
So what we have right now, is exchange 2003 with still ALL mailboxes.
Replications of folders is done.
Policies are updated.
The firewall is forwarding port 25 to the new exchange 2010 server:
Emails are coming in fine.
Internal emails are also perfectly fine (from internal user to internal users).
the only thing that is giving us trouble is the emails coming out. None of them are going out and they are getting "stuck" in the "routing group connector" on the 2003 machine.
The 2010 exchange has a simple send connector set SMTP/* with this server as source. The 2003 exchange only had the exch2003-exch2010 connector.
Because emails were kind of accumulating (80+) I decided to take the send connector on the 2010 exchange out. and added back a send connector on the 2003 exchange. This kind of "fixed" it as now all emails are going just fine. It also fixed
the queue as part of it got liberated when I added the 2003 send connector.
I still have 25 emails stuck in this "routing group connector" that I'd like to take care of.
We are obviously not done with the migration and this coexistence phase as actual mailboxes still need to be moved.
So I'd like to take care of this queue in the routing group connector as well as continue the process of being able to receive and send from the 2010 machine only. then I would continue the migration process.
FYI, the 2003-2010 connector was created using power shell on the 2010 machine. I am not using any smarthost.
and the error message (in the queue) I get is: "unable to bind to the destination server in DNS"
FYI, my 2003 server is called "SERVER1" and the 2010 server is "SERVER2", they're on the same local domain company.local.
FYI (not sure if that's relevant), the server1 exchange has a different certificate (different domain name) than the new server (server2) as our web host finally allowed us to use subdomains. not trying to confuse anyone but I am really stuck there and maybe
this is related: certificate for the exchange 2003 machine: www.company-mail.com (only 1) and certificates for the exchange 2010 are: mail.company.com / autodiscover.company.com (and a legacy.company.com we may not need since the actual coexistence phase will/should
be short).
any idea what's wrong here?

I added back the send connector on the 2010 exchange. everything still works fine since I still have the send connector on the 2003. However...
I connected through telnet to server2 (the exchange 2010) and was able to mail internally. however I couldn't send mail externally, it gives me a "cannot relay" error when I enter my rcpt to:... command.
I am guessing that this may be the reason why the queue is not emptying itself through that send connector.
Anything else I could try to test my "send connector" on the 2010 exchange?

Exchange 2003 to 2010 error

Hello I have been working through a upgrade of exchange 2003. I am at a point where when I try to send from exchange 2003 to 2010 I get the following error
You do not have permission to send to this recipient. For assistance, contact your system administrator.<My2003server.COM #5.7.1 smtp;550
5.7.1 Unable to relay for [email protected]
I have set the relay settings on my 2003 smtp server to allow all as a test with no luck any ideas?

Anyone? I have hit a wall on this. Any help would be greatly appreciated.

Running Unity with both Exchange 2003 and 2010?

My company is planning to upgrade from Exchange 2003 to 2010. We are
currently using Unity 7.0. We'd like to run the two in parrallel for a bit and take our time switching users over.
Now I've read that Unity can support Exchange 2010, but I haven't found anything about running Unity using both Exchange 2003 and 2010 in parrallel.
Is this something Unity can handle?

We're doing something similar, but we have an in-place Unity 7 and Exchange 2003 environment; we are putting some users from an org we support on an Exchange 2010 server, but do not want that to be the partner server (yet). The instructions seem to point you to making 2010 the partner; I'm wondering why Step 13 (of your link) we are uninstalling the Exchange Server 2003 System Management Tools, if it’s a mixed environment and 2003 will still be the partner server. I also saw somewhere that you don’t have to move the unitymsgstoresvc account to Exchange 2010 if you are in a mixed environment. Is that true? Thank you.

Unity 8.0 and Migrating Exchange 2003 to 2010

In the coming months I hope to be upgrading from Exchange 2003 (sp2) to Exchange 2010 (sp3) running on Windows Server 2012. I currently have Unity 8.0(3.1) running on Server 2003. We hope to be upgrading to Exchange 2013 at the end of the year if that is supported.
Before I contact my Cisco partner about this upgrade I would like to know what to expect. Any advice and suggestions would be appreciated.
Thanks!
Nick

The integration is completely different than with legacy Unity. High-level: Unity leverages MAPI integration and is completely dependent upon AD and Exchange to function properly. Hence, the schema extensions, Permissions Wizard (and associated permissions), and etc. Unity Connection leverages web-based APIs for integration. Specifically it uses WebDav for Exch 2003 and EWS for Exchange 2007/2010. It is a dual message store synchronization architecture, which means that 1) it can function independently without AD and/or Exchange integration and 2) no schema extensions and 3) less complicated permissions requirements. With Unity Connection, the users have a mailbox on the server and then a copy of that message is synchronized into the user's corporate Exchange mailbox. You get MWI synchronization between phone and email and etc (hence, you get Unified Messaging). Another nice thing is that you can handle requirements for voicemail only scenarios locally on Unity Connection without having to create dummy or "resource" AD/Exchange accounts in the corporate systems. You can read up more on this integration here and hit me back up if you have questions. I'll be glad to help if I can.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg010.html
As for the fax part, OK - that's a problem in your scenario. Personally, I've never been a big fan of using Unity for that (and don't) but then again, I don't really like "fax" anyway. Personal opinions aside, I'll go with relay of facts. Unity Connection supports integration with 3rd-party fax systems. You can take a look at that here:
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg080.pdf
In terms of Unity though, the reality is that it's days are (and have been) numbered. See below:
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps6509/end_of_life_notice_c51-681593.html
Hailey
Please rate helpful posts!

Migrating exchange 2003 to 2010 while everyone is running SMTP, POP3 and IMAP on the old exchange 2003

Hi all
We have a legacy Exchange 2003 running with more than 800 users and with a very mixed configuration for client access. Most of users are running POP3/SMTP on the Exchange, some are running IMAP/SMTP and some are running MAPI access.
Please note that THERE IS NO WAY that we move all users to MAPI access before the installation (due to deadlines).
We plan to install a new Exchange 2010, starting with a CAS/HUB server. We do not need to migrate users automatically, and we can proceed later to move them individually to the new Exchange 2010 infrastructure in a non-transparent way.
More importantly, we need to maintain that everyone receives their e-mail and all communication through the exchange 2003 continues uninterrupted.
My question is can we install the new CAS/HUB server, while maintaining the old exchange server running with it's old name and create new names for the CAS/HUB server. In such a configuration, will all the Exchange 2003 services continue to run as usual
(POP3/IMAP/SMTP/MAPI)?

In addition, you may also spend some times at below mentioned helpful resources to check the prerequisites before moving all mailboxes from exchange 2003 to 2010 :
http://exchangeserverpro.com/wp-content/uploads/2011/02/Exchange-Server-2003-to-2010-Migration-Guide-V1.3-Planning-Chapter.pdf
http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
Moreover, to avoid any interruption during the completion of migration process, you can also take a look at this application(http://www.exchangemigrationtool.com/) that could be a good alternate approach
for you.

Exchange 2003 to 2010 migration web-mail question?

We are in the process of migrating our Exchange 2003 server onto Exchange 2010 and I have produced a plan to achieve this, but would appreciate some help regarding a couple of steps? In particular how this will affect external users. Information:At present we are running windows 2003 Domain controllers which I will be updating to the levels required for Exchange 2010 to exist.Our Email is provided by an external company which sends the mail to our external IP address on the firewall, which in turn is forwarded to the internal IP of the current exchange server. We have outlook web access in place via https://webmail.Domainname.com/exchange address. We also have mobile device users that are configured to receive mail using the webmail.domainname address – without the /exchange setting at the end.My question is: How, during the install,...
This topic first appeared in the Spiceworks Community

Hello,
After you install exchange 2010 server, you can deploy DAG.
Here are some articles for your reference.
Upgrade Exchange 2003 to Exchange 2010
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
Understanding Database Availability Groups
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx
Exchange 2010 DAG Creation and Configuration Part 1
https://www.simple-talk.com/sysadmin/exchange/exchange-2010-dag-creation-and-configuration-part-1/
Exchange 2010 DAG Creation and Configuration, Part 2
https://www.simple-talk.com/sysadmin/exchange/exchange-2010-dag-creation-and-configuration,-part-2/
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2003 to 2010

I want to migrate from a Windows 2003 server with Exchange 2003 to a Windows 2012 Server with Exchange 2010. My question is when installing Exchange 2010 on the Windows 2012 server does the Exchange server need to be part of the existing Exchange
environment or installed as a stand alone Exchange server?

Hi,
You can install Exchange 2010 in an existing Exchange 2003 organization.
Here is an article about how to install Exchange 2010 in an existing Exchange 2003 organization for your reference.
Install Exchange 2010 in an Existing Exchange 2003 Organization
More information:
Upgrade Exchange 2003 to Exchange 2010
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Error moving mailbox from 2003 Exchange to 2010 Exchange

Hi everyone
I am having some trouble moving a mailbox from our Exchange 2003 server and over to our Exchange 2010 server. at this point i have moved 300 users, but this one here is causing some grief. It stops at 10% Any ideas????
23/06/2012 21:35:28 [VMPRIEXCH] 'ad.DNSArrow.co.uk/Admin Accounts/RJ Admin' created move request.
23/06/2012 21:35:28 [VMPRIEXCH] 'ad.DNSArrow.co.uk/Admin Accounts/RJ Admin' allowed a large amount of data loss when moving the mailbox (250 bad items).
23/06/2012 21:35:30 [VMPRIEXCH] The Microsoft Exchange Mailbox Replication service 'VMPRIEXCH.ad.DNSArrow.co.uk' (14.2.247.1 caps:07) is examining the request.
23/06/2012 21:35:30 [VMPRIEXCH] Connected to target mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)', database 'SHAREDMBDB', Mailbox server 'VMPRIEXCH.ad.DNSArrow.co.uk' Version 14.2 (Build 247.0).
23/06/2012 21:35:30 [VMPRIEXCH] Connected to source mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)', database 'EX01\SG2\Mailbox Store SG2 C', Mailbox server 'ex01.ad.DNSArrow.co.uk' Version 6.0 (Build 7654.0).
23/06/2012 21:35:41 [VMPRIEXCH] Request processing started.
23/06/2012 21:35:41 [VMPRIEXCH] Mailbox signature will not be preserved for mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)'. Outlook clients will need to restart to access the moved mailbox.
23/06/2012 21:35:41 [VMPRIEXCH] Source mailbox information before the move:
Regular Items: 189917, 5.272 GB (5,660,371,162 bytes)
Regular Deleted Items: 2491, 135 MB (141,547,842 bytes)
FAI Items: 2490, 0 B (0 bytes)
FAI Deleted Items: 0, 972 B (972 bytes)
23/06/2012 21:35:49 [VMPRIEXCH] Fatal error MapiExceptionNotFound has occurred.
Error details: MapiExceptionNotFound: Unable to GetSearchCriteria. (hr=0x8004010f, ec=-2147221233)
Diagnostic context:
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=48]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=98][latency=0]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropGetSearchCriteria [49]
Lid: 31418 --- ROP Parse Done ---
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=53]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=15]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropLtidFromId [67]
Lid: 17082 ROP Error: 0x8004010F
Lid: 17505
Lid: 21921 StoreEc: 0x8004010F
Lid: 31418 --- ROP Parse Done ---
Lid: 22753
Lid: 21817 ROP Failure: 0x8004010F
Lid: 30894
Lid: 24750 StoreEc: 0x8004010F
Lid: 29358
Lid: 27950 StoreEc: 0x8004010F
Lid: 29310
Lid: 23998 StoreEc: 0x8004010F
Lid: 29329
Lid: 19729 StoreEc: 0x8004010F
Lid: 23185
Lid: 25233 StoreEc: 0x8004010F
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.MapiContainer.GetSearchCriteria(Restriction& restriction, Byte[][]& entryIds, SearchState& state)
at Microsoft.Exchange.MailboxReplicationService.LocalFolder.Microsoft.Exchange.MailboxReplicationService.IFolder.GetSearchCriteria(RestrictionData& restriction, Byte[][]& entryIds, SearchState& state)
at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.<>c__DisplayClass19.<Microsoft.Exchange.MailboxReplicationService.IFolder.GetSearchCriteria>b__18()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.Microsoft.Exchange.MailboxReplicationService.IFolder.GetSearchCriteria(RestrictionData& restriction, Byte[][]& entryIds, SearchState& state)
at Microsoft.Exchange.MailboxReplicationService.FolderRecWrapper.EnsureDataLoaded(IFolder folder, FolderRecDataFlags dataToLoad, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass4`1.<LoadFolders>b__0()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.LoadFolders[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.GetFolderMap[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.GetSourceFolderMap(GetFolderMapFlags flags, FolderRecDataFlags dataToLoad, GenericCallDelegate abortDelegate)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<CreateFolderHierarchy>b__2d(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CreateFolderHierarchy(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IFolder.GetSearchCriteria
OperationSide: Source
Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)
Search folder: 'MS-OLK-BGPooledSearchFolder28E6C24EFE39F845A1C7309FF139D54F', entryId [len=46, data=00000000ED492DE46CCB2941A6EFC600B0DC8ABD010062EB1CE91779304984F59E79C254E5430000033BC7BF0000], parentId [len=46, data=00000000ED492DE46CCB2941A6EFC600B0DC8ABD010062EB1CE91779304984F59E79C254E54300000015852B0000]
23/06/2012 21:35:50 [VMPRIEXCH] Removing target mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)' due to an offline move failure.
23/06/2012 21:35:50 [VMPRIEXCH] Relinquishing job.
Regards
Ronnie
Ronnie Jorgensen | MCTS Windows Server 2008

Hi ,
Maybe we can configure BadItemLimit for it .
New-MoveRequest:
http://technet.microsoft.com/en-us/library/dd351123.aspx
More information for your reference.
Can not move Exchange 2003 mailboxes to Exchange 2010:<//span>
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/89902f00-4b84-4f10-b909-121a81241c85/
Wendy Liu
TechNet Community Support
Hi Wendy
BadItemLimit is already set to 250 mails and with accept data loss
New-MoveRequest -Identity 'vquotes' -TargetDatabase "DB06" -BadItemLimit 250 -AcceptLargeDataLoss
So that is not the problem :)
Ronnie Jorgensen | MCTS Windows Server 2008

Exchange 2003 to 2010 Migration OAB Generation Issue

Hi
I am in the process of migrating from 2003 to 2010. All mailboxes are moved across and email in and out are moving through the 2010. However I cannot move the oab generation server as when i go to change the generating server my New 2010 server is not listed
only the two old 2003 servers. This is a child domain in a large organization and is one of a large number of exchange servers forestwide. I have created a new oab and asigned to the mailboxes on the new 2010 server. The old 2003 server is off for over a week
and there are no issues.
I now need to remove both 2003 servers, what issues will not being able to move the generation server cause (If any if i am using a new oab). Also I am following the remove last exchange server line as this is the last 2003 server in this child domain are
there any issues with this in this scenario?

Hi,
According to your description, I understand that all mailboxes have been moved to Exchange 2010 and a new OAB is created for all users in your environment.
Please make sure the new created OAB is generated by Exchange 2010 and Enabled Web-based distribution. If there are any Outlook 2003 users in your environment, the public folder distribution should also be enabled. Then we can set the new one as default.
If so, all users in Exchange 2010 would use the new created OAB by default.
If you want to double check the OAB configuration, we can run the following command to check it:
Get-OfflineAddressBook | FL
Additionally, if your migration is complete and successful, we can follow the article below to remove the last legacy Exchange server from your Exchange 2010 organization:
http://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
Best Regards,
Winnie Liang
TechNet Community Support

Shared mailbox access from exchange 2003 to 2010 users

We'd successfully migrated from exchange 2003 to 2010. still some of the users are yet to be migrate.
The issue is only in MAC (Apple) Migrated users was unable to access the shared folder residing in 2003 environment.
but the migrated 2010 users are able to access the shared folders in the windows environment.
Any one can assist or suggest this issue.
Awaiting for ur reply.
Regards
kart26

Hi Kart26,
Please install certificate in your MAC App Client.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Public folders are not in sync after settting up Replicas between Exchange 2003 and 2010

I have setup Public Folder replicas between the 2 Exchange servers and I can see all the top and sub level folders.
For those mailboxes that were migrated over to Exchange 2010, I have noticied a lower number of item contents in these fodders when views from an Outlook client whose mailbox had been migrated over to Exchange 2010.
On Exchange 2003 System Manager, if I properties one of the Public Folders, under the Replicataion tab, I can see the old and new server there. On the Exchange server 2003 box, I can see the last update reviced was a few weeks ago.
I did see an option to synchronize content but I am not sure which server to run this one from. The Exchange 2003 or 2010 server.
There is also a Resend Changes... option. Should I use this instead?
Can anyone advise?

Hi,
The "Resend changes" and "Synchronize content" options in Exchange 2003 ESM are used to initiate hierarchy and content replication.
To update public folder hierarchy and content from Exchange 2010 side, you can use the following commands.
Update-PublicFolderHierarchy
Update-PublicFolder
Please run the Get-publicfolderstatistics cmdlet to get public folder details such as item count, this information will help you compare content replicated between the source and destination servers.
Besides, here is a blog about public folder replication troubleshooting for your reference.
http://blogs.technet.com/b/exchange/archive/2006/01/17/417611.aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

2003 to 2010 Exchange upgrade

Similar Messages

Maybe you are looking for