If you would like to rename a service application or it's proxy, PowerShell can get it done!

Let's say the Managed Metadata service is named "Managed Metadata" and the associated proxy is also named "Managed Metadata".  To change the service name to "Managed Metadata Service" and the proxy name to "Managed Metadata Service Proxy", the following script would do it:

# Rename SharePoint Service Application
$service = Get-SPServiceApplication -Name "Managed Metadata"
$service.Name = "Managed Metadata Service"
$service.Update()

# Rename SharePoint Service Application Proxy
$proxy = Get-SPServiceApplicationProxy | ? {$_.Name -eq "Managed Metadata"}
$proxy.Name = "Managed Metadata Service Proxy"
$proxy.Update()

 

Would you like to know how many workflows are in a given site collection?  How many of those workflows are currently running?  How many old versions of workflows you have laying around?  The following PowerShell script will crawl a site collection and enumerate all lists/libraries for workflow associations and report back useful information such as list name, workflow name and workflows running.

# Title:   Locate-SiteWorkflows.ps1
# Version: 1.0, 08OCT19
# Author:  James Sanders
# Purpose: Find all workflows in a given site collection

# Add the PowerShell Snap-In
Add-PSSnapin Microsoft.SharePoint.PowerShell -EA SilentlyContinue

$results = @()
$siteColl =  "https://your.portal/site_collection"
$site = Get-SPSite -Identity $siteColl -Limit All
ForEach($web in $site.AllWebs) {
  Write-Host "`nProcessing web site: $($web.Url)`n"
  ForEach($list in $web.Lists) {
    Write-Host "Inspecting list: $($list.Title) ... " -NoNewLine
    If ($list.WorkflowAssociations -ne $null) {
      Write-Host "Workflows located!"
      ForEach($wflowAssociation in $list.WorkflowAssociations) {
        $RowDetails =  @{
          "List Name"         = $wflowAssociation.ParentList.Title
          "Workflow Name"     = $wflowAssociation.Name
          "Running Instances" = $wflowAssociation.RunningInstances
          "Created On"        = $wflowAssociation.Created
          "Modified On"       = $wflowAssociation.Modified
          "Parent Web"        = $wflowAssociation.ParentWeb
          "Task List"         = $wflowAssociation.TaskListTitle
          "History List"      = $wflowAssociation.HistoryListTitle
          "Site URL"          = $myWeb.Url
        }  
        $results += New-Object PSObject -Property $RowDetails
      }
    }
    Else {Write-Host}
  }
}

$csvFile = [Environment]::GetFolderPath("Desktop") + "\workflowList.csv"
$results | Select-Object "List Name", "Workflow Name", "Running Instances", "Created On","Modified On","Parent Web", "Task List","History List", "Site URL" | export-csv -Path $csvFile -NoTypeInformation

 

After installing or upgrading to vCenter Server 6.0 on Windows, you may notice the following issues:

Review the %ProgramData%\VMware\vCenterServer\runtime\VMwareSTSService\logs\lookupserver.log for entries like:

Review the %ProgramData%\VMware\vCenterServer\logs\vapi\endpoint\endpoint.log for entries like:

Cause

This issue occurs when the Local System user overrides the Local Machine's Path registry key and prevents the VMware Secure Token Service (STS) from starting properly.

Resolution

 

Copyright 2011 - 2021 The Lazy SharePoint Admin | All Rights Reserved
menu-circlecross-circle linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram