Create the Managed Metadata Service Application in SharePoint Server (GUI & PowerShell)

The most common examples for metadata are “data about data“, or “info about info“. And that’s obviously true πŸ™‚

In a way, you give more info on the data you have. I see that as some kind of “drill down a bit further” in the information.

In SharePoint words, we are talking about taxonomy and folksonomy.

For more information please refer to the official documentation:

In order to benefit from this metadata feature in SharePoint Server, we need to configure the Managed Metadata Service Application.
You can also create a Content Type Hub (to share content types between Site collections), but this is not mandatory.


Create Managed Metadata Service Application via Central Admin (GUI)

Assuming you have the correct permissions (logging into the SharePoint server with an account member of the Farm Admin group), let’s create this awesome feature!

  • Log into Central Admin
  • Navigate to “Manage service applications” under Application Management
  • Click on “New” in the ribbon >> Managed Metadata Service

Managed Metadata Service

  • Give the application a Name
  • Check the SQL Server & Instance (pre-populated)
  • Enter a name for the MMS database
  • Choose the authentication method (I’ll keep the default – Windows)

Create MMS – part 1

  • Enter a Failover database server (if you have one)
  • Select an existing application pool OR create one (I’ll create one)
  • Select the account to run this application pool (I’ll use a separate acct registered as Managed Account in SP called “SPAppPool”)

Create MMS – part 2

  • Enter the URL of the Content Type Hub (if you have created one prior)
  • Choose “Report Syndication report […]” and “Add this service application […]” as you need (I’ll keep the default selected)

Create MMS – part 3

Once you’re happy with your choices, click on “OK
Note: When you click on “OK” it looks like nothing is happening (booo!) but give it a couple of minutes depending on your environment

When finished, we are redirected to the Service Applications page, where we can check out the new MMS Application πŸ™‚


MMS now created


The difference between SharePoint 2013 and SharePoint 2016 when creating this service application is that, in SharePoint 2016, we don’t need to go to “Manage services on servers” and start the “Managed Metadata Web service” anymore πŸ™‚ It’s done automatically!


Access the Term Store

Now that we have the Managed Metadata Service Application created, let’s access the Term Store.

  • Click on the MMS Application

Managed Metadata Service Application

And if all went well, tadaaa! πŸ™‚


Term Store ready



Create Managed Metadata Service Application using PowerShell

We can also create the Managed Metadata Service Application using PowerShell, obviously!
So open your PowerShell editor of choice, and let’s start.

Firstly, the main cmdlet. We will use the New-SPMetadataServiceApplication.
There are many parameters for this cmdlets, but we will only use a few of them.

Secondly, we will also use theΒ New-SPMetadataServiceApplicationProxy as the connection is not created automatically as it is when using Central Admin.

$newSPMetadataServiceApplicationSplat = @{
    Name                 = "Managed Metadata Service Application"
    DatabaseName         = "SP2016_Managed_Metadata_DB"
    ApplicationPool      = "DefaultAppPool"
    FullAccessAccount    = "exams\spapppool"
    DatabaseServer       = "DCSQL\SP2016"
$MMSApp = New-SPMetadataServiceApplication @newSPMetadataServiceApplicationSplat


Now let’s create the application proxy (connection)

New-SPMetadataServiceApplicationProxy -Name "Managed Metadata Service Application Proxy" -ServiceApplication $MMSApp -DefaultProxyGroup


As you can see in cmdlet #1, I’m using what’s called “splatting“. This is useful when using a cmdlet with multiple parameters, that stretches for miles long!

If you don’t know what splatting is, check out this great article made by Rob Sewell (@sqldbawithbeard):


Right, there you have it πŸ™‚

Now, you have to configure this application for your business needs (who will get access, configure the Terms, Term Groups, etc…)



Comments are closed.

%d bloggers like this: