• Patch non-Distributed Cache servers -To find out what servers in your farm are running the Distributed Cache service, you can log into Central Administration, Manage Services on Server, click the dropdown to cycle through each server in the farm, and see if it has the Distributed Cache service running. Note: unlike other services, you will not see Distributed Cache with a status of Stopped if that server is not running it. You simply won’t see a line entry for Distributed Cache at all. Additionally, if you know one of the servers running Distributed Cache, you can run the following PowerShell from that server as the setup account. These commands will not work from a server not running the Distributed Cache service.

Once you know what servers in your farm are not running the Distributed Cache service, you may match them as normal.

• Patch Distributed Cache servers – From the step above, we already found what servers in the farm are running the Distributed Cache service. To patch these servers, you must first stop the service one at a time. You can’t simply stop it like you would any other service as this can result in data loss.
  • You must use the script below to gracefully stop the service, transferring all data that lived in that cache to another server in the cluster. Microsoft documents that this script may take up to 15 minutes to run. I have set the timeout to 30 minutes to be safe.

• • Once the script is complete, you may patch that server.
  • Once the server is patched, you can start the Distributed Cache service again by running:

• • Repeat the above steps on every other server in the farm that is running the Distributed Cache service.

1. Log on to one of the servers in the farm that should have the Distributed Cache service running on it and run the following command again:
2. This should match what it looked like the first time you ran it before patching started. Verify the Service Status says Up for each entry.
3. Click on Central Administration for the farm. View the SharePoint Health Analyzer issues that appear on the top of the page. Make sure there are no entries referring to Distributed Cache.
4. Run Get-CacheClusterHealth. If anything is listed under Unallocated, make sure they go away after 15 minutes or so.

When this workflow action kicks off, a list item will be entered for each assignee in the associated Tasks list. By default, when one of the assignees completes the task, the other list items remain in a "Not Started" state. To get around this, you want to add the "Nintex Workflow Multi Outcome Task" content type to the Tasks list. Now, when the first person completes the task, the other tasks will automatically be completed.

SqlConnection connection = null;

//Build SQL Query

StringBuilder sqlQueryBuilder = null;

try

{

//Add Shell Admin to new DB (add to db_owner role and SharePoint_Shell_Access role

String[] accountsToPermissionForShellAdmin = (<Your comma delimited list of users/groups you want to add>)

connection = new SqlConnection(<Your new database connection string. If you have a SPContentDatabase object, you can call db.DatabaseConnectionString>);

connection.Open();

//Create the SharePoint_ShellAccess Schema

SqlCommand myCommand = new SqlCommand("CREATE SCHEMA [SharePoint_Shell_Access]", connection);

myCommand.ExecuteNonQuery();

//Create the SharePoint_ShellAccess Role

myCommand = new SqlCommand("CREATE ROLE [SharePoint_Shell_Access]", connection);

myCommand.ExecuteNonQuery();

//Have the new Role be the owner of the new Schema

myCommand = new SqlCommand("ALTER AUTHORIZATION ON SCHEMA::[SharePoint_Shell_Access] to [SharePoint_Shell_Access]", connection);

myCommand.ExecuteNonQuery();

foreach (String account in accountsToPermissionForShellAdmin)

{

try

{

//Add as db_owner

myCommand = connection.CreateCommand();

myCommand.CommandText = "sp_addrolemember";

myCommand.CommandType = System.Data.CommandType.StoredProcedure;

myCommand.Parameters.AddWithValue("@rolename", "db_owner");

myCommand.Parameters.AddWithValue("@membername", account);

myCommand.ExecuteNonQuery();

//Add as SharePoint_Shell_Access

myCommand = connection.CreateCommand();

myCommand.CommandText = "sp_addrolemember";

myCommand.CommandType = System.Data.CommandType.StoredProcedure;

myCommand.Parameters.AddWithValue("@rolename", "SharePoint_Shell_Access");

myCommand.Parameters.AddWithValue("@membername", account);

myCommand.ExecuteNonQuery();

}

catch (Exception ex)

{

 #Log error message somewhere

}

}

}

catch (Exception ex)

{

 #Log error message somewhere

}

//Close connection

if ((connection != null) && (connection.State == System.Data.ConnectionState.Open))

{

connection.Close();

}

The output will be a comma delimited set of values which you can easily import into Excel. Hope you find this helpful!

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

$fileForOutput = "C:\YourFilePath\Output.txt"
#Print Headers
("" + "ACCOUNT ID" + "," + "EMAIL IN UPA" + "," + "EMAIL IN AD" + "," + "NOTES") | Out-File $fileForOutput -Append

#Load required assemblies for SP and UPA
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server")
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server.UserProfiles")

#Create new context object
$contextWeb = New-Object Microsoft.SharePoint.SPSite("https://CanUseCAURL")
$serverContext = [Microsoft.Office.Server.ServerContext]::GetContext($contextWeb)

#Create connection to UPA and get profiles
$upaManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($serverContext)
$profiles = $upaManager.GetEnumerator()

$count = 0
foreach($profile in $profiles)
{
    $count++
    try
    {
        #Get email address that is stored in UPA
        $userEmailInUPA = $profile.Item("WorkEmail")
        $userAccountNameInUPA = $profile.AccountName

        #Get email address that is stored in AD
        #Get rid of domain
        if($userAccountNameInUPA.contains("\"))
        {
            $slashLocation = $userAccountNameInUPA.indexOf("\")
            $userAccountNameInUPA = $userAccountNameInUPA.Substring(($slashLocation+1),($userAccountNameInUPA.Length - ($slashLocation+1)))
        }

        $searcher = new-object DirectoryServices.DirectorySearcher([ADSI]"") 
        $searcher.filter = "(&(objectClass=user)(sAMAccountName= $userAccountNameInUPA))" 
        $Searcher.CacheResults = $true 
        $Searcher.SearchScope = "Subtree" 
        $Searcher.PageSize = 1000 
        $results = $searcher.findall() 
 
        #If results does not equal 1, can't do comparison
        if($results.Count -eq 0)
        {
            ("" + $userAccountNameInUPA  + "," + $userEmailInUPA + "," + "NA" + "," + "User Not Found in AD") | Out-File $fileForOutput -Append
            continue
        }
        elseif($results.Count -gt 1)
        {
            ("" + $userAccountNameInUPA  + "," + $userEmailInUPA + "," + "NA" + "," + "Multiple Users Found in AD") | Out-File $fileForOutput -Append
            continue
        }
        elseif($results.Count -eq 1)
        {
            $result = $results[0]
           
            #Get email address if they have one
            [string]$adEmailValue = ""
            if($result.Properties["proxyaddresses"].Count -gt 0)
            {
                $adEmailValue = $result.Properties["proxyaddresses"][($result.Properties["proxyaddresses"].Count -1)]
                if($adEmailValue.IndexOf("SMTP:") -eq 0)
                {
                    $adEmailValue = $adEmailValue.Substring(5)
                }
            }
        }

        #Compare the email found in UPA with what is in AD
        if(($adEmailValue -eq $null) -and ($userEmailInUPA -eq $null))
        {
            ("" + $userAccountNameInUPA +  "," + $userEmailInUPA + "," + $adEmailValue + "," + "Match") | Out-File $fileForOutput -Append
        }
        else
        {
            if($adEmailValue -eq $userEmailInUPA)
            {
                ("" + $userAccountNameInUPA + "," + $userEmailInUPA + "," + $adEmailValue + "," + "Match") | Out-File $fileForOutput -Append
            }
            else
            {
                ("" + $userAccountNameInUPA + "," + $userEmailInUPA + "," + $adEmailValue + "," + "Does Not Match") | Out-File $fileForOutput -Append
            }
        }
    }
    catch
    {
        #Silently skipping any failures. Feel free to put your own logic here
    }
      
}
$count | Out-File $fileForOutput -Append

At the web level, there are 3 properties that exist that should be able to provide some assistance: Users, AllUsers, and SiteUsers

• Users
  • MSDN Description: Gets the collection of user objects that are explicitly assigned permissions in the website.
  • Issue: Take an example where you break inheritance on a list, and permission a user directly to that list. That list is the only thing the user has permissions to on the site. The user will show up under this property. The problem is when that list is deleted, the user still shows up here. The reason is because that user still shows up under site actions - site settings - site permissions as 'Limited Access' even though they have no current permissions to anything. Manually deleting them from here will get them to stop showing up under this property
• AllUsers
  
  • MSDN Description: Gets the collection of user objects that represents all users who are either members of the site or who have browsed to the site as authenticated members of a domain group in the site.
  • Issue: The MSDN description is accurate. It shows you users who have browsed to the site through a domain group that has access. Once that group is removed and the user no longer has permissions, he continues to show up here.
• SiteUsers
  
  • MSDN Description: Gets the collection of all users that belong to the site collection.
  • Issue: From what I can tell, this property just mimics what is found in the User Info table, which is not what we want.

Conclusion: All methods of finding users have some flaw when only looking for users who currently have permissions to something on the site. If you know of a way to do this, please share in the comments section!

To log ULS logs to this database you must enable the 'Diagnostic Data Provider: Trace Log' timer job. By default, this job runs every 10 minutes and logs current ULS to one of 31 dbo.ULSTraceLog_Partition tabbles in the Usage database. There is one partition for each day of the month and every day at midnight, it will start logging to the next partition. By default, logs are only stored for 14 days, so only 14 partition tables should ever have data in it. This number is configurable.

There is also a configurable number which determines how large those partitions can grow. You can find this under the dbo.Configuration table in the Usage database under the property 'Max Total Bytes - ULSTraceLog'. If you take this number, and divide it by 'Retention Period - ULSTraceLog' (also found in dbo.Configuration), this is how many bytes each partition can grow. Taking the default values of 6200000000 for Max Total Bytes and 14 for Retention period, this only gives you 5.77GB worth of logs each day. This may be fine for a small-mid size farm, but for a large farm, this will probably need to be increased. If you are running out of space, you will find that the ULS logs are being written to the partitions correctly starting at midnight and are stopping some point throughout the day. To resolve this, either raise the value of 'Max Total Bytes - ULSTraceLog', lower the value of  'Retention Period - ULSTraceLog', or some combination of the two.

Hope this saves you some time!

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Get available quota templates in farm
$Templates = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.QuotaTemplates

#Loop through wach web app
foreach($webApp in Get-SPWebApplication)
{
    #Loop through each site in the web app to check quota
    foreach($site in $webApp.Sites)
    {
        $currentQuotaID = $site.Quota.QuotaID
        $quotaFound = $false
       
        #Loop through each quota template in the farm looking for a mact in IDs
        foreach($Template in $Templates)
        {
            #If there is a macth found, break out of the loop and move on to the next site
            if($currentQuotaID -eq $Template.QuotaID)
            {
                $quotaFound = $true
                break
            }
        }
       
        #If no match is found, output it
        if($quotaFound -eq $false)
        {
            Write-Host ("No quota found for " + $site.URL + ". QuotaID: " + $currentQuotaID)
        }
        $site.Dispose()
    }
}

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#----------------------------------SETTINGS----------------------------------#

#Original owner that you are looking to globally swap out (Domain\Account)
$originalOwner = "DOMAIN\account1"

#Change from the original owner above to this person(Domain\Account)
$ownerToChangeTo = "DOMAIN\account2"

#When auditMode is set to $true, changes will not actually be made, just displayed to screen ($true/$false)
$auditMode = $true

#----------------------------------SETTINGS----------------------------------#

$sites = Get-SPSite -Limit All
foreach($site in $sites)
{
    #Check primary owner
    if($site.Owner.LoginName -eq $originalOwner)
    {
        Write-Host ($site.URL)
        Write-Host ("-Owner: " + $site.Owner + "-MATCH")
        Write-Host ("-Secondary: " + $site.SecondaryContact)
        Write-Host ("-Changing primary owner from " + $originalOwner + " to " + $ownerToChangeTo)
        Write-Host ("")
       
        #Only process change if audit mode -eq $false
        if($auditMode -eq $false)
        {
            Set-SPSite -Identity $site -OwnerAlias $ownerToChangeTo
        }
    }
   

    #Check secondary owner
    if($site.SecondaryContact.LoginName -eq $originalOwner)
    {
        Write-Host ($site.URL)
        Write-Host ("-Owner: " + $site.Owner)
        Write-Host ("-Secondary: " + $site.SecondaryContact + "-MATCH")
        Write-Host ("-Changing secondary owner from " + $originalOwner + " to " + $ownerToChangeTo)
        Write-Host ("")
       
        #Only process change if audit mode -eq $false
        if($auditMode -eq $false)
        {
            Set-SPSite -Identity $site -SecondaryOwnerAlias $ownerToChangeTo
        }
    }
   
    $site.Dispose()
}

#If Audit mode was on, notify
if($auditMode -ne $false)
{
    Write-Host ("This script was ran in Audit Mode. No changes were made. Edit this file and set that variable to false and run again to actually make the changes.")
}