SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It only takes a minute to sign up.
Sign up to join this community
I just installed SharePoint 2013 Foundation on a server. I'm confused as to how I can access the PowerShell cmdlets from my client pc. Everything I read assumes you're in front of the actual server. Is there anything like an RSAT module I can install on my client PC?
I don't want to use psremoting, because that has some limitations (I have a lot of custom modules loaded on my client pc). Is there really nothing like say the AD, DNS, DHCP, etc. PowerShell modules, but for SharePoint?
You have to be either on the sharepoint server, or use the PSSession module (PSRemote)
New-PSSession -ComputerName SP2013Server
Then add:
Add-PSSnapin Microsoft.SharePoint.Powershell
Instead of using PowerShell Remoting with SharePoint you could consider another approach.
Since SharePoint 2013 supports several sets of APIs, you could utilize client APIs (CSOM/REST) in PowerShell.
As you already mentioned Microsoft released Windows PowerShell for SharePoint Online for working with SharePoint Online. This SDK uses CSOM as the underlying API for SharePoint Online cmdlets.
To summarize, instead of using PowerShell based on Server Side Object Model (SSOM), it is proposed to perform an operations using client APIs (CSOM/REST) in PowerShell
Get-SPFeature cmdlet returns the SharePoint Features, for example:
Get-SPFeature -Limit ALL | Where-Object {$_.Scope -eq "SITE"}
The CSOM version:
$context = New-Object Microsoft.SharePoint.Client.ClientContext($url)
$siteFeatures = $context.Site.Features
$context.Load($siteFeatures)
$context.ExecuteQuery()
The REST version:
$Url = "https://tenant.sharepoint.com/_api/site/features"
$data = Invoke-RestSPO $Url Get $UserName $Password
Invoke-RestSPO is a custom cmdlet, follow this post for a details.
Invoke-RestSPO.ps1 with Add-Type -Path "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.Runtime.dll" Add-Type -Path "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.dll". Seems like - character is different in the one you referred.
An alternative to the snapin is to load the module directly in PowerShell.
& ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 '
The term 'sharepoint.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + sharepoint.ps1 +~~~~~~ +CategoryInfo: ObjectNotFound: (sharepoint.ps1:String) [], CommandNotFoundException +FullyQualifiedErrorId: CommandNotFoundException Suggestion [3,General]: The command sharepoint.ps1 was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default.
If you trust this command, instead type: ".\sharepoint.ps1". See "get-help about_Command_Precedence" for more details. So I tried .\sharepoint.ps1 instead and got Add-PsSnapin : No snap-ins have been registered for Window PowerShell version 5. - which of course is the very thing I've been trying to workaround. Same error if I use the "&" technique. Note that I'm attempting this on another computer than the SharePoint server, just like the OP, and just copied sharepoint.ps1 to it. Maybe there's other things it needs from the server?
The is no need to open a PSSession with the server, you can just use the CSOM service as @vadim says (another answer in this thread), in order to work with lists or Sharepoint sites data. Here is a very good guide which details the first steps: https://www.itunity.com/article/connecting-spo-csom-api-powershell-1038
