Useful SharePoint PowerShell Scripts

Whether you're a developer, or an administrator, there can never be a shortage of knowledge and information about managing SharePoint through PowerShell. Guys over at SharePoint Pro have released a great article composed of 26 handy Windows PowerShell scripts that can help you with various tasks. These script are mainly centered around retrieving information about lists, libraries, files, and pages.

Also, these script will work in your SharePoint 2010, SharePoint 2013, and even SharePoint 2007 environment.

So what are you waiting for, go check it out here: Windows PowerShell Scripts for SharePoint: Info on Files, Pages, Web Parts.

Comments

SharePoint 2013 - Creating and Applying Composed Looks (PowerShell)

If you are a SharePoint administrator looking to quickly apply some basic branding to a site-collection in your SharePoint 2013 environment then you've come to the right spot. Before we begin I assume you have a basic understanding of what Composed Looks are, and perhaps you spent some time playing around with this concept in SharePoint 2013. If not, then don't worry. Here is a basic primer: Composed Look is basically a package which contains elements used for controlling the overall look and feel of a SharePoint site. This includes but not limited to Colors, Fonts, Background Image, CSS files, and Master Page files. Once created, Composed Look can be packaged by using the Design Manager feature, or we can use PowerShell to apply it across one or multiple site collections. NOTE: In this post we will be focusing on creating a composed look from an .spcolor file then using PowerShell to apply the design to a site-site collection of our choice. We wil...

SharePoint 2013 - Can't access the site externally in Internet Explorer ("Page cannot be displayed")

Synopsis Before we start talking about the problem let's understand the setup here. We have a SharePoint 2013 intranet site that is also configured for access outside of the corporate network. Employees use the same URL to visit the site both internally and externally via standard ports (80 and 443). Internal URL: http://sharepoint.domain.com Public URL: https://sharepoint.domain.com The site URL has been added to the Local Intranet zone in Internet Explorer for passing domain credentials. Alternate Access Mappings have been configured in such a way that if a user requests the site over HTTP they are automatically re-directed to HTTPS. Internal URL Zone Public URL for Zone https://sharepoint.domain.com Default https://sharepoint.domain.com http://sharepoint.domain.com Default https://sharepoint.domain.com Web application has been configured to use Kerberos protocol for authenticating incom...

Remove Orphaned Web Parts - MissingWebPart

At some point you may have encountered an error like this while browsing through the SharePoint Health Analyzer or if you are attempting to test your content database (i.e., Test-SPContentDatabase) prior to mounting it. Message reads something like this: One caveat is that the log message never reveals the Location of the culprit web part. Luckily we can utilize T-SQL to query the content database and reveal the location of the web part in question. Query the Content Database To do this fire up the SQL Server Management Studio either locally from your machine or while logged on to the SQL Server back-end of your SharePoint farm, open up the new Query window and enter the following statement: USE < Content_Database_Name > SELECT AllDocs.SiteId,WebId, Webs.Title as 'Web Title', ListId, DirName,LeafName FROM AllDocs inner join AllWebParts on Alldocs.Id = AllWebParts.tp_PageUrlID inner join Webs on Alldocs.WebId = webs.Id...

SharePoint Musings

Search This Blog