Versions Compared
Version | Old Version 9 | New Version 10 |
---|---|---|
Changes made by | Former user |
Former user |
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Tip |
---|
Open a Windows PowerShell session as administrator. |
Enable Credential Security Service Provider (CREDSSP) authentication on the local client machine:
No Format Enable-WSManCredSSP -Role client -DelegateComputer “SharePointServerName”
Open a credentials prompt box:
No Format $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.
Create a new remote session to the SharePointServerName using the authentication type CredSSP and the credentials previously entered:
No Format $s=new-PSsession “SharePointServerName” - authentication credssp -credential $cred
Warning If this fails with an "access denied" error, re-run step 7 in the Server Requirements (go to) to enable configuration of the x64 PowerShell.
Load the SharePoint snap-in to the current session to allow SharePoint related scripts to be executed:
No Format Invoke-Command -Session $s -ScriptBlock {Add-PSSnapin Microsoft.SharePoint.PowerShell;}
Return all content databases in your SharePoint farm (which ensures you have access):
No Format Invoke-Command -Session $s -ScriptBlock {get-SPContentDatabase}
Return all SharePoint service instances (which ensures you have access):
No Format Invoke-Command -Session $s -ScriptBlock {get-spserviceinstance}
To attempt to use the PS Session to ensure connectivity between the two machines
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> |