11

Firstly, you need to know that Managed Metadata Service can be responsible as a Content Type Hub. Content Type Hub is a location where you can manage and publish content type across site collection, web application and farm. One more terminology you need to know is Content Type Subscriber, which will subscribe to Content Type Hub. Once you publish Content ...


6

You can change it via PowerShell. See this article (Link Dead, 2019): http://www.sharepointanalysthq.com/2010/11/how-to-change-the-content-type-hub-url/ Archived Link : http://web.archive.org/web/20110119230901/http://www.sharepointanalysthq.com/2010/11/how-to-change-the-content-type-hub-url/ They basically show how to use this cmdlet: Set-...


4

There is a hidden taxonomy list at site collection level which is populated with terms as they are used. The default is for all users to have read access on this list. However, if you start with something like a blank site template and then retro fit MMD then it seems this permission does not always get applied. Navigate to the hidden list at /lists/...


4

If I understood the scenario correctly, you have TERM SET called Department that contains TERMS like IT, Economy. In this case you could create new term inside the term set "Department", and name it "SUPPORT". Then you should merge the IT term to the new "SUPPORT" term. Note! This will remove term IT, so you can no longer use IT when you create new ...


4

This article fixed my issue: The cause of all this trouble is a permission issue. More precisely a permission issue on the TaxonomyHiddenList. The TaxonomyHiddenList list can be viewed by navigating to /Lists/TaxonomyHiddenList/AllItems.aspx. This list contains the details of all of the terms that are used in any managed metadata column. When ...


3

You need to associate your metadata application with the default application proxy group. Go to Central Admin > Application Management > Configure Service application associations. In the top right corner on the page, change the view to Service Applications. Click the "default" proxy group and check the box for your second Metadata application. Click OK ...


3

When you create the second MMS2, avoid adding it to the default proxy group. If you do, all web apps will have two MMSs, which should be avoided. My guess is that's what happened in your environment.


3

We had the same kind of problem in one of the farm. What we did: Stop the MMS service on the effected server (wfe) ( from central admin > system settings > manage services on server) Check IIS and make sure their is no app pool and Site enter for MMS ( under the Services WebSite). if any entry exist for Managed Meta data service, please delete it. If not ...


2

You have to connect to the term store and then construct a TaxonomyFieldValue and then use the target field's SetFieldValue() method to assign the value. See here: http://social.technet.microsoft.com/Forums/da-DK/sharepointadminprevious/thread/4c63fff1-8681-42a1-9fd2-256f1f80935b regards, KS


2

I used this tool from Codeplex, and entered in the import CSV the column LCID with german language (LCID=1031). Worked smooth when transferring from SharePoint 2010 to SharePoint 2012 As a hint for german speaking areas, please keep in mind to use Unicode settings and the comma instead the semicolon as list separator, then this works smooth as silked http:/...


2

You do this in powershell by converting the TermSet to a NavigationTermSet $site = Get-SPSite -Identity $sitename $navTermSet = [Microsoft.SharePoint.Publishing.Navigation.NavigationTermSet]::GetAsResolvedByWeb($termSet, $site.RootWeb, "GlobalNavigationTaxonomyProvider"); Now you have access to the navigation term set object in powershell and can use it ...


2

Finally I achieved it with following code. $navigationSet = $group.CreateTermSet($termsetName) $navigationSet.SetCustomProperty("_Sys_Nav_IsNavigationTermSet", "True") $navigationSet.SetCustomProperty("_Sys_Nav_AttachedWeb_SiteId", $site.ID.ToString()) $navigationSet.SetCustomProperty("_Sys_Nav_AttachedWeb_WebId", $site.RootWeb.ID.ToString()) $...


2

Basically selection of submission policy (Open or close) will define whether a user can add new terms in the term store or term store managed by the Managers. Anyone can add a new term to an open term set. For Closed Term set only administrator can add it. Only people who were identified as contributors to a term set group can add terms to a closed term set ...


2

I received this error after running a patch (Dec 2016) on SharePoint. The thing that worked for me is running this in Powershell: Initialize-SPResourceSecurity (don't forget to run this first: Add-PSSnapin Microsoft.SharePoint.Powershell;) Credit: https://www.habaneroconsulting.com/insights/the-managed-metadata-service-or-connection-is-currently-not-...


2

OK, it turned out that the Managed Metadata Service was not associated with the web application hosting my site collection. So to fix that, I went to: Central Administration > Application Management > Configure service application associations Once there, I found my web application and then opened Application Proxy Group. It turned out that Managed ...


2

Looks like SPResourceSecurity not properly registered. open cmd as administrator type: cd C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN then type: psconfig.exe -cmd secureresources Source: https://social.technet.microsoft.com/Forums/sharepoint/en-US/edf7946a-a178-46e8-b7f3-82f80ad4a194/have-anyone-set-up-mysite-on-a-...


2

I think you should try the Set-SPMetadataServiceApplication, What i am reading that you can set the Service administrator with the above command. See this Example: Set-SPMetadataServiceApplication -Identity "MetadataServiceApp1" -AdministratorAccount "contoso\username1" -FullAccessAccount "contoso\AppPoolAccount1,contoso\AppPoolAccount2" -RestrictedAccount ...


2

Follow below steps and try, if accepted answer does not work. In the central administration --> Manage Service Application Page, click on the line corresponding to the connection (not on its name, on its right) and click on "Properties". Click on the "This service application is the default storage location for column specific term sets" checkbox and ...


2

I have this little powershell function you can try it out... function SetManagedMetadaService { Param( [parameter(Mandatory=$true)][string]$ServiceName, [parameter(Mandatory=$true)][string]$HubSiteUrl ) Write-Host "Setting contenttype hub Url" #Get-SPServiceApplication | ForEach-Object { # if ($...


2

Try it as below: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue $WebURL="https://sitecollectionurl/" $ListName="Financial" $FieldName="Doc Type" $Web = Get-SPWeb $WebURL $List = $Web.Lists[$ListName] if(!($List.Fields.ContainsField($FieldName))) { $TaxonomySession = Get-SPTaxonomySession -Site $web.Site $TermStore = $...


2

If you click OK in that screen, the first MMS, where you currently have your term groups, terms, enterprise keywords and tags, won't be the default MMS. That means that all new entries will end up in your new MMS and at the same time already configured terms will stay in the old, no longer default, MMS. This ain't a recommended procedure, and you should ...


2

You can't do this using only PnP commands. But you can do it by dropping down to a little bit of CSOM. First, fetch your source term and your destination term. $pinnedTerm = Get-PnPTaxonomyItem -TermPath "Conglomo|Departments|Research and Development" $sourceTermSet = Get-PnPTaxonomyItem -TermPath "Conglomo|Sitemap|Department Sites" Then, call the one of ...


1

Your interpretation is correct. A Managed Metadata Service application can be used to share content types across site collections by associating a Content Type Hub with it. A content type hub site is generally created as it's own site collection and is purely used to store custom site columns and content types and publish these to subscribing site ...


1

Install term set export/import tool WSP from here. Then use the following PowerShell to export and import Term Groups one by one including all content. $ver = $host | select version if ($ver.Version.Major -gt 1) {$host.Runspace.ThreadOptions = "ReuseThread"} if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) { ...


1

You should use the parameter DefaultProxyGroup when using New-SPMetadataServiceApplicationProxy


1

Managed Metadata service is a service offered by sharepoint . The MMS is divided further in taxanomies(term store),folksonomies(keywords),syndicated content types . The managed metadata service application has two purposes, 1. To make it possible to use managed metadata and 2. Share content types. The MMS has 1 term store metadata service applications and ...


1

I think you want to know about the term set scope, Term set has two scope level Local and Global(read below for more details). Term Set A Term set is a group of related terms. Terms sets can have different scope, depending on where you create the term set. Local term sets are created within the context of a site collection, and are available for use (...


1

In a very dull non-techie script free answer, might I suggest creating a new Keywords Term Set called perhaps "Approved Keywords", moving approved Enterprise Keywords into it and then adding the synonyms to the terms in the "Approved Keywords" list.


1

One approach you can take is updating the Managed Metadata field first, and then changing it in Active Directory, then running your User Profile Service Application sync then a search crawl. It doesn't create a duplicate, and as far as I can tell it will resolve itself (since my test showed up under Departments in my refinement panel). I would feel safer ...


1

[update] You are almost there, at first I thought you where referencing the 2013 namespace which does exist, it just doesn't work, now I know a bit more I am 90% sure you can get around your issue with the following. I know I know it might not seem to be what you want at first, but I assure you it is. I see what you are doing now and I think this will work ...


Only top voted, non community-wiki answers of a minimum length are eligible