Open a Windows PowerShell session as administrator. |
Enable Credential Security Service Provider (CREDSSP) authentication on the local client machine:
Enable-WSManCredSSP -Role client -DelegateComputer “SharePointServerName” |
Open a credentials prompt box:
$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:
$s=new-PSsession “SharePointServerName” - authentication credssp -credential $cred |
If this fails with an "access denied" error, re-run step 7 in the Server Requirements to enable configuration of the x64 PowerShell. |
Load the SharePoint snap-in to the current session to allow SharePoint related scripts to be executed:
Invoke-Command -Session $s -ScriptBlock {Add-PSSnapin Microsoft.SharePoint.PowerShell;} |
Return all content databases in your SharePoint farm (which ensures you have access):
Invoke-Command -Session $s -ScriptBlock {get-SPContentDatabase} |
Return all SharePoint service instances (which ensures you have access):
Invoke-Command -Session $s -ScriptBlock {get-spserviceinstance} |
To attempt to use the PS Session to ensure connectivity between the two machines
Enter-PSSession -session $s |
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> |