...
...
...
...
...
...
...
...
...
...
...
| Tip |
|---|
Open a Windows PowerShell session as administrator. |
- To enable
Enable Credential Security Service Provider (CREDSSP) authentication on the local client machine:
EnterNo Format Enable-WSManCredSSP -Role client -DelegateComputer “SharePointServerName”
- To open
Open a credentials prompt box
:
No Format Enter $cred=get-Credential
Enter an administrators account (or the admin account you worked with in the Server Requirements) to run the rest of the PowerShell commands with this account.
- To create
Create a new remote session to the SharePointServerName using the authentication type CredSSP and the credentials previously entered:
Enter No Format $s=new-PSsession “SharePointServerName” - authentication credssp -credential
$cred $credWarning If this fails with an "access denied" error, re-run step
7a on to enable configuration of the x64 PowerShell
(i.e. Set-PSSessionConfiguration -Name Microsoft)- To load
.
PowerShell32 –ShowSecurityDescriptorUI Load the SharePoint snap-in to the current session to allow SharePoint related scripts to be executed:
EnterNo Format Invoke-Command -Session $s -ScriptBlock {Add-PSSnapin Microsoft.SharePoint.PowerShell;}
- To return
Return all content databases in your SharePoint farm (which ensures you have access):
EnterNo Format Invoke-Command -Session $s -ScriptBlock {get-SPContentDatabase}
- To return
Return all SharePoint service instances (which ensures you have access):
EnterNo Format Invoke-Command -Session $s -ScriptBlock {get-spserviceinstance}
To attempt to use the PS Session to ensure connectivity between the two machines
Enter No Format Enter-PSSession -session $s
| Tip |
|---|
You will now see the server(s) name in brackets [ ] PS: c:\users\someuser\documents |
...
. Example: [sp2013-app.fabrikaminc.local]: PS C:\Users\adamb\Documents> |
...