10

Deprecated features User Profile service (ForeFront Identity Manager Client) SharePoint Server 2016 no longer uses FIM as the synchronization client. FIM (synchronize between Active Directory and SharePoint) is being removed and the bidirectional sync with AD has been improved. The default process is Active Directory Import. You can also use any ...


9

You can try something like this in powershell. $allSiteFeatures = Get-SPFeature | Where-Object { $_.Scope -eq "Site" } $activeFeatures = Get-SPFeature -Site "http://sitecollectionUrl" $allSiteFeatures | ForEach-Object { $active = $false foreach($feature in $activeFeatures) { if($feature.Id.ToString() -eq $_.Id.ToString()) { $...


6

You would need to Create a new Web Application in farm 2 Export solutions* from farm 1 Install solutions in farm 2 Backup content databases belonging to the web application in farm 1 Restore all content databases in farm 2 Enable all features on farm 2 Web App | Site | Web that are enabled in farm 1 web app Test From an abstract level, this works. To make ...


5

To just activate the feature use the following command: Enable-SPFeature –Identity <<FeatureID>> –url http://myspsite/ To find the FeatureID use the following for hidden features: Get-SPFeature -Limit ALL | Where-Object {$_.Hidden -eq $true -and $_.Scope -eq “WEB”} | Sort-Object DisplayName | Select DisplayName, Id


4

You can only have Content types at Site or List level. So, even if your feature is scoped as web the Content types will be added to the Site level (at root web). From there on, content type will be available, to be added to the lists and document libraries in all webs and so on.


4

CSOM Feature object exposes the following properties: DefinitionId - gets the GUID that identifies the Feature definition DisplayName - feature name Such SSOM Feature properties as SPFeature.Definition or SPFeature.Properties are not available in CSOM/REST. Below examples demonstrate how to manage features using CSOM Example: how to retrieve activated (...


4

Yes the site template Enterprise Search Center is available in the SharePoint Server 2013 standard edition. The features of search NOT available in standard version is: Content Search Web Part Custom entity extraction Extensible content processing Query rules—advanced actions Search vertical: “Video” Tunable Relevancy Reference: SharePoint 2013 feature ...


3

None of these features required to be activated to perform the Search on the Site. Search will work without these. These features used when you want to import /export the search configuration from /to another site collection. SharePoint 2013 Design Manager design packages You would choose this option if you are designing a site and creating ...


3

You dont need to activate any features in your site. Just configure the contentsource in the serchservice application in your central administration to crawl that site. Here's some more info on that


3

Due to customization, most of stuff is manually and required extra steps. Build New Farm( make Sure it should be same version level) Create and Configure the Service Applications Create a New Web application and configure the Authentication. make sure same authentication Now you have the Apply the customization( i.e any web .config change, hive folder ...


3

here is technet article which will give you some highl level stuff: What's deprecated or removed from SharePoint Server 2016 The following features and functionality have been deprecated or removed in SharePoint Server. Duet Enterprise for Microsoft SharePoint SharePoint Foundation Standalone Install mode ForeFront Identity Manager client (FIM) Excel ...


2

lets explain what you did! you had a feature that was built within a wsp, you deployed the wsp to a webapp and then activated the feature... you then decide to remove the wsp but forgot to deactivate the feature leaving you in the position that your currently in! next time deactivate the feature before removing the wsp, once you remove the wsp it removes ...


2

You cannot define feature dependencies cross scoped according to Activation Dependencies and Scope. In theory you can change the visibility once the site collection feature was enabled but you need to do the same for ever sub site that will be created. From my point of view the best way would be if you check in a feature event receiver of the web scoped ...


2

as far as I know retracting solutions doesn't deactivate their features, so although you wont be able to find or activate/deactivate those features, their references are still there. on the particular case of event receivers, it could turn out to be a major problem. the receiver may still be attached and if you redeploy/reactivate you may end up with firing ...


2

How to exclude Document Sets from List View using filters Assume we have OOTB Document Set content type (0x0120D520) added in Documents Library, then the following filter could be specified: Content Type is not equal to Document Set


2

The below worked for me. Create a visual studio solution and add Module (Module1) which would create a new Feature (Feature1). Create required User Controls and master page under Module1 and modify Elements.xml file accordingly. Deploy the solution to verify whether master page and user controls are working fine. Create new visual studio solution and open ...


2

The Features property only returns Features that have been activated. Web.Features property


2

Depending on where the Central Administration is hosted (Web Front End or App server), and depending on the target of the WSP package (I'm not talking of the scope of the feature; I'm talking about the "Deployment Server Type" setting of the solution), this may happen. For example, the features contained in the package are only installed on the Web ...


2

Regarding your question, are the features are relevant only for the sites and not pages? As a short answer Yes, it's a Web / Site scope. Generally, the feature is activated at Farm / Web Application / Web / site collection scope. Check also Listing All SharePoint Server 2013 Features – Including Name, Title, Scope, ID and Description


2

Try below code: You can use SPFarm.Local.FeatureDefinitions[featureName] for Web features // Look for feature definition using feature name SPFeatureDefinition featureDefinition = SPFarm.Local.FeatureDefinitions[featureName]; // Look for activated feature SPFeature feature = web.Features.Cast().FirstOrDefault(f => f.DefinitionId == featureDefinition.Id)...


2

The features are the same, but the 14/15 indicates where any supporting files are stored. When a solution is deployed through Central Admin, you don't have any control over this, but if you use PowerShell to deploy your solution (using the Install-SPSolution cmdlet), you can specify a "CompatibilityVersion" of 14, 15, or All (both 14 and 15). Specifying 14 ...


2

Here are the articles Deprecated or removed features from SharePoint 2016 New and improved features in SharePoint 2016


2

Learned from Microsoft support that this is an expected behaviour. Newly created site collections are not provisioned with this library any longer as this functionality is available in the O365 Security & Compliance center.


2

If this is expected behavior then why is the ability to configure it in the UI allowing you to get an error message? Also, something I noticed is that I didn't have audit events from SharePoint in the Security and Compliance center until I turned on auditing for site collections. I've put in a DCR to Microsoft to see about getting this fixed if anyone ...


2

Hello here are described server roles and features which need to be activated for SharePoint 2013. There is Windows Feature AS-HTTP-Activation which must be activated, so I think, answer is YES. Otherwise there can be a little differences caused by version of Windows Server you run your SharePoint 2013 servers. Hope it helps!


1

No, if you don't have the permission to do so, you cannot enable the feature. Ask your site collection administrators or a farm admin to do it for you if it is something you need for your site.


1

It seems there is no way to retrieve the list of available features from the client side, but you could extract this information from Features page as demonstrated below: function getFeatureDefinitions(scope){ var url = SP.Utilities.Utility.getLayoutsPageUrl('ManageFeatures.aspx'); if(scope == 'Site') url+= '?Scope=Site'; return $.get(...


1

To show all the features on the farm listed by display name and sorted use this: `Get-SPFeature | Sort -Property DisplayName' To see all features for a Web Application: Get-SPFeature -WebApplication http://webapplication To see all features for a Site Collection: Get-SPFeature -Site http://sitecollection To see all features for a Site: Get-SPFeature -...


1

Include the DisplayName in your .Include: clientContext.Load(webFeatures, fcol => fcol.Include( f => f.DefinitionId, f=> f.DisplayName));


1

You do need to make sure that the Search and Offline Availability page has the Allow this Site to Appear in search results setting enabled.


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