I had this situation where I’d created a couple of content types through a feature and deployed them to a Metadata Hub.  I’d tried and tried to get the bloomin’ things to be picked up by my subscribing Site Collection, but no matter how often I seemed ot run those two jobs “Content Type Hub” and Content Type Subscriber”, the content types never seemed to Sync.

I’d forgotten a simple thing … and it was in this blog entry by Paul Grimley …

I’d based both of my Site Collections, publisher and subscriber on the Blank Site Template, but in order for Managed Metadata stuff to work correctly you must ensure that the “TaxonomyFieldAdded” feature is enabled, which is a hidden feature.  If you don’t enable this feature you can’t use Managed Metadata and also it would seem that the actual Publishing and Subscribing of content types don’t kick in properly.  So make sure you activate the feature in both Publishing and Subscribing Site Collections as follows:

Enable-SPFeature -Url <Publishing Site Collection Url> -Identity "73EF14B1-13A9-416b-A9B5-ECECA2B0604C" 
Enable-SPFeature -Url <Subscribing Site Collection Url> -Identity "73EF14B1-13A9-416b-A9B5-ECECA2B0604C"

You’ll find you can use the Managed Metadata Field type now AND your publishing and Subscribing of content types kicks in.  As always, it’s simple when you know how …

Cheers

Dave Mc