New answers tagged

1

I got to the bottom of this after contacting Microsoft. The problem was that the SSSvc site feature wasn't activated on the Central Admin site, which can only be enabled using PowerShell: Enable-SPFeature -identity " SSSvcAdmin " -URL http://centraladminURL


1

Managed Properties are agnostic of Site Collections. So "Wiki Category" does not belong to any site collection. They are bound to Crawled Properties that are either "out of the box" or created as the result of creating Site and List columns and then crawling the content. The only way to ensure that the Wiki Category you seek is from a specific site or site ...


1

Why not just secure the content with a workflow if the status changes? If it's secure it will not show in search. You could also eliminate the content from the default result source, but I'd prefer security.


1

Since it was created on the SSA level, this property refers to multiple site collections. You have another option to create a managed property on the site collection level and map it to that field and you use it on the site collection level.


1

Without knowing how your farm is created and if you have one search site or multiple ones is hard to say. However, if this condition is true in all environments and all site collections, then your approach is the best approach IMO.


0

Search also has the ability to remove result by URL. You could enter the URL of the canceled page manually and it will be added to the crawl rules and no longer be returned as a result.


0

Maybe you could make a search scope. You would need to make your column a "managed properties" and then add 4 rules for = everything but canceled.


0

It may be necessary to grant permissions to the container in the AD, please see Track SharePoint 2010 Installations by Service Connection Point (AD Marker)



Top 50 recent answers are included