Exchange 2010 to Exchange 2013 Public Folder Problem

Dear Experts,
I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
1) Parent Domain in Site A (abc.com)
2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
Anyone help will be highly appreciated.
Thanks & Regards,
ZB

so you want users to access the PF in site B.
Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
run this for Exchanger 2013 DA
Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
Where Technology Meets Talent

Similar Messages

Exchange 2010 - 2013 Public Folder Migration target database gets much bigger than source database

Hi,
i have a question about the pf migration from Exchange 2010 to Exchange 2013. The source database ist about 370 GB. The migration process is still running. At the moment the target database is already 491GB big. Is that a normal behaviour during the migration
process.
Thanks

Hi,
After you have finished the public folder migration process, you can compare the item count of public folders to make sure all public folders have been moved to Exchange 2013.
You can check this by comparing the snapshots before and after the migration. You can refer to the "How do I know this worked?" section in the following article.
Migrate Public Folders to Exchange 2013 From Previous Versions
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 Public Folder Migration Not Listed

I started a public folder migration from my 2010 SP3 Exchange server to my new 2013 SP1 Exchange server. Somewhere during the process I failed. Not sure where but I am now at the point where if I try to create a new public folder on teh 2013 box i get a
warning like this.
An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch.
So I then run Get-PublicFoldermIgrationRequest to see what is still waiting... I get no migration listed in Exchange Management Shell.
I would like to find the place in AD or in the Server that thinks there is still an active request out there and remove it so I can start again with a clean slate. How do I do that?
Thanks!

Hi Zulea,
This is a known issue, I recommend you refer to the following article to resolve the issue:
http://support.microsoft.com/kb/3004062/en-us
Cause:
This problem occurs when the Exchange organization coexists with an earlier version of Exchange Server, and one or more public folder databases from the earlier version of Exchange still exist.
Resolution:
To resolve this issue, use one of the following methods.
Method 1: Create the mailbox by using the -HoldForMigration switch:
This option lets an administrator create a public folder mailbox in order to begin a migration from the existing public folders:
Open the Exchange Management Shell.
Run the following cmdlet to create the public folder mailbox:
New-Mailbox "Public Folder Mailbox" -PublicFolder -HoldForMigration
Method 2: Remove all public folder databases from earlier versions of Exchange Server
To remove existing public folder databases, see the following TechNet websites, as appropriate for the version of Exchange that an existing public folder resides on.
Exchange 2010:
http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
(http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx)
Exchange 2007:
http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx
(http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx)
Create the public folder mailbox by using either the Exchange Admin Center (EAC) or the Exchange Management Shell (EMS). To do this, see the following TechNet website:
http://technet.microsoft.com/en-us/library/jj552410(v=exchg.150).aspx
Best 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]
Niko Cheng
TechNet Community Support

Exchange 2013 Public Folder Accessability Issues

After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders. Issues range from a hung server requests to on-screen errors like this one:
“Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
Ideas?

Hi Niko,
Firstly, apologies for the delayed update...
We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation. While migrating from Exchange 2010
to Exchange 2013 we did follow the migration process.
Here is what our current settings from Get-OutlookAnywhere -Server %Server%
RunspaceId                         : e2e4f324…
ServerName
: %server%
SSLOffloading
: True
ExternalHostname
: <set>
InternalHostname                   : <set>
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods
: {Basic, Ntlm, Negotiate}
XropUrl
ExternalClientsRequireSsl
: True
InternalClientsRequireSsl
: True
MetabasePath
        : IIS://%server%/W3SVC/1/ROOT/Rpc
Path
: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags
ExtendedProtectionSPNList
AdminDisplayVersion
: Version 15.0 (Build 775.38)
Server                             : %server%
AdminDisplayName
ExchangeVersion
: 0.20 (15.0.0.0)
Name
: Rpc (Default Web Site)
DistinguishedName
: CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                    Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
Identity                           : %server%\Rpc (Default Web Site)
Guid
: 0bf08d0e…
ObjectCategory
: %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged
: 5/5/2014 3:08:31 PM
WhenCreated
: 2/20/2014 2:13:17 PM
WhenChangedUTC
: 5/5/2014 8:08:31 PM
WhenCreatedUTC
: 2/20/2014 8:13:17 PM
OrganizationId
OriginatingServer
: %server%
IsValid
: True
ObjectState
: Changed

Exchange 2013 - Public Folder Mailbox and Single Item Recovery

Hello,
I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
"Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder.
Check out this article
http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward. That said this will also increase the
DB size so consider all the options before implementing
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange 2013 Public Folder Missing in Outlook

Hello,
i have succesfully migrated from Exchange 2010 to Exchange 2013.
Everything was running after i migrated the public folders they disappeared on the Clients after starting Outlook 2013.
We are able to see the public Folders in OWA but not in Outlook.
Anybody know this Problem and can help?
regards
René

Hi,
Based on the description, everything was running after you migrated from Exchange 2010 to Exchange 2013. When you upgraded from Outlook 2010 to Outlook 2013, you couldn't see public folders in Outlook 2013. However, you could see public folders in Outlook
2010, but you couldn't expand it. OWA worked well.
If I misunderstood your concern, please feel free to let me know.
About "No we had migrated to Office 2013 before but tested it now with Outlook 2010.", was the Outlook 2010 client a remaining Outlook 2010 client?
Did the issue affect all users or some of them?
Could you please switch between online mode and cached mode to check the result?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 to Exchange 2013 work order

Hi ,
Can anyone help me on below points.
I have installed exchange 2013 , and able to view all mail box form existing server 2010.
And move successfully some mail box from 2010 to 2013.
My question are :
Pls let me know the sequence for below reimaging task……
Move all mailbox from 2010 to 2013
Change connectors (received /Send)
NAT the IP in Router (private to Public)
Change the IP address in service provide site. ( OWA for external users)
Need to create or change MX record in internal DNS as well ?
How to change MX record for external DNS.
Note: 2010 is exchange 2010 & 2013 is exchange 2013.
Regards,
Dilip T

Hi,
Based on my experience, here are the steps of migration from Exchange 2010 to Exchange 2013:
Exchange 2013 Deployment
Digital Certificates Configurations
Configure Exchange-related virtual directories
Configure offline address book (OAB)
Move Internet mail flow from Exchange 2010 to Exchange 2013
Move Client Access from Exchange 2010 to Exchange 2013
Move mailboxes from Exchange 2010 to Exchange 2013
Move public folder data from Exchange 2010 to Exchange 2013
Decommissioning Exchange 2010
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 to Exchange 2013 mail flow?

We are planning to migrate Exchange 2010 to Exchange 2013.
I understand that we need to upgrade the CAS to 2013 for Internet Facing.
What about mail flow. Currently, Internet mail flows to Exchange 2010 (single site). Can I keep it for sometime after introducing 2013 and do the cutover of HUB once all the mailboxes are moved to 2013? Or I have to get the mail flow to 2013 first.
Also, how does HUB 2010 transfer mail or receive mail from 2013? Does it get from the CAS proxy in 2013 or from HUB?
Thanks!!!

Yes, you can. But my preference is to move the mail routing early in the migration, usually even before moving mailboxes, because I believe it reduces the risk of a service interruption.
I believe it goes through the front-end transport on the CAS, since that is the TCP port 25 service.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

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 :-)

Exchange 2010 Migration to 2013 Coexistence url's

Hello,
What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information
I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while
only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.
So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my
existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Read the article below from Ross Smith. There can't be better article than this:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
If exchange 2010 and 2013 are on same site, then you need to:
1. Remove External URL from Exchange 2010 CAS servers, retain the Internal URL
2. Move the SSL certificates from Exchange 2010 to Exchange 2013
3. Point the external URL to Exchange 2013 instead of Exchange 2010
4. Of course, you would need to re-configure Autodiscover, Web Services URLs on Exchange 2013 CAS servers.
Once this is done, for any mailbox that is hosted on Exchange 2010, Exchange 2013 would proxy the connections and deliver the content.
- Sarvesh Goel - Enterprise Messaging Administrator

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Comparing-the-differences-between-anti-spam-agents-from-exchange-2010-to-exchange-2013

http://social.technet.microsoft.com/wiki/contents/articles/23582.comparing-the-differences-between-antispam-agents-from-exchange-2010-to-exchange-2013.aspx
Sathish

Hello,
This forum is for discussions and questions regarding profiles and Microsoft's recognition system on the MSDN and TechNet sites. It is not for products/technologies.
As it's off-topic here, I am moving the question to the
Where is the forum for... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Copy UM settings and prompts from Exchange 2010 to Exchange Online

When I migrated UM from Exchange 2007 to Exchange 2010, there is a script called "MigrateUMCustomPrompts.ps1"
that would copy over all the customized greeting files.
We are now migrating from Exchange 2010 to Exchange Online and will be using Exchange Online UM. Is there a similar script to copy over the files just like
the on-prem?

Sorry, I don't share code examples in most cases because they're generally one-off customer-specific scripts and I'm not in a position to answer lots of follow-up questions about them.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

Anyone come across this?
Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
outlook client knows the mailbox has moved as it connects to the new server
Not happening to every mailbox
thak=nks

Hi,
After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 to Exchange 2013 Public Folder Problem

Similar Messages

Maybe you are looking for