Versions Compared

Old Version 26

changes.mady.by.user Former user

Saved on

compared with

New Version 27

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

  • Powershell 4.0
  • .NET Framwork Framework 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
To set the appropriate permissions and settings for monitoring, please view the Server Requirements and Client Requirements sections below:
Tip

Open a Windows PowerShell session as administrator.

On the

Server Requirements:

  1. Configure the station to receive remote commands:

    No Format
    Enable-PSRemoting –Force


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

    No Format
    Enable-WSManCredSSP –Role Server
  3. To increase

    Increase the maximum number of PS shells per user to 25

    and to increase the max memory per shell to 600MBEnter winrm set

    :

    No Format
    winrm set winrm/config/winrs '@{MaxShellsPerUser="25"}'
     Enter winrm set 
  4. Increase the max memory per shell to 600MB:
     No Format
    winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="600"}'
      
  5. To 
    Return all users who have the SharePoint_Shell_Access role:
     No Format
    Enter 
    Get-SPShellAdmin
     
     Highlight
    If the desired user is not listed, you can add a specified service account to the SharePoint_Shell_Access role for a given database:
     Note
    Replace Domain\Username with the desired user and ContentDatabaseName with the desired content database.
     No Format
    Enter Add-SPShellAdmin -UserName Domain\Username -Database (Get-SPContentDatabase -Identity “ContentDatabaseName”)
    6.   
  6. Replace Domain\Username with the desired user
    7. Replace ContentDatabaseName with the desired Content Database
    Note: 
  7.   
     Info
    You will need to run this command for all content databases for the user(s) who need access.
    8.   To 
  8.  Highlight
    To grant access to all Content Databases
    9.  enter 
  9. :
     No Format
    Get-SPDatabase | Add-SPShellAdmin DOMAIN\UserName
  10. To 
    Return all users who have the SharePoint_Shell_Access role and confirm the desired user is now listed:
     No Format
    Enter 
    Get-SPShellAdmin
     
  11. To open 
    Open the permissions dialog box and enter:
     No Format
    12. Enter 
  12.  Set-PSSessionConfiguration -Name Microsoft.PowerShell32 –ShowSecurityDescriptorUI
    13.  

  14. Add the desired user(s) and ensure they have Read and Execute permissions.

  15. Click OK to save the changes

  16. Follow step 7a to ensure the permissions were successfully applied
    .

  17. Once the server requirements have been met, please 
     view our 
    review the Client Requirements
     page
    .
On the 

Client Requirements:
  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>)