•  Navigate to your desired page
• Click on "Page" tab, Click on "Make Homepage" button from the ribbon.
  
• Confirm to the "If you make this page the home page for this site, users will no longer be able to see the old site home page. Do you want to set this page as this site's home page?" message box.
  
• Done!

• Navigate to site settings >> Click on "Welcome Page"
  link under "Look and Feel" section
• Enter the home page URL either directly or by Clicking on "Browse" button and choosing the right page.
  
• Click on "Ok" to save your changes.

• Navigate to "Site Pages" library, or any other library where your target page exists
• Right click on the page and choose "Set as Home page" menu item from the context menu. Alternatively, you can use the Ribbon button also as highlighted.

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Variables
$WebURL="http://intranet.crescent.com"
$HomePageURL="SitePages/default.aspx"

#Get the Web
$web = Get-SPWeb $WebURL

#Change Welcome page
$RootFolder = $Web.RootFolder
$RootFolder.WelcomePage = $HomePageURL
$RootFolder.Update()

$web.Dispose() 

• Storage space allocated - Storage used, warning and maximum levels
• Site collection GUIDs
• Site collection database names
• Primary and Secondary Owners

Stsadm -o EnumSites -url http://Sharepoint-web-app-URL 

Stsadm -o EnumSites -url http://Sharepoint-web-app-URL > SitesInfo.xml 

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Variables
$SiteURL="http://intranet.crescent.com/" 
$ListName="Change Request"
$ColumnName="Activity Status"

#Get Internal Name of the columns
$web = Get-SPWeb $SiteURL

#Get the list
$list = $web.Lists.TryGetList($ListName)

if($List -ne $null)
{
    #Get the column 
    $column = $list.Fields[$ColumnName]

    if($column -ne $null)
    {
        #Reset column properties to allow delete
        $column.Hidden = $false
        $column.ReadOnlyField = $false
        $column.Sealed = $false
        $column.Update()

        #Delete the column from list
        $list.Fields.Delete($column)
        write-host "Column has been deleted!" -f Green
    }
    else
     {
        write-host "Specified column name not found!" -ForegroundColor Red
     }
}

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Custom Function to delete a column with PowerShell
Function Remove-Column($WebURL, $ListName, $ColumnName)
{

    #Get Internal Name of the columns
    $web = Get-SPWeb $WebURL

    #Get the list
    $list = $web.Lists.TryGetList($ListName)

    if($List -ne $null)
    {
        #Get the column 
        $column = $list.Fields[$ColumnName]

        if($column -ne $null)
        {
            #Reset column properties to allow delete
            $column.Hidden = $false
            $column.ReadOnlyField = $false
            $column.Sealed = $false
            $column.Update()

            #Delete the column from list
            $list.Fields.Delete($column)
            write-host "Column '$ColumnName' has been deleted!" -f Green
        }
        else
        {
            write-host "Specified column name not found!" -ForegroundColor Red
        }
    }
    else
    {
        write-host "Specified List is not found!" -ForegroundColor Red
    }
}

#Variables
$WebURL="http://intranet.crescent.com" 
$ListName="Change Request"

#Array to hold column titles
$ColumnNames=@("Change Type","Approvers","Proposed Date and Time")

#Process each column
$ColumnNames | foreach {

    #Call the function to remove column
    Remove-Column $WebURL $ListName $_
}

#Get Date
$ReportDate = Get-Date -format "MM-dd-yyyy"

#Configuration Variables for E-mail
$SmtpServer = "smtp.crescent.com" #or IP Address such as "10.125.150.250"
$EmailFrom = "Site Delete Script <SiteDeleteScript@Crescent.com>"
$EmailTo = "SharePointSupport@Crescent.com.com"
$EmailSubject = "Site Delete Script - Daily Report on: "+$ReportDate

#HTML Template
$EmailBody = @"

<table style="width: 68%" style="border-collapse: collapse; border: 1px solid #008080;">
<tr>
<td colspan="2" bgcolor="#008080" style="color: #FFFFFF; font-size: large; height: 35px;"> 
        Site Delete Script - Daily Report on VarReportDate  
</td>
</tr>
<tr style="border-bottom-style: solid; border-bottom-width: 1px; padding-bottom: 1px">
<td style="width: 201px; height: 35px">&nbsp; Number of requests Approved</td>
<td style="text-align: center; height: 35px; width: 233px;">
<b>VarApproved</b></td>
</tr>
<tr style="height: 39px; border: 1px solid #008080">
<td style="width: 201px; height: 39px">&nbsp; Number of requests Rejected</td>
<td style="text-align: center; height: 39px; width: 233px;">
<b>VarRejected</b></td>
</tr>
</table>

"@

#Get Values for Approved & Rejected variables
$ApprovedCount= Get-ApprovedReq()
$RejectedCount= Get-RejectedReq()

#Replace the Variables VarApproved, VarRejected and VarReportDate
$EmailBody= $EmailBody.Replace("VarApproved",$ApprovedCount)
$EmailBody= $EmailBody.Replace("VarRejected",$RejectedCount)
$EmailBody= $EmailBody.Replace("VarReportDate",$ReportDate)

#Send E-mail from PowerShell script
Send-MailMessage -To $EmailTo -From $EmailFrom -Subject $EmailSubject -Body $EmailBody -BodyAsHtml -SmtpServer $SmtpServer

#send-mailmessage in powershell with attachment
$attachment = "D:\Reports\SiteDeleteRpt.csv"

#send-mailmessage in powershell multiple attachments
$attachment = "D:\Reports\SiteDeleteRpt1.csv","D:\Reports\SiteDeleteRpt2.csv"

Send-MailMessage -To $EmailTo -From $EmailFrom -Subject $EmailSubject -Body $EmailBody -BodyAsHTML -Attachments $attachment -SmtpServer $SmtpServer 

$EmailTo = "marcm@crescent.com", "victor <victor@crescent.com>"
#or use:
$recipients = @("Marc M <marcm@crescent.com>", "victor <victor@crescent.com>")

• Open your SharePoint 2013 site in SharePoint designer 2013. Navigate to "Master Pages" folder
• Right click on your master page (by default: Seattle.master) and choose "Edit file in Advanced Mode"
• Locate the text: id="DeltaSuiteLinks" and add the below code just below the DeltaSuiteLinks tag to add link to suite bar of SharePoint 2013
  

  <span id="CustomerSupport" class="ms-core-suiteLink">
  <a class="ms-core-suiteLink-a" href="http://support.crescent.com">
  <asp:Label ID="lblCS" runat="server" Text="Customer Support"></asp:Label>
  </a>
  </span>

• Save and close SharePoint designer. This adds link to SharePoint 2013 suite bar and you should see the new link as below:

<script type="text/javascript" src="http://code.jquery.com/jquery-1.2.6.min.js"></script>
<script type="text/javascript">
 $(document).ready(function() {
 //Define new links
  var newLinks = "<li class='ms-core-suiteLink'> \
<a class='ms-core-suiteLink-a' href='http://extranet.crescent.com'>Extranet</a> \
</li> \
<li class='ms-core-suiteLink'> \
<a class='ms-core-suiteLink-a' href='http://support.crescent.com'>Customer Support</a> \
</li> ";

  $('.ms-core-deltaSuiteLinks').prepend(newLinks);
  alert('works');
  });

</script>

• Navigate to SharePoint 2013 Central Administration site
• Go to Monitoring >> Check Job status
• Click on "Job History" link from left navigation
  
• Under the "View" filter, choose "Job Definition". You'll find an cascading filter appears as "Job Definition" once you choose View filter as "Job definition". You can also choose options such as: Service, Web Application, Server.
• Click on the job definition filter to "change job definition"
  
• Pick the relevant timer job definition. E.g. Audit Log Trimming, Immediate Alerts, etc.
  
• Now, you'll find the jobs history for selected timer job as below.
  

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

# Variables
$WebAppURL = "http://intranet.crescent.com" 
$StartTime = "09/26/2015 01:00:00 AM"  # mm/dd/yyyy hh:mm:ss
$EndTime = "09/26/2015 01:30:00 AM"

#Get all timer jobs associated with a web application
$WebApp = Get-SPWebApplication $WebAppURL

$Results = $WebApp.JobHistoryEntries | 
      where { ($_.StartTime -ge  $StartTime) -and ($_.EndTime -le $EndTime) } | 
          Select JobDefinitionTitle,WebApplicationName,ServerName,Status,StartTime,EndTime

#Send results to Grid view    
$Results | Out-GridView

# Variables
$StartTime = "09/26/2015 01:00:00 AM"  # mm/dd/yyyy hh:mm:ss
$EndTime = "09/26/2015 01:30:00 AM"
$TimerJobName = "Immediate Alerts"

#To Get Yesterday's use:
#$StartDateTime = (Get-Date).AddDays(-1).ToString('MM-dd-yyyy') + " 00:00:00" 
#$EndDateTime   = (Get-Date).AddDays(-1).ToString('MM-dd-yyyy') + " 23:59:59"

#Get the specific Timer job
$Timerjob = Get-SPTimerJob | where { $_.DisplayName -eq $TimerJobName } 

#Get all timer job history from the web application
$Results = $Timerjob.HistoryEntries  | 
      where { ($_.StartTime -ge  $StartTime) -and ($_.EndTime -le $EndTime) } | 
          Select WebApplicationName,ServerName,Status,StartTime,EndTime

#Send results to Grid view    
$Results | Out-GridView

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

# Variables
$WebAppURL = "http://intranet.crescent.com" 
$StartTime = "01/01/2016 01:00:00 AM"  # mm/dd/yyyy hh:mm:ss
$EndTime = "05/01/2016 01:30:00 AM"
$OutPutFile="D:\FailedJobHistoryRpt.csv"

#Get all timer jobs associated with a web application
$WebApp = Get-SPWebApplication $WebAppURL

#Get all Failed Timer jobs in between given Time
$Results = $WebApp.JobHistoryEntries | Where {($_.StartTime -ge $StartTime) -and ($_.EndTime -le $EndTime) -and ($_.Status -ne 'Succeeded')} 

#Export to CSV
$Results | Export-Csv $OutPutFile –NoType

write-host "Failed Timer jobs history Exported to CSV!" -F Green

1. Document Management System
2. File Shares
3. Content Management System
4. Enterprise Search Centre (Search site to index and search all sites, including non-SharePoint sites of the company)
5. Enterprise Social Networking Site - Yammer!
6. Corporate News Portal-Intranet-Extranet-Internet web Sites
7. Project Management tool (with or without project server integration)
8. Team Collaboration work space
9. Employee Self-Service portal - Employee requests center
10. Business process Automation/Workflows – BPM E.g. Expense Reimbursement, Travel Request
11. Event Management - Party!
12. Knowledge Base - KB sites
13. Issue/bug Tracker system
14. Reporting Tool - SSRS!
15. Task Management
16. Calendar Sharing - Corporate Calendars with important events and schedules
17. Help desk management - Ticketing system
18. Incident/Change Management - as part of process!
19. Learning / Training Management, Competency management, Training Scheduling and Materials
20. Innovation Management
21. Blog Sites - Wiki sites
22. Community Portal
23. Electronic Forms to capture and process data - InfoPath!
24. Performance/Goal tracker tool
25. Organizational Browser – People directory!
26. Personal sites- My site!
27. Business Performance Reporting - MIS
28. Case Management
29. Inventory Tracking
30. Competitive Analysis Site
31. Discussion Forums
32. Invoice Management
33. Request/ Change Management
34. Employee Activities Site - Associations– E.g. Sports League, Toast Master
35. Request for Proposal
36. Process Management, Policies and Procedure Templates
37. Room and Equipment Reservations
38. Physical Asset Tracking and Management
39. Job Requisition and Interview Management
40. Contacts Management
41. Leave Request and Vacation Schedules
42. Records / Document Life cycle management
43. Business Intelligence Tool
44. Surveys
45. Meeting Management
46. Dashboards & Scorecards Solutions
47. Visio Process Repository
48. Digital Assets Management - Image management
49. Vendor & Customer management
50. Portfolio management

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Variables for Processing
$SiteURL = "http://projects.crescent.com"
$ListOneName ="Team One Tasks"
$ListTwoName ="Tasks Two Tasks"
$ColumnToCompare="Task Name"

#Get site and List objects
$Web = Get-SPWeb $SiteURL
$ListOne = $web.lists[$ListOneName]
$ListTwo = $web.lists[$ListTwoName]

#Fetch specifc Column Values from each lists to compare
$ListOneValues = @()
$ListTwoValues = @()

$ListOne.Items| foreach { $ListOneValues+= $_[$ColumnToCompare] }
$ListTwo.Items | foreach { $ListTwoValues+= $_[$ColumnToCompare] }

#Compare
Compare-Object $ListOneValues $ListTwoValues # -PassThru

• <= - Difference is in Left side - first object we compare
• => - Difference is in the Right side - Second object in the comparison

1. To make sure that the profile file is created, run:
   

   #Check if the profile file exists already
   if (test-path $profile) 
   { 
       write-host "profile file already exists at: $profile" 
   } 
   else
   {
       #Create the profile file
       New-Item -type file -path $profile -force 
       write-host "profile file has been created!" 
   }
   

   This script will create a new profile file, if it isn't created already! Your output will be something like:
2. Open the profile file you received from above script, Add the below line to it. (in my case, its: C:\Users\salaudeen\Documents\WindowsPowerShell\Micro
   soft.PowerShellISE_profile.ps1)
   

   Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

3. Save and close

• Go to Share 2013 Central Administration >> Monitoring 
• Click "Configure diagnostic logging" Under Reporting group
• Scroll down and set location for diagnostic log files. E.g. Set the log location to "D:\SPLogs\ULS"
• Click on "Ok" button to save your changes.

Set-SPDiagnosticConfig -LogLocation "D:\SPLogs\ULS"  

Set-SPDiagnosticConfig -LogLocation "D:\SPLogs\ULS" -DaysToKeepLogs 90 -LogMaxDiskSpaceUsageEnabled -LogDiskSpaceUsageGB 50

Set-SPUsageService -UsageLogLocation "D:\SPLogs\UsageLogs"

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

function Copy-SPAlerts($SourceWebUrl,$SourceList, $TargetWebUrl, $TargetList)
{
    #Get the source Web & List objects
    $SourceWeb = Get-SPWeb $SourceWebUrl
    $SourceList= $SourceWeb.lists.TryGetList($SourceList)   

    #Get the Target Web & List objects
    $TargetWeb = Get-SPWeb $TargetWebUrl
    $TargetList= $TargetWeb.lists.TryGetList($TargetList)   

    #Get All Alerts of the Source list
    $SourceAlertsColl = $SourceWeb.Alerts | Where-Object { ($_.List.Title -eq $SourceList.Title)}

    write-host Found $SourceAlertsColl.count alerts in the source List!

    if($SourceAlertsColl.Count -gt 0)
    {
        foreach ($SourceAlert in $SourceAlertsColl)
        {
            #Copy alerts from source to destination
            $alert = $TargetWeb.Alerts.Add()
            $alert.Title = $SourceAlert.Title
            $alert.AlertType = [Microsoft.SharePoint.SPAlertType]::List
            $alert.User = $SourceAlert.user 
            $alert.List = $TargetList
            $alert.DeliveryChannels = $SourceAlert.DeliveryChannels
            $alert.EventType =  $SourceAlert.EventType
            $alert.AlertFrequency = $SourceAlert.AlertFrequency
            $alert.Update()

            Write-Host "Copied Alert: $($SourceAlert.Title)" -foregroundcolor Green
        }
    }

}

#Variables
$SourceWebURL="http://intranet.crescent.com/PMO"
$SourceListName="Project Documents"
$TargetWebURL="http://intranet.crescent.com/sites/projects/BI/"
$TargetListName="Project Documents"

#Call the function to Copy Alerts
Copy-SPAlerts $SourceWebURL $SourceListName $TargetWebURL $TargetListName

• Create Everywhere -  Selected by default, this means any content created in source label will propagate to all target variations.  Sync will happen automatically
• Create Selectively -  Variation should be triggered manually 
• Recreate Deleted Target Page - Page should be re-created on a target variation site if the page was deleted 
• Update Target Page Web Parts - Source web part changes updated to the target sites 
• Notification - Email to label contact person

• Language: This setting defines SharePoint User interface elements of the variation site. Choices appear on the site template language drop-down depends on the language packs installed.
• Locale: Locale determines the language site based on your browser settings. It automatically redirects the browser from Variation home to target variation site. Locale helps in creating content in different languages. 
• Variation Home: is the location site where sub sites for all labels will be created
• Specify the Label Name for source variation and choose Publishing site template as "Publishing site". 
• Click "OK" button to create source variation.

• On "Configure Your Target Label" page, Select the Site Template Language. This depends on language packs you deployed to the SharePoint server. E.g Install Arabic language pack if you want to configure variation for Arabic & to choose Arabic as as a site template language! Select locale for target variation, and then click on "Continue" button.
  
• Run through the wizard to create a new target variation.  Choose Translation options.  I have  selected "Allow Human and Machine translation" and selected target language as "Arabic".
  
• Choose the Target label behavior. I've selected the option to push content updates automatically from source label to target label
  
• Name your Target label.
  
• Review and Click on Finish to complete target variation label creation.
  

• Navigate to SharePoint 2013 Central Administration
• Click on: Monitoring >> Review job definitions under Timer Jobs
• Pick your web application and click on "Variations Create Hierarchies Job Definition" timer job
• Click on "Run Now" to run this timer job.

1. Variations Create Hierarchies Job Definition: Creates all variation sites, lists and pages from the source variation site. It runs hourly.
2. Variations Propagate List Items Job Definition: Creates and updates list items on target variation Default, every 15 minutes.
3. Variations Propagate Page Job Definition: Creates and updates pages on target variation after approved. Runs every 15 minutes.
4. Variations Propagate Sites and Lists Job Definition: Creates variation sites and lists when the "Create Everywhere" option is enabled.  Runs on every 30 minutes.

• Site Settings >> Site Collection Administration >> Variation logs 

• Go to any custom list or library in source variation site
• Click on Variations Tab >> Click on Settings
• Select Variation labels (sites) to sync and click "Continue". You'll get "Your new variations are on the way" message.
  
• Once done, The particular list will be propagated on selected targets.

• Open the SharePoint 2013 Central Administration >> Manage Service applications
• Open User Profile Service application
• Click the "Stop" link under "Profile Synchronization Settings" section. 

• Go to your SharePoint site, Navigate to "Site Pages" library - Click on "Site Contents" link from Left navigation >> Click on "Site Pages" library. 
• Go to the "Files" tab, expand the New Document drop-down list and click on the "Web Part Page"
• Enter the Name for your new web part page, select the page Layout and Save Location, and then click on Create button.
• This creates a blank web part page in SharePoint 2013 as shown below. Now, We'll have to add some relevant web part to this web part page. Click on "Add a web Part" link shown in web part zones
• Select the relevant Web part to insert and click on "Add" button. I've added "Excel Web Access" web part.
• Configure web part properties. In my case, I've specified the excel sheet to display in the Excel web access web part.
• Click on "Stop Editing" button from ribbon to Save the page. That's all. We've added a new web part page in SharePoint 2013.

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Variables for processing
$WebURL="http://sharepoint.crescent.com/teams/marketing"
$NavigationTitle="Employee Profile"
$NavigationLink="https://peoplesoft.crescent.com/employee/profile.aspx"

#Get the Web
$Web= Get-SPWeb $WebURL

#Get Top Navigation
$TopNavigation = $Web.Navigation.TopNavigationBar
#For Quick Launch, Use: Navigation.QuickLaunch

#Create a New Top Navigation Node
$node = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode($NavigationTitle, $NavigationLink, $true)

#Add the Node
$TopNavigation.AddAsLast($node)

#Set the Target Property - Will work only when Publishing features is enabled
$node.Properties["Target"] = "_blank"

$node.Update

• Navigate to SharePoint 2013 Central Administration
• Click on "Monitoring" >> Review Timer job definitions
• Pick ""Search Health Monitoring - Trace Events" timer job by navigating to the next page in the list.
• Click on "Enable" button if its not enabled already. Once enabled, Click on "Run Now" button for the same timer job.
• Give it a minute to run. Once Ran, This issue should be gone away!

• Manageability: Any SharePoint site owner/admin can manage users on SharePoint groups within SharePoint (Self-Service!). But AD group creation and adding/removing users can be done only by AD administrators, unless delegated. So, to create new users or removing accounts you may have to wait for AD Admins/Help-desk! However, AD Groups Serves better in Centralized management, performance, Minimum administration efforts
• Scope: Since AD Groups are created globally, you can re-use them in any different SharePoint site collections (even in different systems like File Shares, Exchange, etc) . E.g. You may be having existing department wise AD groups created, say "Sales Team" and you can grant permission to any SharePoint site collection to the AD group. But SharePoint groups are scoped at site collection level and can't be re-used beyond that boundary. So, If you have an existing SharePoint group with 5000 users, you'll end-up recreating it in a different site collection (Although PowerShell can help!)
• Users from Multiple Authentication Sources: AD Group consists of users from AD, but SharePoint groups can be the combination of users from AD as well as non-Active directory authentication sources like SQL Server, LDAP, Live, Google, Facebook, Yahoo, etc.
• List All Usersof the Group - If you want to list users of the group, SharePoint groups can be listed with "Site Users" web part. But you can't do it with AD Groups - You can't look inside them from SharePoint (without custom solutions!) SharePoint considers AD group as a single user.
• Nested Groups: AD Groups can be nested, But SharePoint groups can't be added under any other SharePoint group. (However, you can add a AD Group inside SharePoint group!)
• Group Announcements: If you use SharePoint Group, There is no way to send alerts toall of them OOTB, But you can use E-mail enabled AD Group to subscribe to an Alert in SharePoint! 
• Audience targeting - does not work with AD groups, only with SP security groups!
• Orphaned Users - When you delete a user in AD, SharePoint groups can still hold them as orphan users!
• securable objects with unique permissions - When you have a requirement for dynamically changing security needs, SharePoint groups provides better flexibility.

#Web Application URL to delete
$WebAppURL="http://sharepoint.company.com" 

#sharepoint 2013 powershell delete web application
Remove-SPWebApplication -identity $WebAppURL -Confirm

#Web Application URL to delete
$WebAppURL="http://sharepoint.company.com" 

#Remove the web application and its databases & IIS Web Application
Remove-SPWebApplication -identity $WebAppURL -Confirm -DeleteIISSite -RemoveContentDatabases

#Web Application URL to delete
$WebAppURL="http://sharepoint.company.com" 

#sharepoint 2013 powershell delete web app
Get-SPWebApplication http://sitename | Remove-SPWebApplication -Zone "Internet" -Confirm

• Go to SharePoint 2013 Central Administration >> Service Applications 
• Pick your Search Service Application 
• In Search Administration page, Click on "Index Reset" link under crawling section of the left navigation menu.
• In the index reset page, click on "Reset Now" button to reset search index in SharePoint 2013.

• When you try to reset search index from Web UI, you get timeouts error on large index
• You may want to partially reset index for only certain content source

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Get Search service application
$ssa = Get-SPEnterpriseSearchServiceApplication

#Content Source Name
$ContentSourceName = "Crescent Portal"

#Get the content source 
$ContentSource = Get-SPEnterpriseSearchCrawlContentSource -Identity $ContentSourceName -SearchApplication $SSA 

#Get Each Start Address
$StartAddresses = $ContentSource.StartAddresses | ForEach-Object { $_.OriginalString } 

#Clear Indexed content starts with custom contnet source
$ContentSource.StartAddresses.Clear()

#Re-add the start address to content source
ForEach ($Address in $StartAddresses ){ $ContentSource.StartAddresses.Add($Address) }

(Get-SPEnterpriseSearchServiceApplication).reset($true, $true)