SharePoint 2010 PowerShell: Batch assign permissions to each list item

PowerShell script to add permissions to all items in a list or library, where each item already has its unique set of permissions. Useful when you have hundreds of items in your library and can't be bothered to assign one by one.

SharePoint 2010 "Add to My Links" error: Page not found

Today I came across an interesting issue where users from a certain remote location were reporting a 'Page not found' error when trying to use 'Add to My Links' for documents stored under mysites.

Interestingly, the URL was malformed each time they attempted to click on the function.

It would end up looking like http://_vti_bin/portalapi.aspx?cmd=PinToMyPage&IconUrl=/_layouts/images/null&ListViewURL=xxxxxxxx 

SharePoint 2010 - Where are custom .acsx stored?

If you are developing visual webparts in SharePoint 2010 you may have wondered where the controls were stored.
It can be found in this folder in the 14 hive:
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\

However for SharePoint 2013 this is no longer valid as the ascx is generated on the fly from the compiled DLL.

SharePoint PowerShell - Set Site Collection Owner

Set-SpSite "http://sharepoint" -owneralias "DOMAIN\username"
Set-SpSite "http://sharepoint" -SecondaryOwnerAlias "DOMAIN\username2"

or alternatively, set the secondary site collection owner to null.

Set-SpSite "http://sp2010:90" -SecondaryOwnerAlias $null

Upgrading instances of a form - InfoPath 2010 administrator-approved templates

If you have an administrator approved template for InfoPath in SharePoint, you will notice that whenever you upload a new form template via Central Administrator, all existing instances of the form would not be automatically upgraded.

If there are specific scenarios where you need to have existing forms upgraded, there is a very simple workaround.

1. Take note of the most recent uploaded version of the form in Central Administration - General Application Settings - Manage form templates.

2. Download a copy of the form instance.

3. Open the .xml file in a plain text editor.

4. Modify the version in the form's solutionVersion attribute near the header.

 <?mso-infoPathSolution name="urn:schemas-microsoft-com:office:infopath:Your-Form-Name:-myXSD-2014-01-27T23-22-27" solutionVersion="1.0.0.155" productVersion="14.0.0.0" PIVersion="1.0.0.0" href="http://Your-Site/Your-Form-Name.xsn"?>  

5. Save and re-upload the .xml with the same name.