What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

I have problems with the PowerShell Exchange sensors, what can I do?

Votes:

3

When trying to add new Exchange sensors to PRTG, I get the message

(1) "The Sensor cannot connect to the Device using Remote-PowerShell. Ensure that remote management is enabled on the Exchange Server and the username and password is correct. ..."

-or-

(2) "The Sensor was able to connect to the Device using Remote-PowerShell but couldn't retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. ..."

-or-

(3) "The MessageQueue can only be retrieved from an ExchangeServer 2010 or higher that has the Role 'HubTransport' or 'EdgeTransport' ..."

-or-

(4) “The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details.“

What can I do to fix it?

database exchange folder mailbox mailqueue powershell prtg public publicfolder queue

Created on Jun 21, 2013 2:50:15 PM by  Dieter Loskarn [Paessler Support]

Last change on Jan 4, 2023 11:45:31 AM by  Brandy Greger [Paessler Support]



68 Replies

Accepted Answer

Votes:

1

This article applies as of PRTG 22

Resolving Exchange PowerShell sensor issues

See the following troubleshooting solutions for the error messages:

(1) "Sensor Cannot Connect to the Device"

  • Make sure that PowerShell 2.0/.Net 4.7.2 is installed on your probe system.
  • Do not use an IP address in the device settings of the Exchange server. Instead, use the Fully Qualified Domain Name (FQDN). Note: Some sensors work with the NetBIOS name of the target device, but the Exchange Mail Queue (PowerShell) sensor definitely needs FQDN.
  • See Connect to Exchange servers using remote PowerShell for additional requirements on target side.

(2) "Could Not Retrieve Access to Remote Exchange Management Shell"

  • The user of the sensor needs elevated rights on the Exchange system. Administrator rights are not sufficient. The easiest way to do this is to add the user to the View Only Organisation Management group. For details, see Connect to Exchange servers using remote PowerShell.

(3) "Exchange Server 2010 or Higher with Role 'HubTransport' or 'EdgeTransport' ..."

  • Make sure that your server has the mentioned role.
  • See error message Sensor Cannot Connect to the Device.

(4) "The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details."

  • Solution: PRTG 21.2.67 includes a fix for the issues caused by KB5001779. We recommend that you install PRTG 21.2.67 to resolve the issues with Exchange (PowerShell) sensors. For more information, see the respective release notes.
  • Workaround: If you cannot update your system, follow the steps below:
  1. Navigate to the \Sensor System subfolder of the PRTG program directory and create a backup of ExchangeSensorPS.exe.
  2. Download ExchangeSensorPS_21.x.67.zip here, unzip the file, and store it in the \Sensor System subfolder of the PRTG program directory.

Note: If your Exchange (PowerShell) sensors still show the Down status, try to pause and resume the probe and the sensors. Click Scan Now for each sensor after you resume them.

More

Created on Jun 21, 2013 3:02:01 PM by  Dieter Loskarn [Paessler Support]

Last change on Jan 3, 2023 9:27:39 AM by  Brandy Greger [Paessler Support]



Votes:

0

When adding Exchange Powershell Sensors, I get the following error message:

The Sensor was able to connect to the Device using Remote-PowerShell but couldn't retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/knowledgebase/en/topic/54353 for details. Cannot process argument transformation on parameter 'Identity'. Cannot convert value "\FQDN" to type "Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter". Error: "'\FWDN' is not a valid value for the identity. Parameter name: Identity"

I can connect to ExchDB like at https://kb.paessler.com/en/topic/60793-unknown-error-exchange-database-powershell. My user is member of "view-only organization Management" Group.

Rather strange is the backslash in front of the FQDN, but other sensors without powershell are working and uses the defined correct FQDN.

Any thoughts? Thank you in advance.

Created on Apr 19, 2017 2:17:00 PM



Votes:

0

Did you enter domain, username and password within the windows credential section of the device?

Created on Apr 20, 2017 12:04:55 PM by  Stephan Linke [Paessler Support]



Votes:

0

Our message is:

The Sensor was able to connect to the Device using Remote-PowerShell but couldn't retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/knowledgebase/en/topic/54353 for details. The term 'Get-MailboxDatabaseCopyStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

What is going on?

Created on Jun 22, 2017 10:24:16 AM



Votes:

0

Hi there,

Did you actually check if Get-MailboxDatabaseCopyStatus works on the Exchange host?
Is the device address the FQDN of your exchange server?


Kind regards,
Stephan Linke, Tech Support Team

Created on Jun 22, 2017 12:00:29 PM by  Stephan Linke [Paessler Support]



Votes:

0

Error while trying to add Exchange Database (PowerShell) Sensor:

Could not create the sensor Exchange Database (PowerShell) on device exchange.domain.com (exchange.domain.com).

The Sensor can not connect to the Device using Remote-PowerShell. Ensure that remote management is enabled on the Exchange Server and the user-name and password is correct. See https://kb.paessler.com/knowledgebase/en/topic/54353 for details. Processing data from remote server exchange.domain.com failed with the following error message:
[...]
The user "domain.com/Service/admininistrator" isn't assigned to any management roles. For more information, see the about_Remote_Troubleshooting Help topic.
Please check the following resources:

Can you say anything about my Error? Need i add my account to Management Group of Exchange? What exactly access rights i need to add?

Thank you!

Created on Dec 28, 2018 8:40:46 AM

Last change on Dec 28, 2018 8:46:12 AM by  Felix Saure [Paessler Support]



Votes:

2

Hi Vasily,

The configured user needs to be in the administrative management role to be able to see other values than just his own mailbox. You can check the membership via this CMDlet. Please do also read this article from Microsoft for the required rights to remotely access Exchange servers using remote PowerShell.


Kind regards,
Felix Saure, Tech Support Team

Created on Dec 28, 2018 8:52:56 AM by  Felix Saure [Paessler Support]



Votes:

14

Hello guys,

I know it has been quiet silent around this topic in the last years. Today I updated our Exchange Server with KB5001779. Since then we get (2) "Could Not Retrieve Access to Remote Exchange Management Shell" The user of the sensor needs elevated rights on the Exchange system. It is not sufficient to have administrator rights! The easiest way to achieve this is to add the user to the 'View Only Organisation Management' group. For details, see the Microsoft article Connect to Exchange servers using remote PowerShell.

The strange ting is - it worked perfectly before the update. Also I did set the ExecutionPolicy to RemoteSigned once again and added the user to the View Only Organisation Management' group.

It didn't change anything. Maybe some else experienced this problem?

Thanks! Daniel

Created on Apr 14, 2021 7:58:08 AM



Votes:

8

Hey,

Unfortunately, several customers have reported exactly this behavior after the Exchange update. In software development, it is unfortunately sometimes the case that one manufacturer (in this case Microsoft) changes something and others then have to follow suit.

We have to analyze the problem and I hope that my colleagues from development can offer a hotfix soon. This also means, that unfortunately, I can't offer you a quick solution at the moment and ask for your patience.

Best,
Sven Roggenhofer [Paessler Technical Support]

Created on Apr 14, 2021 8:40:57 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

5

I am experiencing the same issue as you Daniel. This sensor worked fine for many years until last night's Windows Updates (Tuesday April 13, 2021). I double-checked the rights and the rights are fine.

"The sensor was able to connect to the device using Remote PowerShell but could not retrieve access to Remote Exchange Management Shell. Ensure that remote management is enabled on the Exchange Server and the user has sufficient rights. See https://kb.paessler.com/en/topic/54353 for details. The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode."

I suspect that PRTG will have to issue an update to resolve this.

Created on Apr 14, 2021 11:03:07 AM



Votes:

3

Hi there We experience the same behavior after installing Exchange KB5001779. Lets wait. Cheers, Thomas

Created on Apr 14, 2021 11:17:58 AM



Votes:

1

Same here, setting PS Policy and add user to 'View Only Organisation Management' group do not help.

Created on Apr 14, 2021 11:35:21 AM



Votes:

1

I wanted to add my report to the pile. My database and queue sensors have died ever since the update.

Created on Apr 14, 2021 12:42:55 PM



Votes:

0

the same here...

Created on Apr 14, 2021 2:42:05 PM




Votes:

0

Same problem here after Exchange Security Update on four systems. Problem is on database and Mail Queue sensors.

Created on Apr 14, 2021 3:59:53 PM



Votes:

0

Add me to the list

Created on Apr 14, 2021 5:44:11 PM



Votes:

0

Same issue here since latest April 2021 Exchange Cumulative Updates - and based on the exploits against Exchange recently, I patch as early as possible!

Created on Apr 14, 2021 10:50:24 PM



Votes:

0

Same here, multiple Exchange sites no longer working.

Created on Apr 15, 2021 4:10:33 AM



Votes:

0

Same here, Exchange 2016 CU 19 + KB5001779

Created on Apr 15, 2021 5:46:45 AM



Votes:

0

+1

Created on Apr 15, 2021 6:03:18 AM



Votes:

0

Add me to the list

Created on Apr 15, 2021 6:14:54 AM



Votes:

0

Running into the same problem. Please keep me also up-to-date! Thank

Created on Apr 15, 2021 6:23:42 AM



Votes:

5

Hey all,

The problem is already known as mentioned above and the colleagues in development are working on the problem with high priority. As soon as we have a solution for this, we will of course announce it on our release notes.

Best,
Sven Roggenhofer [Paessler Technical Support]

Created on Apr 15, 2021 6:29:40 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

0

Same here, please update me once this is resolved.

Created on Apr 15, 2021 6:40:58 AM



Votes:

0

Same here since the KB5001779 is installed on our Exchange 2016 CU19

Created on Apr 15, 2021 7:04:55 AM



Votes:

0

Same here, please update me once this is resolved.

Created on Apr 15, 2021 9:02:40 AM



Votes:

0

Same here - Exchange Mail Queue and DB sensors all down since KB5001779 installed (Exchange 2019 CU 9)

Created on Apr 15, 2021 9:16:47 AM



Votes:

0

Same problem here with Exchange 2013 CU23 and the latest security update. Could it be that you need to run a "import-pssession" now to be able to use the required commandlets? See https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/import-pssession?view=powershell-7.1

Created on Apr 15, 2021 12:16:10 PM



Votes:

0

Same here, please update me once this is resolved.

Created on Apr 15, 2021 12:29:25 PM



Votes:

1

Same here since the KB5001779 is installed on our Exchange 2016 CU19

Created on Apr 15, 2021 1:09:29 PM



Votes:

0

Same here after installing the April 2021 update to our Exchange 2013 servers.

Created on Apr 15, 2021 3:24:51 PM



Votes:

0

Same with Exchange 2013 after Security Update For Exchange Server 2013 CU23 (KB5001779), 4/‎13/‎2021

Created on Apr 16, 2021 12:41:12 AM



Votes:

0

Same here, please update me once this is resolved.

Created on Apr 16, 2021 8:48:24 AM



Votes:

0

+1 Exchange 2013 CU23 + KB5001779

Created on Apr 16, 2021 8:52:21 AM



Votes:

0

same for me after cu23 for exchange 2013

Created on Apr 16, 2021 11:21:47 AM



Votes:

0

Same here, after Windows patching KB5001779.

Created on Apr 16, 2021 12:34:01 PM



Votes:

0

+1 - after Exchange 2016 CU20 KB5001779

Created on Apr 16, 2021 1:32:08 PM



Votes:

0

Same Issue

Created on Apr 16, 2021 6:20:39 PM



Votes:

0

+1 - also after Exchange 2016 CU20 KB5001779

Created on Apr 18, 2021 10:52:38 AM



Votes:

0

+1 - also after Exchange 2016 CU19 KB5001779 / multple systems

Created on Apr 18, 2021 11:35:10 AM



Votes:

0

+1 - several customer Exchange versions (E2016 CU19 / E2013 CU23) affected after installing KB5001779

Created on Apr 18, 2021 11:49:27 AM



Votes:

0

+1 - after Exchange 2016 CU20 KB5001779

Created on Apr 18, 2021 1:20:25 PM



Votes:

7

Hey all,

We plan to release a fix for the Exchange issue related to KB5001779 with the upcoming stable PRTG version 21.2.67 - most probably within this week.

Please keep an eye on our release notes.

Best,
Sven Roggenhofer [Paessler Technical Support]

Created on Apr 19, 2021 4:17:44 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

0

+1 after the update KB5001779

Created on Apr 19, 2021 12:17:32 PM



Votes:

0

+1

Created on Apr 20, 2021 6:17:51 AM



Votes:

1

On https://techcommunity.microsoft.com/t5/exchange-team-blog/released-april-2021-exchange-server-security-updates/ba-p/2254617 is written :

Known Issues

After application of the Exchange Server April security update CMDlets executed against the Exchange Management Console using an invoked runspace might fail with the following error message: The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. This behavior is expected; please change any code using .AddScript() to use .AddCommand() for continued compatibility.

Created on Apr 20, 2021 8:07:18 AM



Votes:

0

Today's update solved the issue for me. However we have a new problem now. The CPU load on the PRTG server is > 70% now.

Created on Apr 21, 2021 11:56:36 AM



Votes:

0

Hello Jan,

Thank you for your feedback.

Regarding the issue with the CPU load, I invite you to open a support ticket by sending a support bundle, under Setup > Contact Support. So, we can have a look at the server logs.

Regards.

Created on Apr 21, 2021 12:11:19 PM by  Florian Lesage [Paessler Support]



Votes:

0

The issue with Powershell sensors after KB5001779 has been fixed by todays update. I can also confirm though, that unexpectedly high CPU utilization has been a side effect.

Created on Apr 21, 2021 9:28:52 PM



Votes:

1

After the PRTG Core Update to 21.2.67.1562 the Exchange Scripts running again. We have PRTG on an physical machine, can't see higher cpu usage.

Created on Apr 22, 2021 5:34:27 AM



Votes:

0

Thanks for sharing this.

We will have a closer look into cases where the CPU usage increased after the update. Stay tuned.

Best,
Sven Roggenhofer [Paessler Technical Support]

Created on Apr 22, 2021 5:36:43 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

0

Yes, the update did fix it. We also don't experience the high CPU issue on our physical machine.

Created on Apr 22, 2021 5:38:24 AM



Votes:

0

Important information about the issues caused by KB5001779:

PRTG 21.2.67 includes a fix for the issues caused by KB5001779. We recommend that you install PRTG 21.2.67 to resolve the issues with Exchange (PowerShell) sensors. For more information, see Release notes for Version 21.2.67.1562.

Created on Apr 22, 2021 8:25:50 AM by  Florian Weik (1,927) 2 2



Votes:

0

Exchange Powershell probleme resolved. High CPU problem here as well after update to 21.2.67.1562. With version 21.1.66.1664 CPU load 13% With version 21.2.67.1562 CPU load 51%

Created on Apr 22, 2021 9:18:15 AM



Votes:

0

Is it possible that the update "only" triggered a Cache Re-Calculation that now has to be processed? You can see this in a small pop-up in the lower right corner of the web GUI (if it's running).

If this is the case, the CPU load should go down again as soon as the re-calculation is done.

Best,
Sven Roggenhofer [Paessler Technical Support]

Created on Apr 22, 2021 9:21:58 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

0

4 hours later the CPU load is going back to normal. Never waited so long in the past.

Created on Apr 22, 2021 1:30:52 PM



Votes:

0

Thank you for your feedback.

The cache re-calculation can take more or less time depending on many factors including the server resources as well as the number of sensors (taking into account the polling interval and historical data retention periods).

I'm glad to hear that everything works normally again.

Regards.

Created on Apr 22, 2021 1:41:30 PM by  Florian Lesage [Paessler Support]



Votes:

0

Hello ... the new "fix" for Exchange is only available in PRTG 21.2.67 which is the "preview" PRTG channel. And from PRTG it's not recommended to use this channel in "live environments".

--- *snip* --- We strongly recommend that you not use those versions in live environments you depend on. --- *snip* ---

Could you please tell me when this fix will be implemented in the "stable" one?

Thanks and regards

Created on Apr 26, 2021 9:15:09 AM



Votes:

2

Hi,

The version 21.2.67 has been released in the Stable channel on April 21st, as indicated in our release notes: https://www.paessler.com/prtg/history/stable.

Therefore, I invite you to check for new update with the button Check for latest update and download, under Setup > Auto-Update.

You also have the possibility to download the latest installer via this URL: https://downloads.paessler.com/prtg/prtg.zip

Regards.

Created on Apr 26, 2021 10:04:40 AM by  Florian Lesage [Paessler Support]



Votes:

0

Hello, How to fix this issue without upgrade PRTG version?

Created on Apr 26, 2021 10:48:53 AM



Votes:

0

Hey MAA,

We are currently still working on a hotfix for customers without active maintenance. Unfortunately we do not have an ETA for this yet.

Best,
Sven Roggenhofer [Paessler Technical Support]

Created on Apr 26, 2021 11:03:49 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

0

The link to download ExchangeSensorPS is broken: http://download3.paessler.com/support/ExchangeSensorPS_21.x.67.zip

Please let me know if there is another link

Created on Jun 1, 2021 8:15:16 PM



Votes:

0

We're sorry for the inconvenience, we replaced the broken link in the article above.

Cheers,
Sven

Created on Jun 8, 2021 1:08:24 PM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

0

>>We are currently still working on a hotfix for customers without active maintenance. Unfortunately we do not have an ETA for this yet.

you still cannot give a timeframe for fixing the problem?

Created on Jan 2, 2022 2:26:48 PM



Votes:

0

Hello there,

I'm afraid we won't fix this for older versions.


Kind regards

Felix Wiesneth - Team Tech Support

Created on Jan 4, 2022 11:33:29 AM by  Felix Wiesneth [Paessler Support]



Votes:

0

Iam having the same Problem. Iam using the newest version oft PRTG. I has stoppt working since some Days. Is there a Windows or Exchange Update (wich comes from Windows Updates) that is making these problems??!

Created on Feb 11, 2022 2:47:24 PM



Votes:

0

Hi there,

we are not aware of a new issue with the latest Updates from Windows and/or Exchange yet. If you can verify that the issue is related to an update, please let us know and contact us via [email protected] with more insights. Thank you in advance.


Kind regards

Felix Wiesneth - Team Technical Support

Created on Feb 14, 2022 12:29:06 PM by  Felix Wiesneth [Paessler Support]




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.