By Michael T. Smith
As I discussed in "Inventorying SharePoint Using PowerShell," Windows PowerShell is a valuable tool that you can use to inventory top-level SharePoint objects. That article shows you how to get lists of farm features, web applications, site collections, and sites using PowerShell cmdlets. In this article, I will explain how you can use PowerShell to obtain information from SharePoint about lists, libraries, files, and pages. Here are some of the tasks we will explore:
- Find lists and libraries based on just about any feature (e.g., versioning, content approval, date created).
- Find all libraries that use a selected content type.
- Find all items based on a selected column (including finding all documents created by a user).
- Find all documents of a certain type (e.g., .docx).
- Find all files larger than a certain size.
- List all libraries, their file counts, and total file size.
A reminder before we get started: Just because you can use PowerShell does not mean that you can ignore SharePoint security. See "Inventorying SharePoint Using PowerShell" for the basic security requirements. You will need to have at least read permissions to the content you want to explore. You can add the account you're using with PowerShell as a site collection administrator to every site collection or use SharePoint Central Administration user policies to give your account full read permissions in each application (select Central Administration, Application Management, then select an application, then click User Policy).
To read the rest of the article, click here.
By Caroline Marwitz
See if any of the new or improved features listed below for SharePoint 2013 catch your eye. Then head over to Microsoft's SharePoint site for a deeper dive.
1. Authentication
1. Authentication
- OAuth support. This web authorization protocol means that a user or web app can request authorization to get temporary access to specific network resources.
- Default claims-based authentication for new web apps. A new Windows PowerShell cmdlet, Convert-SPWebApplication, helps you migrate from Windows classic-mode authentication to claims-based authentication.
- Distributed Cache Service for login tokens. A dedicated cache helps avoid the need for additional configuration and makes for less memory utilization in the web front-ends.
- Enhanced logging.
To read the rest of the article, click here.
SharePoint Pro Magazine Tips and How-To's
Integrate Windows 8 Applications with SharePoint 2010, by Todd Baginski
No comments:
Post a Comment