New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


How can I increase memory for Remote PowerShell?

Votes:

0

Your Vote:

Up

Down

I use several PRTG sensors that use Remote PowerShell. Because I run a large IT environment, the memory that is allocated for Remote PowerShell is not sufficient. This results in errors for Remote PowerShell sensors like, for example, “The WSMan provider host process did not return a proper response”.

How can I turn off the Remote PowerShell memory limitation so that there is always enough memory available for my sensors?

memory powershell prtg remote-powershell

Created on Oct 28, 2014 2:28:58 PM by  Gerald Schoch [Paessler Support]

Last change on Mar 21, 2016 3:46:13 PM by  Gerald Schoch [Paessler Support]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 14 or later

Increasing the Memory Limit for Remote PowerShell

There are various sensor types for which you have to enable Remote PowerShell to monitor the target devices. By default, a remote shell has maximally 150MB memory allocated. This might be insufficient in larger network environments with, for example, several Hyper-V hosts and dozens of virtual machines.

Remote PowerShell sensors might show the following error message if there is too little memory available:

The WSMan provider host process did not return a proper response

In this case, increase the memory limitation of 150MB to 1GB. Use the following command to increase the memory allocation limit for Remote PowerShell:

Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1024

Sensors which use Remote PowerShell will not fail anymore because of this memory limit.

Created on Oct 28, 2014 2:31:48 PM by  Gerald Schoch [Paessler Support]

Last change on Mar 21, 2016 3:46:41 PM by  Gerald Schoch [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.