In the releases note of the probe it states that:
Probe fails to collect data from exchange server on Windows 2008 R2 Server due to security issues. Data collector process fails to execute due to errors in impersonation.
Solution: Manually add permission to the directory "probe/application/exchange_monitor" for the user.
To get this working:
1) Impersonation error occurred because exchange_monitor uses logon type 2 (interactive logon) to access Exchange server. So you have to add this user to local policy Allow log on locally.
2) When the user did not have enough rights to access the earlier mentioned directory Powershell gives an error message saying "Returns POWERSHELL data fetch error". This was solved by adding the following rights allowed to this specific user: Read & execute, List folder contents, Read and Write.
If the above directions do not resolve this error then follow the instructions below:
See also-> http://technet.microsoft.com/en-us/library/ff367871%28v=exchg.141%29.aspx
"Returns POWERSHELL data fetch error"
- "Allow log on locally" on Exchange server
- Allow read, write, execute, list folder contents file permissions on Nimsoft folder (specifically exchange_monitor folder)?
Whenever the user did not have enough rights to access Nimsoft/probes/application/exchange_monitor, on the machine where the probe itself is installed, then Powershell gives an error message saying "Returns POWERSHELL data fetch error".
However, this can be solved by adding the following rights allowed to this specific user on that machine:
Read & execute, List folder contents, Read and Write.
Solution: Manually add permission to the directory "probe/application/exchange_monitor" for the user."
Also to execute the cmdlet on the exchange server, the user should also have 'Exchange View-Only Administrators' privilege.
Along with this, you need to add 'Exchange View-Only Administrators' group in 'Allow log on locally' policy of the exchange server.
To achieve this, open security settings and click on User Rights Assignment. All the policies will be listed in the right pane. Double click on 'Allow log on locally' and add 'Exchange View-Only Administrators' group.
In one other case cmd-let authentication issue was resolved by adding cmd-let user to the Windows Administrators Group.