PowerShell command to add all users via claims via PowerShell to SharePoint
New-spuser “c:0(.s|true" -web http://www.mysharepointsite.com/ -permissionlevel "read"
PowerShell command to add all users via claims via PowerShell to SharePoint
New-spuser “c:0(.s|true" -web http://www.mysharepointsite.com/ -permissionlevel "read"
I recently was given a WSP to add to our farm.
In this case after the WSP was installed and deployed we needed to activate the feature at the site collection level.
Thats usually easy enough to do through the UI, but in this particular case we had a web application which had over a dozen site collections.
ie:
Activating it at http://jack.com from the UI was fine, but when the user navigated to http://jack.com/blog they were stumbling onto another site collection, and the feature wasn’t activated there.
To activate it on every Site collection meant that I’d have to a) know what each site collection was, and b) visit that site, and activate the feature.
Too much work.
What was needed was a simple script that would loop though each site collection, enabling the feature on each one.
The script below is a result of that need…
# this script enables a feature on every site collection on a given web app
Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue
$webs = get-spsite -webapplication "http://www.yoursharepointURL.com"
$feature = "YourFeatureName" #this might not be what you expect it to be, best to do get-spfeature | Select displayname
Foreach ($oneweb in $webs)
{
write-host $oneweb
$siteFeature = get-spfeature -site $oneweb | Where {$_.displayname -eq $feature}
if ($siteFeature -eq $null)
{
Write-Host "Activating Site level Features at $oneweb" -foregroundcolor Yellow
Enable-SPFeature -Identity $Feature -URL $oneweb.URL -Confirm:$False
}
else
{
Write-Host "Feature $feature is already activated on $oneweb" -foregroundcolor green
}
}
If you look at the simple logic, you’ll see you can run it more than once – and the second time you run it, it should display an all green list indicating that all the site collections already have the feature activated.
See who has them with
get-spshelladmin
add one with
add-spshelladmin
Add-SPShellAdmin Domain\Username #then do it again for all the content databases Get-SPContentDatabase | Add-SPShellAdmin Domain\Username
This was so easy, I had to bookmark it here…
Get-SpSolution | forEach-Object { $_.SolutionFile.SaveAs("C:\exportedWSP\$($_.Name)") }
Note that this only exports farm solutions, not sandboxed ones that sit in the content database
I wanted a way to inject myself as a site collection admin into every site in sharepoint, Note, I’m not talking about the primary/secondary that you can set in Central admin.
I’m talking about that group you can only get to from within each site itself. Or in this case, with the powershell script below…
Note that it takes an array of names – if you have a team of admins or developers that all need access, you can put all their names in the list.
# set site collection owner for all sites...
# 1-2012
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
# $AccountList is an array of Windows Identities in the format of $AccountList = @("DOMAIN\USERID" , "DOMAIN\USERID2")
$AccountList = @("LAB\Jack", "Lab\tom", "Lab\dick", "lab\harry")
#this gets an array of objects representing the sites at the IIS level:
$IISSites = Get-SPWebApplication
Foreach($oneIISSite in $IISSites)
{
#using .Sites, we can get a list of the site collections
foreach ($SharepointSiteCollection in $oneIISSite.Sites)
{
write-host $SharepointSiteCollection.url -ForegroundColor Cyan
$spweb = Get-SPWeb $SharepointSiteCollection.url
#now we have the website, so lets look at each account in our array
foreach ($Account in $AccountList)
{
#lets see if the user already exists
Write-host "Looking to see if User " $account " is a member on " $SharepointSiteCollection.url -foregroundcolor Blue
$user = Get-SPUSER -identity $Account -web $SharepointSiteCollection.url -ErrorAction SilentlyContinue #This will throw an error if the user does not exist
if ($user -eq $null)
{
#if the user did NOT exist, then we will add them here.
$SPWeb.ALLUsers.ADD($Account, "", "", "Added by AdminScript")
$user = Get-SPUSER -identity $Account -web $SharepointSiteCollection.url
Write-host "Added user $Account to URL $SPWeb.URL" -Foregroundcolor Magenta
}
else
{
Write-host "user $Account was already in URL " $SPWeb.URL -Foregroundcolor DarkGreen
}
if ($user.IsSiteAdmin -ne $true)
{
$user.IsSiteAdmin = $true
$user.Update()
Write-host "$account has been made an admin on $SPWeb.URL" -Foregroundcolor Magenta
}
else
{
Write-host "$account was already an admin on $SPWeb.URL" -Foregroundcolor DarkGreen
}
}
$SharePointSiteCollection.Dispose()
}
}
Here’s another version of the script, this one also takes an array of top level URL’s
It’s handy if you have lots of url’s on your site and only want to work with a few of them.
# set site collection owner for all sites...
# 2-2013 Jack
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$logfile = "Powershelloutput.log"
# $AccountList is an array of Windows Identities in the format of $AccountList = @("DOMAINUSERID" , "DOMAINUSERID2")
$AccountList = @("domaintom", "domaindick", "domainharry")
# $iisSiteList is an array of top level IIS site URLs
$iisSiteList = @("http://site1.yoururl.com", "http://anothersite.yoururl.com")
# this is from an earlier version of the script
# That scrip looks at all SP sites on the farm, I've left the old code here for reference
# this gets an array of objects representing the sites at the IIS level:
## $IISSites = Get-SPWebApplication
Foreach($oneIISSite in $IISSiteList)
{
#using .Sites, we can get a list of the site collections
#so really what were saying is for each SharepointSiteCollection
#this code is altered a bit, since we're using an array of top level site names.
# we need to use (Get-SPWebApplication $oneIISSite).Sites
# which is the same as $sitelist = Get-SPWebApplication $oneIISSite
# $sitelist.sites
foreach ($SharepointSiteCollection in (Get-SPWebApplication $oneIISSite).Sites)
{
$msg = $SharepointSiteCollection.url
write-host -ForegroundColor Cyan $msg
Add-Content $logfile $msg
$spweb = Get-SPWeb $SharepointSiteCollection.url
#now we have the website, so lets look at each account in our array
foreach ($Account in $AccountList)
{
#lets see if the user already exists
$msg = "Looking to see if User " + $account + " is a member on " + $SharepointSiteCollection.url
Write-host -foregroundColor Blue $msg
Add-Content $logfile $msg
$user = Get-SPUSER -identity $Account -web $SharepointSiteCollection.url -ErrorAction SilentlyContinue #This will throw an error if the user does not exist
if ($user -eq $null)
{ #if the user did NOT exist, then we will add them here.
$SPWeb.ALLUsers.ADD($Account, "", "", "Added by AdminScript")
$user = Get-SPUSER -identity $Account -web $SharepointSiteCollection.url
$msg = "Added user $Account to URL $SPWeb.URL"
Write-host -Foregroundcolor Magenta $msg
Add-Content $logfile $msg
}
else
{
$msg = "user $Account was already in URL " + $SPWeb.URL
Write-host -ForegroundColor DarkGreen $msg
Add-Content $logfile $msg
}
if ($user.IsSiteAdmin -ne $true)
{
$user.IsSiteAdmin = $true
$user.Update()
$msg = "$account has been made an admin on $SPWeb.URL"
Write-host -Foregroundcolor Magenta $msg
Add-Content $logfile $msg
}
else
{
$msg = "$account was already an admin on $SPWeb.URL"
Write-host -ForegroundColor DarkGreen $msg
Add-Content $logfile $msg
}
}
$SharepointSiteCollection.Dispose()
}
}
$msg = "=============== ALL DONE ================"
Write-host -ForegroundColor DarkGreen $msg
Add-Content $logfile $msg
I had this problem enough times that I wanted to capture the solution.
First of all, credit goes to Craig Lussier on the Technet forms, his post has the full solution and background.
I used the above solution and it worked great.
I also found a script that I did not try. The script is described as being able to change this setting system wide by looping through each document library in each subsite of a given site – it could come in handy. (the script is by the same poster – Craig Lussier – Thanks Craig!
http://gallery.technet.microsoft.com/scriptcenter/Set-SPDocumentLibrary-0426781c
The code below is from the first link above, I’ve copied it here in case MS ever changes the link structure and the original post can’t be found.
# SPAssignment $gc = Start-SPAssignment #Get Web $web = $gc | Get-SPWeb "http://yourspweburl" #Get Document Library $docLib = $web.lists["Your Document Library Title"] #View all properties/methods of the Document Library and you'll see that BrowserFileHandling is a property $docLib | Get-Member #See the current BrowserFileHandling setting for the Document Library $docLib.BrowserFileHandling #If you need to change it from Strict to Permissive $docLib.BrowserFileHandling = "Permissive" $docLib.Update() # End SPAssgment $gc | Stop-SPAssignment