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 Framwork 4.5.1

To set the appropriate permissions and settings for monitoring, please view the Server Requirements and Client Requirements pages.

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

On the Server:

1. Configure the station to receive remote commands:

   Enable-PSRemoting –Force

   
   

2. Enable Credential Security Service Provider (CREDSSP) authentication on the local server:

   Enable-WSManCredSSP –Role Server

3. To increase the maximum number of PS shells per user to 25 and to increase the max memory per shell to 600MB
   1. Enter winrm set winrm/config/winrs '@{MaxShellsPerUser="25"}' 

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

       

4. To Return all users who have the SharePoint_Shell_Access role
   1. Enter Get-SPShellAdmin
       
5. If the desired user is not listed, you can add a specified service account to the SharePoint_Shell_Access role for a given database
1. Enter Add-SPShellAdmin -UserName Domain\Username -Database (Get-SPContentDatabase -Identity “ContentDatabaseName”)  
2. Replace Domain\Username with the desired user

3. Replace ContentDatabaseName with the desired Content Database

   
   

   Note: 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 enter Get-SPDatabase | Add-SPShellAdmin DOMAIN\UserName
6. To Return all users who have the SharePoint_Shell_Access role and confirm the desired user is now listed
   1. Enter Get-SPShellAdmin
       
7. To open the permissions dialog box
1. Enter Set-PSSessionConfiguration -Name Microsoft.PowerShell32 –ShowSecurityDescriptorUI
2.  Add the desired user(s) and ensure they have Read and Execute permissions
3. Click OK to save the changes
   
   
8. Follow step 7a to ensure the permissions were successfully applied
   
   
9. Once the server requirements have been met, please view our Client Requirements page.

On the Client:

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

6. 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)

    

7. 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;}
       
8. To return all content databases in your SharePoint farm (which ensures you have access)
   1. Enter Invoke-Command -Session $s -ScriptBlock {get-SPContentDatabase}
       
9. To return all SharePoint service instances (which ensures you have access)
   1. Enter Invoke-Command -Session $s -ScriptBlock {get-spserviceinstance}
       
10. To attempt to use the PS Session to ensure connectivity between the two machines
11. 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>)