Upgrading a multi-server SharePoint farm from Standard to Enterprise

1. Stop the Timer Service on all machines in the farm except for 1, in my case I left it running on the APP server.
2. Add the new product key and hit OK to start the SKU upgrade process in the Central Admin GUI.
3. Watch the event log of the APP server and wait for an entry with a source of “SharePoint 2010 Products Configuration Wizard” which will inform you that it was Successful.
4. Start the Timer Service on the next machine in the farm.
5. Watch the event log and wait again for the successful entry…
6. Continue with steps 4-5 on all additional servers in the farm.
7. Once you’ve received all successful entries in your event logs, a minute or so later you should get a successful notification in the GUI for the SKU upgrade.

SharePoint 2010 / 2013 HTTP 500 Internal Server Error Explanation & How to fix

HTTP 500 Internal Server Error Explanation & How to fix

HTTP 500 Internal Server Error in SharePoint 2013

Moving the Index Partition to the Web Front Ends

Manage the index component in SharePoint Server 2013 - By Microsoft

Moving the Index Partition to the Web Front Ends - By Steve Mann

Move the search index location in SharePoint 2013 - By Marco

How to add Desktop Experience feature on Windows Server 2012 “Server

https://blogs.technet.microsoft.com/meamcs/2012/05/01/how-to-add-desktop-experience-feature-on-windows-server-2012-server-8-beta/

Thanks Tamer

Using Script
http://blog.qumsieh.ca/2010/02/16/hide-columns-in-sharepoint-new-edit-and-disp-forms/

Using Designer 
http://promx.net/en/2016/09/how-to-hide-columns-from-sharepoint-forms/ -


Using Power Shell

First load SharePoint Core Assembly

[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)

 

$url = "http://ulabtechnologies.sharepoint.com";

$list = "Employee";

$fieldname = "NewColumn";

 

#Setting up context

$contextSite = New-Object Microsoft.SharePoint.SPSite($url);

$contextWeb = $contextSite.OpenWeb();

 

$list = $contextWeb.Lists.TryGetList($list);

$field = $list.Fields[$fieldname];

 

# Controls Field in Edit Form

$field.ShowInEditForm = 1;

# Controls Field in New Form

$field.ShowInNewForm = 0;

# Controls Field in New Form

$field.ShowInDisplayForm = 1;

# Hides fields from list settings

$field.ShowInListSettings = 1;

# Hides fields from version history

$field.ShowInVersionHistory = 1;

# Hides fields form selection in views

$field.ShowInViewForms = 1;

# Don't forget to update this field

$field.Update();

# And finally dispose everything.

$contextWeb.Dispose();

$contextSite.Dispose();

Set Privileges for Using PowerShell to Manage SharePoint

To execute a command in the SharePoint 2013 Management Shell, open the Management Shell on a SharePoint 2010 server. To execute commands, the user must have the necessary privileges to the SharePoint object model and to the SharePoint databases. When you are working with SharePoint objects, connections to the database are generally created with the permissions of the current user. 

You can use SPShellAdmin for configuring a user’s privileges and security. Here’s how. 

To list Shell administrators:
Get-SPShellAdmin 

To add a user as a Shell administrator:
Add-SPShellAdmin -UserName -Database  

For example, to allow user Jeff Hay to execute commands against the PartnerNet site, use the following command: 
Add-SPShellAdmin -UserName Contoso\Jeff Hay 
-Database (Get-SPContentDatabase -Identity PartnerNet_ContentDatabase) 

Note that the Get-SPContentDatabase cmdlet and the PartnerNet content database name are used to retrieve the SPContentDatabase object. 

To remove a user from Shell Admin:
Remove-SPShellAdmin -UserName -Database  

SharePoint 2010 and 2013 Subsite backup and restore using Powershell

Backup

export-spweb -identity "http://ulabtechnologies/legal" -path "D:\subslitebacku\legasubsite.cmp"

Restore

 import-spweb -identity "http://ulabtechnologies/lcs" -path "D:\subslitebacku\legasubsite.cmp"

Note:

Master page template should be same as backup site in restore site

Creating subsite using PowerShell

Add-PsSnapin Microsoft.SharePoint.PowerShell

## SharePoint DLL
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")

#Creating Sub Sites in top site collection.
Write-Output " "
Write-Output "Creating Sub Sites"

$SiteCollectionURL = "http://legal.ulab.com/LCS/TrainSiteLgl/TrainSiteDOCRep"

$SiteCollectionTemplate = "CMSPUBLISHING#0"

$SiteCollectionLanguage = 1033

$SubSites = @("Insur","Insurrance","LegalMatters","TradeMarks")

for($i=0 ; $i -lt $SubSites.count ; $i++)
{
$SiteUrl = ""
$SiteUrl = $SiteCollectionURL + "/"
$SiteUrl = $SiteUrl += $SubSites[$i]
Write-Output " "
#Write-Output "Creating Site for " += $SubSites[$i]
Write-Output " "
New-SPWeb $SiteUrl -Template $SiteCollectionTemplate -Name $SubSites[$i]  -UseParentTopNav -Language $SiteCollectionLanguage
Write-Output " "
#Write-Output "Site Created for " += $SubSites[$i]
Write-Output " "
}

Useful tools - SharePoint Practitioners

Useful tools for SharePoint Practitioners

Thanks Vignesh

How to find which version of SharePoint we are using

• WHAT SHAREPOINT VERSION AM I USING?
• How to determine the installed SharePoint version

RSS Viewer web part missing in Content Rollup category in SharePoint 2013

We need to Activate site collection feature "SharePoint Server Standard Site Collection features".

Error loading navigation: TermStore not found

Introduction

In this posting, I present two causes of this problem, that I have experienced, and the solutions I implemented that resolved them.  The two causes involve minor interruptions to network connectivity and server restart.

Network Connectivity Interruptions

Problem

Your network experienced some very minor, very temporary interruptions in service.  Afterwards, some users were unable to connect to the SharePoint 2013 farm and others experienced an error in the global navigation bar:

Error loading navigation: TermStore not found (Correlation ID:...)

Note that a correlation ID appears with this error.  Checking farm health reports, a rule failure of the Security Token Service on WFE2 was found.  However, on investigation, all services were found to be running on this server, and all IIS application pools were found to be started.  Review of the WFE2 error logs found application errors involving claims authentication.  The server was up and IIS and all other services were found to be running.

Solution

• Restart the SecurityTokenClaimsApplicationPool.

Notes

• NLB was configured with WFE2 as primary and WFE1 as secondary.  Those users routed to WFE2 experienced failure connecting to the farm, while those routed to WFE1 just experienced the navigation error.  WFE2 eventually recovered partially on its own, but the navigation issue persisted.
• My sequence of troubleshooting steps for this issue:
1. Review farm health reports
2. Review server event logs
3. Check services on all farm servers
4. Check application pools on all farm servers

Server Restart

Problem

The farm servers are restarted.  Afterwards, users connecting to their site see the following error message displayed in the global navigation bar:

Error loading navigation: TermStore not found

Note that no correlation ID appears in this case for the error, unlike the earlier example.  Checking farm health reports, you find NO failure of the Security Token service on any any web front end. Checking IIS, you find that all application pools and sites have started.  Checking server services, you find that both FIM service, and the Search (OSearch) and Timer services, are in the stopped state.

Solution

• Start the Timer service.

http://expertsharepoint.blogspot.de/2014/08/managed-metadata-service-or-connection.html 

SharePoint 2013 Kerberos authentication configuration

http://blog.blksthl.com/2012/09/26/the-first-kerberos-guide-for-sharepoint-2013-technicians/