Configuring WinRM: Difference between revisions
(Created page with " == Introduction == Windows servers can be monitored by nGeniusPULSE using either WinRM or SNMP. Both need configuration on Windows servers to be ready for data collect...") |
No edit summary |
||
| Line 23: | Line 23: | ||
Example: | Example: | ||
<pre>PS> winrm set winrm/config/client/auth | <pre>PS> winrm set winrm/config/client/auth '@{Basic="true"}'</pre> | ||
| | ||
Revision as of 17:58, 11 March 2020
Introduction
Windows servers can be monitored by nGeniusPULSE using either WinRM or SNMP. Both need configuration on Windows servers to be ready for data collection. WinRM is recommended because the Windows SNMP Agent (native SNMP or 3rd party SNMP) has insufficient support for health metrics.
Solution
Please refer to the following document to configure WinRM on Windows Servers:
https://downloads.netscout.com/nGeniusPulse/v33/ConfigureWinRMonWindowsServers.html
The remarks may be usefull:
Configure Windows server using Group Policy (Basic Authentication, no Encryption) in Domain
> GPO objects must be linked to one or more Organizational Units but not enforced.
Configure WinRM on a Windows server in Workgroup (Basic Authentication, no Encryption)
> If you want to run winrm command from PowerShell you need to put @{Basic="false"} in the single quotes.
Example:
PS> winrm set winrm/config/client/auth '@{Basic="true"}'