• Create user accounts for "Portal Super Reader" and "Portal Super User" in your active directory
• Grant web application policy on these user accounts on web applications.
• Associate super user and super reader user accounts to web applications

• SPS_SuperUser
• SPS_SuperReader

Import-Module ActiveDirectory -ErrorAction SilentlyContinue

#Set configurations
$AccountPassword = "Password1"
#Convert to Secure string
$Password = ConvertTo-SecureString -AsPlainText $AccountPassword -Force

$Domain = "YourDomain.com"
#Specify the OU
$AccountPath= "ou=SharePoint,DC=YourDomain,DC=com"

#Create Super Reader Account
$Account="SPS_SuperReader"
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="SharePoint 2013 Super Reader Account for object cache."}

#Create Super User Account 
$Account="SPS_SuperUser"
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="SharePoint 2013 Super User Account for object cache."} 

1. SharePoint Central administration >> Application Management >> Manage web applications.
2. Select your web application >> From the ribbon, click on User Policy button.
3. Click on "Add" button from the User policies page.
4. From the zones list, select "All zones" and click on next.
5. In the Add users page, Enter the Super Reader user name. Under Permissions, Select "Full Read" option and Click on Finish button.

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

Function Grant-UserPolicy($UserID, $WebAppURL, $Role)
{
    #Get the Web Application
    $WebApp = Get-SPWebApplication $WebAppURL

    #Convert UserID to Claims - If Web App is claims based! Domain\SPS_SuperReader to i:0#.w|Domain\SPS_SuperReader
    if($WebApp.UseClaimsAuthentication)
    {
        $UserID = (New-SPClaimsPrincipal -identity $UserID -identitytype 1).ToEncodedString()
    }

    #Crate FULL Access Web Application User Policy
    $ZonePolicies = $WebApp.ZonePolicies("Default")
    #Add sharepoint 2013 web application user policy with powershell
    $Policy = $ZonePolicies.Add($UserID,$UserID)
    #Policy Role such as "FullControl", "FullRead"
    $PolicyRole =$WebApp.PolicyRoles.GetSpecialRole($Role)
    $Policy.PolicyRoleBindings.Add($PolicyRole)
    $WebApp.Update()

    Write-Host "Web Application Policy for $($UserID) has been Granted!"
}

#Get all Web Applications
$WebAppsColl = Get-SPWebApplication
foreach($webApp in $WebAppsColl)
{
    #Call function to grant web application user policy
    Grant-UserPolicy "Crescent\SPS_SuperReader" $webapp.URL "FullRead"
    Grant-UserPolicy "Crescent\SPS_SuperUser" $webapp.URL "FullControl"
}

$WebApp = Get-SPWebApplication "http://web-app-url/"

$webApp.Properties["portalsuperuseraccount"] = "i:0#.w|Crescent\SPS_superuser"
$webApp.Properties["portalsuperreaderaccount"] = "i:0#.w|Crescent\SPS_superreader"

$WebApp.Update()

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Get all Web Applications
$WebAppsColl = Get-SPWebApplication

foreach($webApp in $WebAppsColl)
{
    #Update with your SuperUser and Super Reader Ids
    $SuperReader = "Crescent\SPS_SuperReader" 
    #Convert to Claims ID
    $SuperReaderID = (New-SPClaimsPrincipal -identity $SuperReader -identitytype 1).ToEncodedString() 

    $SuperUser = "Crescent\SPS_SuperUser" 
    $SuperUserID = (New-SPClaimsPrincipal -identity $SuperUser -identitytype 1).ToEncodedString()

    #Set Super User and Super Reader accounts 
    $webApp.Properties["portalsuperreaderaccount"] = $SuperReaderID 
    $webApp.Properties["portalsuperuseraccount"] = $SuperUserID 

    $webApp.Update() 
    Write-host Object cache accounts updated for $WebApp.URL
}

• Open your SharePoint site collection with SharePoint Designer
• Click on the Site Options button from the top right hand corner of the ribbon
• You'll be presented with a window to manage site’s property bag under "Parameters" tab.
• From here, you can add, modify or delete properties.

<style>
#sideNavBox a[href$="/_layouts/15/viewlsts.aspx"]
 {
    display: none;
 }
</style>

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#create a new result source at Search Service Application
$SearchServiceApplication = Get-SPEnterpriseSearchServiceApplication 
$FederationManager = New-Object Microsoft.Office.Server.Search.Administration.Query.FederationManager($SearchServiceApplication)

$SearchOwner = Get-SPEnterpriseSearchOwner -Level Ssa
$ResultSourceName ="Bing Search Result Source"

#For Site Level Result Source, Use:
#$SiteCollection = Get-SPSite $SiteUrl -ErrorAction SilentlyContinue
#$SearchOwner = Get-SPEnterpriseSearchOwner -Level SPSite -SPSite $SiteCollection

#Check if the Result Source is already exists
$ResultSource = $FederationManager.GetSourceByName($ResultSourceName,$SearchOwner)
if($ResultSource)
{
    $FederationManager.RemoveSource($ResultSource)
}

# create a new result source
$Query = "{SearchTerms}"

$ResultSource = $FederationManager.CreateSource($SearchOwner)
$ResultSource.Name = $ResultSourceName
$ResultSource.ConnectionUrlTemplate = "http://www.bing.com/search?q={searchTerms}&format=rss&Market=en-us"
$ResultSource.ProviderId = $FederationManager.ListProviders()['OpenSearch Provider'].Id
$ResultSource.CreateQueryTransform($queryProperties, $query)
$ResultSource.Commit()

Write-host Result Source: $ResultSourceName has been created successfully!

$HostFile = 'C:\Windows\System32\drivers\etc\hosts'

# Create a backup copy of the Hosts file
$dateFormat = (Get-Date).ToString('dd-MM-yyyy hh-mm-ss')
$FileCopy = $HostFile + '.' + $dateFormat  + '.copy'
Copy-Item $HostFile -Destination $FileCopy

#Hosts to Add
$Hosts = @("intranet.Crescent.com", "Intranet", "mysite.crescent.com")

# Get the contents of the Hosts file
$File = Get-Content $HostFile

# write the Entries to hosts file, if it doesn't exist.
foreach ($HostFileEntry in $Hosts) 
{
    Write-Host "Checking existing HOST file entries for $HostFileEntry..."

    #Set a Flag
    $EntryExists = $false

    if ($File -contains "127.0.0.1 `t $HostFileEntry") 
    {
        Write-Host "Host File Entry for $HostFileEntry is already exists."
        $EntryExists = $true
    }
    #Add Entry to Host File
    if (!$EntryExists) 
    {
        Write-host "Adding Host File Entry for $HostFileEntry"
        Add-content -path $HostFile -value "127.0.0.1 `t $HostFileEntry"
    }
}

Get-SPProduct -local

• Site Settings >> under Site Actions section, click on Reset to site definition 
• Choose a specific page or entire site. Click on Reset! .

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

$WebURL ="https://intranet.crescent.com/sites/operations/us"

$web =  Get-SPWeb $SiteURL
$web.RevertAllDocumentContentStreams();
$web.Update()

$SiteURL ="https://intranet.crescent.com"

#Revert all webs to site definition
Get-SPSite $SiteURL | Get-SPWeb | foreach-object {
 $_.RevertAllDocumentContentStreams()
 Write-Debug "Site Resetted: $($web.Url)"
 } 

 Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#Variables for Web and File URLs
$WebURL ="http://intranet.crescent.com/support/"
$FileURL ="http://intranet.crescent.com/support/T1Support/Reports/ServiceTickets.xlsx" 

#Get Web and File Objects
$web = Get-SPWeb $WebURL
$File = $web.GetFile($FileURL)

#Check if File is Checked-out
if ($File.CheckOutType -ne "None")
 {
    Write-host "File is Checked Out to user: " $File.CheckedOutByUser.LoginName
    Write-host "Checked Out Type: " $File.CheckOutType
    Write-host "Checked Out On: "  $File.CheckedOutDate

    #To Release from Checkout, Ask the checked out user to Checkin
    #$File.Checkin("Checked in by Administrator")
    #Write-host "File has been Checked-In"
 }

 #Check if File is locked
 if ($File.LockId -ne $null)
 {
     Write-host "File is Loked out by:" $File.LockedByUser.LoginName
     Write-host "File Lock Type: "$file.LockType
     Write-host "File Locked On: "$file.LockedDate
     Write-host "File Lock Expires on: "$file.LockExpires

     #To Release the lock, use:
     #$File.ReleaseLock($File.LockId)
     #Write-host "Released the lock!" 
 }

How to Create Federated Search in SharePoint 2013 :

1. Create a Result source for federated content source
2. Create a query rule to include federated search results in SharePoint search results page

• Go to Central Administration >>  Application Management >> Manage service applications >> Select your  Search Service Application.
• You'll be presented with the Search Administration page.

• To start with federated search in SharePoint 2013, Navigate to Site settings >> Click on  "Result Sources" link under Search group.
• From the Manage result sources page, click "New Result Source" link.
• Enter the name for your result source:
•  I've entered "Bing Search Results" 
• Choose the Protocol as "OpenSearch 1.0/1.1
• Source URL - This is important. Source URL specifies our source for Federation.
• For Bing - Enter: http://www.bing.com/search?q={?searchterms}&format=rss&Market=en-US
• For Twitter - http://search.twitter.com/search.atom?q={searchTerms}
• Specify the credentials. I've specified "Anonymous". Click on "Save" button to create result source.

• From site settings page, Click on "Query Rules" link this time.
• Choose Result source as "Local SharePoint Results" and click on "New Query Rule" link.
• In "Add Query Rule" page, Give a name to your query rule. Click on "Remove Condition" link under Query conditions. In "Actions" section, click on "Add Result Block" link, You'll be prompted with the "Add Result Block" dialog box.
• In Add Result block page:
• Enter the title for your result block. I've entered "Bing Search Results for "{subjectTerms}" 
• In Query section, Choose the search source as "Bing Search Results" we created in step 1.
• Choose Number of items to show in search results.
• Under Settings, Choose "This block is always shown above core results"option. Click "Ok" to create a result block.
• Click Save to save your query rule.

1. Go to your library, Click on Library settings.
2. In the settings page, under users and permissions, click on "Permissions for this document library"
3. Click on "Delete Unique permissions" button in ribbon from Inheritance group.

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#Variables for Web URL, List Name
$WebURL ="https://intranet.crescent.com/marketing"

#get the list object
$web = Get-SPWeb $WebURL

# Check if web has Unique permission - Root webs always uses Unique permission
if ( ($web.HasUniqueRoleAssignments) -and ($web.IsRootWeb -eq $false ) )
 {
      #Reset broken inheritance
      $web.ResetRoleInheritance()
      Write-host "Broken Inheritance Reset on web:" $web.URL
 }

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#Variables for Web URL, List Name
$WebURL ="https://intranet.crescent.com/marketing/"
$ListName ="Invoices" 

#get the list object
$List = (Get-SPweb $WebURL).lists.TryGetList($ListName)

# If List Exists with Unique permission
if ( ($list -ne $null) -and ($list.HasUniqueRoleAssignments) )
 {
      #Reset broken list inheritance
      $list.ResetRoleInheritance()
      Write-host "Broken Inheritance Reset on List:" $list.Title
 }

<#To Reset Folder level inheritance, Use:
 foreach ($folder in $list.Folders) 
   {  
        if ($folder.HasUniqueRoleAssignments) 
        { 
            Write-Host "Resetting Folder inheritance at:" $folder.Url   
            $folder.ResetRoleInheritance()  
            $folder.Update() 
        } 
   }
 #>

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#Variable for Web URL
$WebURL ="https://intranet.crescent.com/marketing/"

#get Web object
$Web = Get-SPWeb $WebURL

#Get Lists with Unique permissions - Exclude Hidden lists
$ListColl =  $web.lists | Where-Object  {  ($_.HasUniqueRoleAssignments -eq $true)  -and ($_.hidden -eq $false) }

#Enumerate through each list and reset permission inheritance
foreach($list in $ListColl) #if($list) #Exists
 {
      #Reset list inheritance
      $list.ResetRoleInheritance()
      Write-host "Broken Inheritance Reset on List:" $list.Title
 }

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#Variables for Web URL, List Name
$WebURL ="https://intranet.crescent.com/marketing/"
$ListName ="Invoices" 

#Get the list items with Unique permissions
$ListItems = (Get-SPweb $WebURL).lists.TryGetList($ListName).Items | Where {$_.HasUniqueRoleAssignments}

# If List Exists with Unique permission
Foreach($ListItem in $ListItems)
 {
      #Reset broken list item inheritance
       $ListItem.ResetRoleInheritance()
      Write-host "Broken Inheritance Reset on List Item:" $ListItem.URL
 }

(Get-SPweb "https://intranet.crescent.com/marketing/").Lists["Invoices"].Items | Foreach-Object{ $_.ResetRoleInheritance() }

• Break Inheritance in SharePoint using PowerShell
• SharePoint unique permissions report

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue

#### rename sharepoint service application proxy### 
#Get the Service Application proxy
$Proxy = Get-SPServiceApplicationProxy | ? {$_.Name -eq "Search SSA Proxy"} 
#Rename Service application proxy
$Proxy.Name = "Search Service Application Proxy"  
$Proxy.Update()

###sharepoint 2013 rename service application###
#Get Service application
$Service = Get-SPServiceApplication -Name "Search Service App"
#Rename Service application
$Service.Name = "Search Service Application" 
$Service.Update() 

rename SharePoint service application

• Site Settings >> Change the Look 
• Select the new look to apply
• Click on "Try it out" link >> SharePoint will give you the preview of your SharePoint site with the new theme 
• Once you confirm by "Yes, Keep it", the new look and feel is applied to your SharePoint 2013 site.

Create composed look in SharePoint 2013:

• Master Page - AKA - Site Layout
• Color palette - AKA - Theme
• Font scheme  - Optional
• Background image  - Optional

<s:color name="FooterBackground" value="7F333333" />

The "Composed Looks" List:

• Site Settings > Composed looks under the Web Designer Galleries heading 
• Click on add new item.  
• From there you simply fill out the form giving the title, name and URLs to your custom Master Page (which may have custom CSS files linked inside) and other artifacts.

• Open Visual Studio 2013 (or 2012) >> Click on File >> New >> Project
• Choose: Office/SharePoint >> SharePoint 2013 - Empty Project. Name your solution and click on "OK"
• Enter the site for debugging and choose "Farm Solution" (Doesn't matters even its a sandboxed solution too!) and click on "Finish" button. wait for Visual studio to create project structure.
• Now, in Visual studio, Right click the "Project" node from solution explorer window, choose Add >> New Item menu.
• Choose "Module"and give it a name. Click on Add.
• This module brings a feature "feature1" and "Sample.txt" File by default. Remove the sample.txt from the solution and rename Feature1 to something meaningful, I've made it as same as my project name - SignInAsDiffUser
• Update the elements.xml file with the below code

  <?xml version="1.0" encoding="utf-8"?>
  <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <CustomAction
          Id="LoginAsDifferentUser"
          GroupId="PersonalActions"
          Location="Microsoft.SharePoint.StandardMenu"
          Sequence="1000"
          Title="Sign in as Different User">
  <UrlAction Url="/_layouts/closeConnection.aspx?loginasanotheruser=true"/>
  </CustomAction>
  </Elements> 

• Now, Right click the Feature, "SignInAsDiffUser" from solution explorer and choose "View Designer"menu item.
• In the feature designer page, Give a name and description to your feature. Set the scope for the feature, I've made it : Site, So that it will be applicable for the entire site collection. Make sure the module we've created is included in the feature.
• Right click the solution in visual studio, choose Deploy. This will automatically Build,deploy and active your feature. Go to site collection features and make sure "Sign in As different User"feature is activated.

• Farm administrator's group
• Central administration web application policies
• Site collection administrators 
• Scans all site collections and sub-sites with unique permissions in which user has access.
• Scans all lists and libraries with unique permissions in which user has access.
• Scans all folders and list Items which has permissions in the site in which user has access.

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Function to retrieve Permission data
Function Get-PermissionInfo([String]$UserID, [Microsoft.SharePoint.SPSecurableObject]$Object)
{
 #Object Array to hold Permission data
    $PermissionDataCollection = @()

 #Determine the given Object type and Get URL of it
    switch($Object.GetType().FullName)
 {
  "Microsoft.SharePoint.SPWeb"  { $ObjectType = "Site" ; $ObjectURL = $Object.URL }
  "Microsoft.SharePoint.SPListItem" 
  { 
   if($Object.Folder -ne $null)
   {
     $ObjectType = "Folder" ; $ObjectURL = "$($Object.Web.Url)/$($Object.Url)" 
   }
   else
   {
    $ObjectType = "List Item"; $ObjectURL = "$($Object.Web.Url)/$($Object.Url)" 
   }
  }
  #Microsoft.SharePoint.SPList, Microsoft.SharePoint.SPDocumentLibrary, "Microsoft.SharePoint.SPPictureLibrary",etc
  default { $ObjectType = "List/Library"; $ObjectURL = "$($Object.ParentWeb.Url)/$($Object.RootFolder.URL)" }
 }

 #Get Permissions of the user on given object - Such as: Web, List, Folder, ListItem
 $UserPermissionInfo = $Object.GetUserEffectivePermissionInfo($UserID)
 #Iterate through each permission and get the details
 foreach($UserRoleAssignment in $UserPermissionInfo.RoleAssignments)
 {
  #Get all permission levels assigned to User account directly or via SharePOint Group
  $UserPermissions=@()
        foreach ($UserRoleDefinition in $UserRoleAssignment.RoleDefinitionBindings)
        {
   #Exclude "Limited Accesses"
   if($UserRoleDefinition.Name -ne "Limited Access")
   {
          $UserPermissions += $UserRoleDefinition.Name
   }
        }

  #Determine Permissions granted directly or through SharePoint Group
  if($UserPermissions)
  {
   if($UserRoleAssignment.Member -is [Microsoft.SharePoint.SPGroup])   
   {
     $PermissionType = "Member of SharePoint Group: " + $UserRoleAssignment.Member.Name     
   }
   else
   {
    $PermissionType = "Direct Permission"
   }
   $UserPermissions = $UserPermissions -join ";"  

   #Create an object to hold storage data
         $PermissionData = New-Object PSObject
         $PermissionData | Add-Member -type NoteProperty -name "Object" -value $ObjectType
   $PermissionData | Add-Member -type NoteProperty -name "Title" -value $Object.Title
         $PermissionData | Add-Member -type NoteProperty -name "URL" -value $ObjectURL  
   $PermissionData | Add-Member -type NoteProperty -name "Permission Type" -value $PermissionType
   $PermissionData | Add-Member -type NoteProperty -name "Permissions" -value $UserPermissions
   $PermissionDataCollection += $PermissionData
  }   
 } 
 Return $PermissionDataCollection
}

#Function to Generate Permission Report
Function Generate-PermissionReport($UserID, $WebAppURL, $ReportPath)
{
    #Output Report location, delete the file, If already exist!
    if (Test-Path $ReportPath)
     {
        Remove-Item $ReportPath
     }

   #Write Output Report CSV File Headers
  "Object, Title, URL, Permission Type, Permissions" | out-file $ReportPath

 ###Check Whether the Search Users is a Farm Administrator ###
 Write-host "Scanning Farm Administrators..." 
   #Get the SharePoint Central Administration site
   $AdminWebApp = Get-SPwebapplication -includecentraladministration | where {$_.IsAdministrationWebApplication}
    $AdminSite = Get-SPWeb $AdminWebApp.Url
    $AdminGroupName = $AdminSite.AssociatedOwnerGroup
    $FarmAdminGroup = $AdminSite.SiteGroups[$AdminGroupName]

 #enumerate in farm adminidtrators groups
    foreach ($user in $FarmAdminGroup.users)
    {
     if($user.LoginName.Endswith($UserID,1)) #1 to Ignore Case
     {
       "Farm, $($AdminSite.Title), $($AdminWebApp.URL), Farm Administrators Group, Farm Administrator" | Out-File $ReportPath -Append
     }     
    }

 ### Check Web Application User Policies ###
 Write-host "Scanning Web Application Policies..." 
  $WebApp = Get-SPWebApplication $WebAppURL

  foreach ($Policy in $WebApp.Policies)
  {
      #Check if the search users is member of the group
     if($Policy.UserName.EndsWith($UserID,1))
       {
       #Write-Host $Policy.UserName
        $PolicyRoles=@()
       foreach($Role in $Policy.PolicyRoleBindings)
       {
        $PolicyRoles+= $Role.Name +";"
       }
   #Send Data to CSV File
      "Web Application, $($WebApp.Name), $($WebApp.URL), Web Application Policy, $($PolicyRoles)" | Out-File $ReportPath -Append
   }
  }

 #Convert UserID Into Claims format - If WebApp is claims based! Domain\User to i:0#.w|Domain\User
    if($WebApp.UseClaimsAuthentication)
    {
        $ClaimsUserID = (New-SPClaimsPrincipal -identity $UserID -identitytype 1).ToEncodedString()
    }

 #Get all Site collections of given web app
 $SiteCollections = Get-SPSite -WebApplication $WebAppURL -Limit All

 #Loop through all site collections 
    foreach($Site in $SiteCollections)
    {
     Write-host "Scanning Site Collection:" $site.Url
  ###Check Whether the User is a Site Collection Administrator
     foreach($SiteCollAdmin in $Site.RootWeb.SiteAdministrators)
        {
      if($SiteCollAdmin.LoginName.EndsWith($ClaimsUserID,1))
      {
       "Site Collection, $($Site.RootWeb.Title), $($Site.RootWeb.Url), Site Collection Administrators Group, Site Collection Administrator" | Out-File $ReportPath -Append
      }     
    }

  #Get all webs
  $WebsCollection = $Site.AllWebs
  #Loop throuh each Site (web)
  foreach($Web in $WebsCollection)
  {
       if($Web.HasUniqueRoleAssignments -eq $True)
             {
     Write-host "Scanning Site:" $Web.Url

     #Get Permissions of the user on Web
     $WebPermissions = Get-PermissionInfo $ClaimsUserID $Web

     #Export Web permission data to CSV file - Append
     $WebPermissions |  Export-csv $ReportPath  -notypeinformation -Append 
    } 

    #Check Lists with Unique Permissions
    Write-host "Scanning Lists on $($web.url)..."
    foreach($List in $web.Lists)
    {
              if($List.HasUniqueRoleAssignments -eq $True -and ($List.Hidden -eq $false))
                 {
      #Get Permissions of the user on list
                        $ListPermissions = Get-PermissionInfo $ClaimsUserID $List

      #Export Web permission data to CSV file - Append
      $ListPermissions |  Export-csv $ReportPath -notypeinformation -Append       
     }

     #Check Folders with Unique Permissions
     $UniqueFolders = $List.Folders | where { $_.HasUniqueRoleAssignments -eq $True }                    
                    #Get Folder permissions
                    foreach($folder in $UniqueFolders)
        {
                        $FolderPermissions = Get-PermissionInfo $ClaimsUserID $folder

      #Export Folder permission data to CSV file - Append
      $FolderPermissions |  Export-csv $ReportPath -notypeinformation -Append    
                    }

     #Check List Items with Unique Permissions
     $UniqueItems = $List.Items | where { $_.HasUniqueRoleAssignments -eq $True }
                    #Get Item level permissions
                    foreach($item in $UniqueItems)
        {
                        $ItemPermissions = Get-PermissionInfo $ClaimsUserID $Item

      #Export List Items permission data to CSV file - Append
      $ItemPermissions |  Export-csv $ReportPath -notypeinformation -Append    
                    }
    }
  }
 }
 Write-Host Permission Report Generated successfully!
}

#Input Variables
$WebAppURL = "http://intranet.crescent.com"
$Userid ="Crescent\Salaudeen" 
$ReportPath = "D:\Reports\PermissionRpt.csv"

#Call the function to generate user access report
Generate-PermissionReport $Userid $WebAppURL $ReportPath

• SharePoint Users and Groups Permission Report
• Unique Permissions Report in SharePoint
• SharePoint Site Collection Owners Report
• Site Collection Administrators Report for All SharePoint Sites
• Export SharePoint Users and Groups to Excel using PowerShell
• SharePoint Permission Levels Report

• Documentation Toolkit for SharePoint - SPDocKit 
• SharePoint Management tool from Sharegate 
• SharePoint Permission Report from BoostSolutions 
• Metavis Security Manager for SharePoint 
• SharePoint Permissions Management
• ControlPoint from Metalogix

1. You can Edit Managed Metadata columns (Still Rich text columns are not editable in Quick Edit! content type change can't be done from quick edit!!)
2. It works just fine in other browsers ( I tested with Firefox and Chrome), where SharePoint 2010 Datasheet view was working ONLY with internet explorer 32 bit version.
3.  No more Active-X control dependencies. Quick edit doesn't need Office access run time engine now!
4. It supports Filters now! Remember the pain of losing filters on datasheet views in those old days?

1. Check Quick Edit is Enabled: To enable/disable quick edit in SharePoint 2013, you need to navigate to: List Settings >> Advanced settings page >> Scroll down and Under quick edit option,  choose "Yes" and then click OK.
2. Remove the Group By: If you have grouping enabled in your Views, You got to remove it! If you group list or library items in SharePoint 2013, quick edit (Datasheet View) option is disabled. remove "Group By" selection by setting it to none.
3. Change the View style to default: Changing view style to "Shaded", "Newsletter" or something else disables Quick Edit. Change it to "default" in view settings. https://support.microsoft.com/kb/2876824
4. Enable 'Allow individual item" check boxes: In view settings make sure, "Allow Individual Items Check boxes" is enabled.   
5. If you are in datasheet view already- If your current view is "Datasheet view" then quick edit is disabled (obviously!). 
6. SharePoint View definition XML uses an attribute "<JSLink>clienttemplates.js</JSLink>". During a migration, I had to add this to an existing view using SharePoint designer and verified Quick Edit works as expected.
7. Last but not least: Try creating a new view using "Standard View".

1. Get your current farm patch level
2. Download SharePoint 2013 service pack/CU/Hot-fix
3. Install binaries on SharePoint Servers
4. Run the SharePoint Products Configuration Wizard
5. Verify the updated build number of your SharePoint farm.

Step 1: Get SharePoint 2013 Patch Level

• Go to your SharePoint 20103 Central Administration site. 
• From the Central Administration, navigate to System Settings >> Manage Servers in this Farm
• From the Servers in this Farm page, under the Farm information section, you will see the SharePoint Farm Build Version.

• Browse to the location where you downloaded patches. 
• Start the patching process by double clicking the installers (you may have to extract the downloaded binaries!). Accept the license agreement and click on "Continue".

•  You should see the installation progress window. You may asked to reboot the server to complete patch installation.

•  Wait for the installation is complete message.

• Go to start >> Search "SharePoint products configuration wizard" and run PSConfig wizard as administrator. Click on Next to continue.

• You will get a warning message saying few services will be restarted during this upgrade process. Click Yes and then Click Next

•  SharePoint products configuration wizard will run through the upgrade process. Wait for the wizard to complete.

•  When the wizard is completed, click Finish.

• Go to your SharePoint 20103 Central Administration site. 
• From the Central Administration, navigate to System Settings >> Manage Servers in this Farm
• From the Servers in this Farm page, under the Farm information section, you will see the Configuration Database Version.

• Hotfix/patch is a update addressing a specific problem/bug/security issue. On Demand - normally not for everyone, you should only apply the patch if you're having the specific problem it addresses. Microsoft publishes a corresponding KB article for every hotfix that is released for every Microsoft product. 
• Cumulative Updates  - As their name suggest, they are cumulative in content so they include a collection previously released hotfixes to date. Hotfixes and CUs are not always publicly released.  You'll get a link to download these hotfixes and CUs on requesting via Microsoft site. 
• Service pack is a collection of CUs (and patches). It rolls together all patches that have come along over a given period of time. - Usually contains new features and available to public.

• Go to "Site Settings" of your root site collection >> Click on "Site collection features" under site collection administration
• Click on "Activate" button next to "SharePoint Server Publishing Infrastructure".
• Activate "SharePoint Server Publishing Infrastructure" from site features via "Site Setting" >> Click on "Manage site features" and activate SharePoint Server Publishing Infrastructure.

<!--SPM:<SharePoint:CssRegistration Name="Themable/corev15.css" runat="server"/>-->

<!--SPM:<SharePoint:CssRegistration Name="http://YOUR-SITE-COLLECTION-URL/SiteAssets/YOUR-CSS-FILE.css" runat="server" After="corev15.css" />-->

<!--SPM:<SharePoint:CssRegistration name="&lt;% $SPUrl:~site/_catalogs/masterpage/YOURFOLDER/YOUR-style-Sheet.css %&gt;" runat="server" after="SharepointCssFile" />-->

 /*** Top Navigaion Menu Items container DIV ***/
.ms-core-listMenu-horizontalBox {
    background-color: #47A4D3;
}  

 /*** Top Navigaion Static Menu Items ***/ 
.ms-core-listMenu-horizontalBox li.static {
    border: 1px solid transparent;
    background: url("/_layouts/Images/selbg.png") repeat-x left top;
}

 /*** Top Navigaion Static Menu Item Links  ***/ 
.ms-core-listMenu-horizontalBox li.static > .ms-core-listMenu-item {
    color: #21374C;
    white-space: nowrap;
    border: 1px solid transparent;
    padding: 10px;
    padding-left: 20px;
    margin-right: 1px;
}  

  /* Top Navigation static Menu Item Links Hover Style  */
.ms-core-listMenu-horizontalBox li.static > .ms-core-listMenu-item:hover {
    background: url("/_layouts/Images/selbg.png") repeat-x left top;
    background-color: #0A85C4;
    color: #fff;
    text-decoration: none;
}

 /*** Top Navigaion Static Menu Selected ***/
.ms-core-listMenu-horizontalBox li.selected a.selected {
     /* Glass Effect Shade Image */
    background: url("/_layouts/Images/selbg.png") repeat-x left top;
 /* Glass Effect Shade Image */
    background-color: #0A85C4;
    color: #fff;
    text-decoration: none;
    border: 1px #134072 solid;
    padding: 10px 10px;
    margin: 1px;
}  

 /*** Sub-Menu/Flyover/Dynamic Menu Container ***/
ul.dynamic {
    background-color: #D5E4F2;
    border: 1px solid #000;
    padding: 1px;
    margin-top: 5px;
}  

/***  Sub-Menu Items (HyperLinks) Style ***/
ul.dynamic .ms-core-listMenu-item {
    background-color: #f7f7f7;
    padding: 10px 20px 10px 20px;
    white-space: nowrap;
}  


/*** Sub-Menu Items (HyperLinks) Hover Style ***/
ul.dynamic .ms-core-listMenu-item:hover {
    background-color: #61CBFD;
    color: #FFF;
}  

 /** Hide "Edit Links" ***/
.ms-listMenu-editLink {
    display: none !important;
}