{"id":438,"date":"2012-05-16T11:02:40","date_gmt":"2012-05-16T11:02:40","guid":{"rendered":"http:\/\/www.myfatblog.co.uk\/?p=438"},"modified":"2012-05-16T11:14:56","modified_gmt":"2012-05-16T11:14:56","slug":"shell-access-to-sharepoint","status":"publish","type":"post","link":"http:\/\/www.myfatblog.co.uk\/index.php\/2012\/05\/shell-access-to-sharepoint\/","title":{"rendered":"Shell access to SharePoint."},"content":{"rendered":"

One of the things that has always annoyed me in SharePoint 2010 is the security in PowerShell when trying to work with SharePoint objects.<\/p>\n

There I am, logged into my freshly created development box, drop into PowerShell and can\u00e2\u20ac\u2122t access anything, despite running as administrator. The missing ingredients, yes Database permissions, so duly into SQL, give my log on account DBO access (Come on, it\u00e2\u20ac\u2122s a development box! grin..)<\/p>\n

A better way though is to use the PowerShell cmdlet Add-SPShellAdmin against each of the content databases that I want to work with. (It\u00e2\u20ac\u2122s my Dev box, so all of them frankly..)<\/p>\n

http:\/\/technet.microsoft.com\/en-us\/library\/ff607596.aspx<\/a> <\/p>\n

This command, coupled with a quick PowerShell script to loop through the SPContentDatabase collection soon ensures unrestricted access!<\/p>\n

Get-SPContentDatabase | ForEach-Object {<\/pre>\n
Add-SPShellAdmin -username "domain\\paul"<\/span> -database $_<\/pre>\n
}<\/pre>\n