Manually Configuring the Windows Management Framework

Last updated on 2022-12-14 10:51:56

Barracuda RMM Onsite Managers query WMI over the WSManagement Protocol. If the WS-Management protocol is not available on a device, Barracuda RMM Onsite Manager reverts to querying WMI over DCOM.

In order to utilize WS-Man, Windows Management Framework (WinRM 2.0) or greater must be installed. Below are the steps required to configure the Windows Management Framework manually on a device.

To determine the version of the Windows Management Framework

Launch Command Prompt as Administrator.
Run the following command and look for the version:
```
PowerShell.exe Get-Host
```

Configuring WinRM 2.0

Launch Command Prompt as Administrator.
Run the following command and follow the prompts to enable WinRM: winrm quickconfig –q

Run the following commands to apply the required configuration changes:

winrm set winrm/config @{MaxEnvelopeSizekb = "2000"}
winrm set winrm/config/client @{TrustedHosts="*"}
winrm set winrm/config/client/auth @{Basic="true"}
winrm set winrm/config/service @{EnumerationTimeoutms="240000"}
winrm set winrm/config/service @{MaxConcurrentOperationsPerUser="1500"}
winrm set winrm/config/service @{MaxConnections="50"}
winrm set winrm/config/service/auth @{Basic="true"}

Configuring WinRM 3.0 or higher

Launch Command Prompt as Administrator.
Run the following command and follow the prompts to enable WinRM: winrm quickconfig –q

Run the following commands to apply the required configuration changes:

winrm set winrm/config @{MaxEnvelopeSizekb = "2000"}
winrm set winrm/config/client @{TrustedHosts="*"}
winrm set winrm/config/client/auth @{Basic="true"}
winrm set winrm/config/service @{EnumerationTimeoutms="240000"}
winrm set winrm/config/service @{MaxConcurrentOperationsPerUser="1500"}
winrm set winrm/config/service @{MaxConnections="300"}
winrm set winrm/config/service/auth @{Basic="true"}
winrm set winrm/config/service @{AllowRemoteAccess = "true"}