I have a web template based off of a Team Site. I included all of the site and web scoped features that were in an OOB Team Template, minus "Wiki Home Page" feature. I got the list of features through powershell, so I'm pretty sure I'm not missing anything (as the sts onet only lists a small handful of features). I have also added in "MetaDataNav "7201d6a4-a5d3-49a1-8c19-19c4bac6e668" at the web level, as I had read it is another dependency for Term Store Management. Despite this, I am not seeing the "Term Store management" under "Site Administration," nor are my content types being published to this site via the Content Type Syndication hub. I have manually run the timer jobs, and am not having a problem with any OOB Sites subscribing to the hub. In fact, they automatically subscribe on creation with no need for running the timers manually. Anyone have any advice on this matter? - Daniel

Hi Daniel, Please try republish the content type from content Hub and check whether any error has been logged or not. you can find the options to see the errors via site setting in the content Hub site. Hope the error logs will help to identify the root cause of the failure Regards, Roy Joyson Please remember to mark your question as "answered"/"Vote helpful" if this solves/helps your problem.Roy Joyson

I checked the ULS logs and didn't see anything out of the ordinary. Which setting are you referring to? 'Audit Log Reports'? I have a feeling I'm about to learn something mighty useful, do continue. - Daniel

Hi Daniel in the content hub site settings we can see a link for "Content type service application error log ". please check the same for more details of error. Regards, Roy Joyson Please remember to mark your question as "answered"/"Vote helpful" if this solves/helps your problem.Roy Joyson

Nope, nothing out of the ordinary. Any other ideas? I've reviewed my web templates active features side by side with an OOB Team site that is functioning properly. Only difference is mine has WikiHomePage removed and some added features to populate lists and pages. I'm stumped. . . - Daniel

Okay, I fixed it, though I'm not sure what the problem is exactly. PS C:\Users\Administrator> Disable-SPFeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -Url http://windows-emavpj7/sites/mmtest PS C:\Users\Administrator> Enable-SPFeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -Url http://windows-emavpj7/sites/mmtest And now it's there. Note that I did try to enable it first, even though I knew it was activated from reviewing the active features, just to make sure. Maybe this will help, I'm activating my site scoped features through an event receiver on my Web Templates (in case the template is used to create a subsite) using the following code (abbreviated to not include all features) public override void FeatureActivated(SPFeatureReceiverProperties properties) { SPWeb web = properties.Feature.Parent as SPWeb; //Activate Site Collection Features if (web != null) { List<Guid> siteFeatures = new List<Guid>(); siteFeatures.Add(new Guid("73ef14b1-13a9-416b-a9b5-ececa2b0604c")); foreach (Guid featureID in siteFeatures) { if (web.Site.Features[featureID] == null) { web.Site.Features.Add(featureID); } } web.Update(); } } - Daniel