Tuesday, May 31, 2016

Configuring the SharePoint 2013 Managed Metadata service for Navigation

Configuring the SharePoint 2013 Managed Metadata service for Navigation

One of the new features of SharePoint 2013 is the ability to save your custom navigation in the Managed Metadata Service Application. Some of my coworkers were playing with it and noticed it worked fine on farms set up with the Farm Configuration Wizard (Booooo!) but did not work on Farms where the service applications had been lovingly created by hand. With some help we were able to find the difference and fix it. I would tell you how now, but I’m building up for the big reveal at the end. Big reveals are the hallmark of great storytelling.
We found the problem when going to a site collection with the Publishing Feature enabled and going to Site Settings > Navigation. We tried to enable the Managed Navigation, which stores our custom navigation links in the Managed Metadata service. Here’s what the problem looked like:
Office-PC 8-8-2012 10.11.05 PM -2
We checked the two boxes to enable Managed Navigation. Since we were turning it on for the first time we didn’t have a term set created to store our navigation in. Clicking the “Create Term Set” button on the bottom resulted in the following error:
Failed to create term set. A default managed metadata service connection hasn’t been specified.
This message made it sound like the service application wasn’t created (it was) or that it wasn’t in this web application’s proxy group (it was), but that wasn’t the case. We discovered there’s a magic checkbox in the Proxy for the Managed Metadata Service application that makes it available for navigation. The Farm Configuration Wizard checks that checkbox. I hadn’t. Here’s how to do it. Go into Central Admin > Manage Service Applications and highlight the Managed Metadata Service Proxy. Then click Properties in the Ribbon.
Office-PC 8-8-2012 10.12.25 PM -2
In the Properties for the Proxy, check the box next to “This service application is the default storage location for column specific term sets.”
Office-PC 8-8-2012 10.12.56 PM
If you’d prefer to do it with PowerShell (and honestly why wouldn’t you?) you can do it like this:
Office-PC 8-9-2012 9.05.41 AM
and for your copying and pasting pleasure:
$saproxy = Get-SPServiceApplicationProxy | Where-Object { $_.typename -like "Managed*" }
$saproxy.Properties.IsDefaultSiteCollectionTaxonomy
False
$saproxy.Properties.IsDefaultSiteCollectionTaxonomy = $true
$saproxy.Update()
Regardless of how you change that setting, either through PowerShell or the wimpy way through Central Admin, you should be able to create a Term Set when enabling Managed Navigation. Victory looks something like this:
Office-PC 8-8-2012 10.23.24 PM -2
Hope this help,


Monday, May 16, 2016

How to remove delegate control rights in AD

How to remove delegate control rights in AD

Hi

Question:
I have added a user on the Delegate Controls wizard but now I want to remove it, how do I do this?
Solution :
on the OU open the properties and then go to security tab, here the user account should be listed and can be removed.

Hope this help,
Oumaima

Sharepoint Designer 2013, XSLT List View Options ribbon option is not showing

Sharepoint Designer 2013, XSLT List View Options ribbon option is not showing I have an ordinary Wiki Page, also tried making an Article...