Forum Discussion

Clark_Kent's avatar
Clark_Kent
4 years ago

WinRM status - Not Operational

Hi all,

I need to add Veeam Backup and Recovery items to Logic Monitor. To achieve this, all needed DataSources have been created and added. Unfortunately, there is an issue with WinRM status service in Logic Monitor. The WinRM service seems to be in Not Operational status. I have checked that PSRemoting is enabled as well as IP address of the collector was added to trusted lists on the endpoint.

Do you have any idea how to troubleshoot why WinRM serverice is not operational? To be honest, I have received this documentation page to review (https://www.logicmonitor.com/support/logicmodules/datasources/powershell-support/using-powershell-scripts-in-logicmonitor), but from there I am not able to recognise, how to figure out what prevents WinRM service from being in Operational state.

I am looking forward to any help.

1 Reply

Sort By
  • Barb's avatar
    Barb
    Icon for Advisor rankAdvisor
    2 months ago

    Hi I realize this is an old post but just incase anyone is looking for a simple list of what to check to get WinRM working i have collated some steps.

    Enable WinRM with the below;

    Open Powershell as admin on host that needs to be monitored.

    On domain Servers run > Enable-PSRemoting -Force
    For workgroup Servers run > Enable-psremoting -force -skipnetworkprofilecheck

    On Both Domain and Workgroup run > Set-Item WSMan:\localhost\Client\TrustedHosts -Value 'collectorip1,collectorip2,collectorip3' -Concatenate

    Check result - Get-Item WSMan:\localhost\Client\TrustedHosts


    If above is done and still not working try below;

    This sets up the listener;
    winrm quickconfig

    Also you can remove any WinHttp traffic proxy with; 
    netsh winhttp show proxy
    netsh winhttp reset proxy

    If on a public domain run;

    Set-NetFirewallRule -Name "WINRM-HTTP-In-TCP-PUBLIC" -RemoteAddress Any


    Commands for testing Remote PS session from collector;
    Test-WsMan <Target IP>

    Invoke-Command -ComputerName <TargetIP> -ScriptBlock { Get-ChildItem C:\ } -credential domain\username

     

    https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_troubleshooting?view=powershell-7.4