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()) { $...


9

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 ...


8

You should enable the "SharePoint Server Enterprise Site Collection features" at the site collection level. You can find the "Site collection feature" management link on the Site Actions>Site Settings page under the section "Site Collection Administration".


5

I think any release date you see at present will be speculation as there is nothing official from Microsoft. Many have speculated that MS will try to align the Office 15 release date with their conference in November, so I suppose the best answer anyone can give you right now is "probably the end of this year".


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


5

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 ...


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

Simillarly as with Content Query Web Part (CQWP) also the Summary Link Web Part is governed by an XSL file in charge of rendering content available at the Site Collection Level in the Style Library called SummaryLinkMain.xsl. I would strongly recomand simply copy that file, rename it to your liking and then export your SLWP and change its attributes to ...


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

List template gallery (the url atribute of _catalogs/lt) is only available in the root web of the site collection. So you get an exception when the feature is activated in the subsite because it cannot find the specified list (http://sitename/subsitename/_catalogs/lt). The templates should be available across the site collection. Change the feature scope to ...


3

The only 'fixed' information we know about dates at this point (early March) is that there will be a beta version of Office 15 and its companion software (SharePoint 15, Lync 15, etc) 'this summer'. We do not know anything beyond that, if 'knowing' is defined as what Microsoft has published. 'This summer' can technically mean anything up to and including ...


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

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

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

You can use delegate controls, check this article.


2

The entire WSP file is stored in the configuration database so you can always get it from there with PowerShell like: (Get-SPFarm).Solutions | ForEach-Object{$var = (Get-Location).Path + "\" + $_.Name; $_.SolutionFile.SaveAs($var)} When a farm solution is deployed the assemblies are copied to GAC or webapp bin folder. All the feature files are copied to ...


2

If you're working with Visual Studio 2010 make sure that new/old Feature is added in Package. You can use the Package Designer to create and customize a package (.wsp). For example, you can add SharePoint project items and Features, specify if the Web server is reset when the solution is deployed, and set the deployment server type. http://msdn....


2

To remove the link break the connection to the Search Center Step by step: Select Site Actions | Site Settings In Site Collection Administration click Search Settings In Site Collection Search Center select Do not use custom scopes. ... OK


2

SharePoint 2013 reached RTM on October 11, 2012. Reference: SP Team Blog & Office Blog


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

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

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

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

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)...


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