SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

SharePoint 2013 has introduced Friendly URLs and is implemented using Managed Meta Data Service. The Content Deployment will complain Metadata Navigation is not supported Deactivate Metadata Navigation

We need to have the architecture like Source Farm where content authors create content. And using Content Deployment or Quick deploy to publish the content in the target farm with the Friendly URL's

Any way to achieve this?

share|improve this question
I'm pretty sure it's because the terms won't be the same accross farms (guid wise) unless you first restore a backup from source to production environment (but what about future changes...). Setting up a cross farms Shared Services might help I think but not sure the lovely content deployment jobs will see this architecture. – Francois Verbeeck Mar 12 '13 at 12:17

What about XPS? Cross Site Publishing now is the preferred way to publish content in these kinds of scenarios.

Everything in Waldek blog is gold for this topic:

share|improve this answer

This is how SharePoint 2013 works. Nothing you can do about it.

What you can do is to have your catalogs/content in a remote farm and leverage that through federated search.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.