Michael Blumenthal's BlumenthalIT.NET

The best practice is to deploy a site branding through a web solution package.  We had a third party do a branding for us, then needed to update it before they delivered the source code for the WSP to us.  So I found myself needing to update a master page for multiple site collections.  The master page was deployed via the WSP. If I updated it by uploading a new version of the master page to the Master Page Gallery in each site collection, I’d have to do that upload 20 times since we had 20 site collections.  But if I updated the file in its Feature folder in the 12 Hive, I’d only have to do the update once, and it would take effect everywhere assuming that the master pages that were out there were not customized from the site definition.  Could I use PowerShell to quickly report on the customization state of all instances of my master page? Of course!

function global:Get-SPWebApplication{
  Get-SPFarm |% {$_.Services} | where {'$_.TYPEName -eq "Windows SharePoint Services Web Application"'} |% {$_.WebApplications} |% {Write-Output $_}
}

function global:get-AllSiteCols($webAppName){
$WA = Get-SPWebApplication |where {$_.Name -eq $webAppName}
return $WA.Sites
}

function global:report-masterPageStates($masterFilename)
{

#example of $masterFilename: “mycustom.master’
$sites = get-AllSiteCols $webAppName
$sites | foreach {
    $site = $_
    $rootweb = $site.Rootweb
    $MPG = $rootweb.Lists["Master Page Gallery"]
    $masterItem = $MPG.Items | where {$_.Name -eq $masterFilename}
    if ($masteritem.File.CustomizedPageStatus -eq "Customized") {$fontcolor = "Red"} else {$fontcolor = "Green"}
    Write-host -foreground $fontcolor $site.Url":"$masterItem.Name ": Customization Status:" $masteritem.File.CustomizedPageStatus
    $rootweb.Dispose()
    $site.Dispose()
    }
}

--Michael