Microsoft Sharepoint Requirements (Sharepoint Users)

In addition to the system and hardware requirements, the following must be installed on the VitalSigns workstation/server.

Powershell 4.0
.NET Framework 4.5.1

The administration account must have the following:

Active Directory credentials
Member of Exchange Administrators group is ideal
Requires the right to run remote Powershell commands

To set the appropriate permissions and settings for monitoring, please view the Server Requirements and Client Requirements sections below:

Open a Windows PowerShell session as administrator.

Server Requirements:

Configure the station to receive remote commands:
```
Enable-PSRemoting –Force
```
Enable Credential Security Service Provider (CREDSSP) authentication on the local server:
```
Enable-WSManCredSSP –Role Server
```
Increase the maximum number of PS shells per user to 25:
```
winrm set winrm/config/winrs '@{MaxShellsPerUser="25"}'
```

Increase the max memory per shell to 600MB:

winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="600"}'

Return all users who have the SharePoint_Shell_Access role:
```
Get-SPShellAdmin
```
If the desired user is not listed, you can add a specified service account to the SharePoint_Shell_Access role for a given database:

Replace Domain\Username with the desired user and ContentDatabaseName with the desired content database.
```
Enter Add-SPShellAdmin -UserName Domain\Username -Database (Get-SPContentDatabase -Identity “ContentDatabaseName”)  
```
You will need to run this command for all content databases for the user(s) who need access.
To grant access to all Content Databases:
```
Get-SPDatabase | Add-SPShellAdmin DOMAIN\UserName
```
Return all users who have the SharePoint_Shell_Access role and confirm the desired user is now listed:
```
Get-SPShellAdmin
```

Open the permissions dialog box and enter:

 Set-PSSessionConfiguration -Name Microsoft.PowerShell32 –ShowSecurityDescriptorUI

Add the desired user(s) and ensure they have Read and Execute permissions.
Click OK to save the changes.
Once the server requirements have been met, please review the Client Requirements.

Client Requirements:

To enable Credential Security Service Provider (CREDSSP) authentication on the local client machine
1. Enter Enable-WSManCredSSP -Role client -DelegateComputer “SharePointServerName”
To open a credentials prompt box
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 a new remote session to the SharePointServerName using the authentication type CredSSP and the credentials previously entered
Enter $s=new-PSsession “SharePointServerName” - authentication credssp -credential $cred

If this fails with an "access denied" error, re-run step 7a on the server (Server Requirements) to enable configuration of the x64 PowerShell (i.e. Set-PSSessionConfiguration -Name Microsoft.PowerShell32 –ShowSecurityDescriptorUI)
To load the SharePoint snap-in to the current session to allow SharePoint related scripts to be executed
1. Enter Invoke-Command -Session $s -ScriptBlock {Add-PSSnapin Microsoft.SharePoint.PowerShell;}
To return all content databases in your SharePoint farm (which ensures you have access)
1. Enter Invoke-Command -Session $s -ScriptBlock {get-SPContentDatabase}
To return all SharePoint service instances (which ensures you have access)
1. Enter Invoke-Command -Session $s -ScriptBlock {get-spserviceinstance}
To attempt to use the PS Session to ensure connectivity between the two machines
Enter Enter-PSSession -session $s

You will now see the server(s) name in [ ] PS: c:\users\someuser\documents (Example: [sp2013-app.fabrikaminc.local]: PS C:\Users\adamb\Documents>)