SharePoint 2010 Powershell script displays all the Site Collection Administrators for a given web application.

Here's a useful powershell script that I'm blatantly stealing borrowing from here. 

This script displays all the Site Collection Administrators for a given web application.




$siteUrl = Read-Host "Enter Site URL"
 
$rootSite = New-Object Microsoft.SharePoint.SPSite($siteUrl)
$spWebApp = $rootSite.WebApplication
 
foreach($site in $spWebApp.Sites)
{
    foreach($siteAdmin in $site.RootWeb.SiteAdministrators)
    {
        Write-Host "$($siteAdmin.ParentWeb.Url) - $($siteAdmin.DisplayName)"
    }
    $site.Dispose()
}
$rootSite.Dispose()

Comments

  1. AnonymousMay 5, 2015 at 12:22 AM

    This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Setting SharePoint announcements to auto delete after expiration

Image
Setting announcements to auto delete after expiration One thing that always bugged me was the expiration date attached to an Announcement list that does nothing out of the box. Sure, you could always add a filter and change the default view but as soon as you add an Announcements web part to a page the view is UNFILTERED even if a filtered view is the only one to choose from.  You or I could change the default view, but we can’t trust all users to do so. A workflow would be fine to delete the item – simply pause until the expire date then delete the current item.  The workflow would stick with the template if you saved your list off as a template and then still work when you created a new list from that template.  That’s good, but still relies on the user creating the right Announcement list. The better answer was to change the Announcements default content type.  If anyone asks, tell them it’s called Governance, Sparky. The first step was to go to site sett...
Read more

Security Considerations When Using SharePoint Online

SharePoint Online offers a flexible, cloud-based platform for building internal portals, document repositories, and even limited public-facing content. But like any powerful system, it requires careful configuration to ensure it's secure—especially when content is meant to be shared or discovered across a broader audience. Authentication and Access Control The first layer of defense in SharePoint Online is identity. SharePoint is tightly integrated with Azure Active Directory, making it easy to manage access using Microsoft 365 groups, conditional access policies, and multifactor authentication. For internal sites, restrict access to only the necessary users or groups. Avoid using “Everyone” or “Everyone except external users” unless the site is truly intended for broad organizational access. If external sharing is required, limit it as much as possible: Use guest access sparingly and monitor usage Require sign-in for external users, rather than anonymous links Expire s...
Read more

Central notification bar for non coder users in SharePoint 2013 (or 2010)

We wanted a central place to notify people of any important news - planned outages, where the donuts are, etc. This marquee banner had to appear on every site and subsite using our template. I added a content editor webpart, pointing to a file in the SiteAssets of the root site. That worked and allowed me to add CSS, javascript, jquery, etc. in one location and all was right and good. I set up a marquee for those announcements, but since it was in my external file, i was a little uneasy when they decided that the night shift should be able to edit my marquee bar. The night shift usually can't be trusted to close the refrigerator door, let alone any HTML tags, so I needed to lock them down while preventing them from breaking the site as much as possible. I looked into SPServices - "GetListItems", but that seems to always be a local list.  I use this to my advantage when working with "Announcements" and " Links " and that works well, but I couldn...
Read more