theme-sticky-logo-alt
theme-logo-alt

Step By Step Guide to configure the Managed Metadata Service Application for SharePoint 2013

February 15, 2013
by Vlad Catrinescu
13 Comments

As you have probably seen lately, I am releasing a lot of step by step guides to configure Service Applications in SharePoint 2013!  The final objective is to have all Step By Step guides for every Service Application in SharePoint 2013 and have a fully featured farm!

This guide is a step by step guide with Screenshots to create and configure a Managed Metadata Service Application in SharePoint 2013 as well as a Content Type Hub. It’s a really easy tutorial that should take maximum 30 minutes to complete!

I embedded the PDF with Scribd, however if you want to download it, there will be a link at the bottom of the post

[scribd id=117461472 key=key-9xwtjvet6t692h2cf6r mode=scroll]

Past Guides:

SharePoint 2013 Service Accounts Best Practices! 
Step By Step Guide to configure the “Replicating directory changes” for SharePoint 2010 and 2013

Future Guides

Creating a User Profile Application & MySites
Configuring SharePoint Search Topology
Configure an environment for apps for  SharePoint 2013
Configure Machine Translation Services  SharePoint 2013

If you have any ideas for other Guides or need help with something, leave it in the comments! It might help more people than you think.

Leave  a comment and don’t forget to like us on Facebook here and to follow me on Google+ here and on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check the SharePoint Community Partners list for other great SharePoint Sites, and vote for my blog if you like my content!

SharePoint Server
Previous Post
Troubleshooting setting up an environment for apps for SharePoint 2013
Next Post
Did you Know the SharePoint Server 2013 February Cumulative Update was out?

13 Comments

  • February 28, 2013 at 6:55 pm
    Sean O’Leary

    This is a helpful guide. Screenshots are always beneficial when explaining how to do something within SharePoint, especially for those that are new to the platform.

    Reply
  • April 15, 2013 at 5:02 am
    Suresh Pydi

    Very helpful. Here are few more more posts explaining managed meta data configuration
    http://sureshpydi.blogspot.in/2013/04/share-point-2013-managed-meta-data.html
    http://sureshpydi.blogspot.in/2013/04/sharepoint-2013-configure-managed.html
    http://sureshpydi.blogspot.in/2013/04/sharepoint-2013-create-term-set-terms.html

    Reply
  • July 9, 2014 at 3:26 am
    Ashish

    Hello Vlad,

    It was really a very nice post. But i am not able to find the link in your post to download the same.
    Kindly provide me the link to download the pdf doc as it is paid in scribd.

    Thanks

    Reply
  • October 29, 2014 at 11:54 am
    Chad C

    Vlad,
    Very handy, thanks for putting these guides together. One question, I’m guessing you used New-SPServiceApplicationPool to create the service app pool, were you able to have it show up with its name in IIS Manager, rather than with a GUID?
    Thx,
    Chad

    Reply
    • December 29, 2014 at 10:56 am
      Vlad Catrinescu

      Service application pools appear in IIS as long random strings of characters. The name you give it in SharePoint is not reflected in IIS Manager.

      An IIS Application Pool can have but one unique identifier, it’s Name, for which uniqueness is enforced. It works perfectly. However SharePoint has decided to use GUIDs for this Name. Within Central Administration the Application Pools are displayed using a SharePoint only property – Name, which is actually a Display Name (e.g. SharePoint Web Services Default).

      Moreover, the GUIDs used are unique. These aren’t “well known GUIDs” like class ids. They will be different on every installation. It would appear the GUID love from SQL server has found it’s way into IIS thru the back door.

      Source: http://sharepoint.stackexchange.com/questions/109441/app-pool-created-with-powershell-name-appears-as-guid-in-iis

      Reply
  • January 20, 2015 at 3:54 pm
    John Calvert

    Hi Vlad, couple of suggestions:
    * since title is “configure the Managed Metadata Service Application”, suggest you rip out the stuff related to content type hub, or put that at the end. I’ve often had to configure MMS but only occasionally had to config CTH. But lots of people put the CTH stuff up front which I find misleading / confusing.
    * add some details about adding the MMS SA to the service application associations for Central Admin if the MMS SA is not included in the default associations. Otherwise you can’t access the MMS from CA

    Reply
  • February 20, 2015 at 1:42 am
    Tarun

    Hello, when i go to the site setting -> site collection features, i can’t find the Content Type Syndication Hub Feature. There is only Custom Site Collection Help, Open Documents in Client Application by Default, Search Server Web parts and Templates, Three-state workflow

    Reply
    • February 23, 2015 at 8:30 am
      Vlad Catrinescu

      Hey, are you sure you are a site collection admin?

      Reply
  • March 4, 2015 at 6:31 pm
    Tom

    That side bar that tracks down the screen is super annoying. I almost hate reading your stories just because of the continual jerky jumping motion. I made sure to block it. Thanks for the article though.

    Reply
    • March 10, 2015 at 10:59 am
      Vlad Catrinescu

      Hey Tom,

      I disable the side bar that scrolls with you when yo scroll down the article. :).

      Thanks for the feedback!

      Reply
  • October 3, 2015 at 10:44 pm
    Dearie

    Hey, great article! can u publish content types from the content type hub to doc libraries in a project web app on the same farm? thx!

    Reply

Leave a Reply

Top Learning Resources

15 49.0138 8.38624 1 0 4000 1 https://vladtalkstech.com 300 1