Windows Firewall Profiles Monitoring Status fails with "102 Method not found"

Last Modified

Sun Aug 19 11:11 GMT 2018

Description

• Windows Firewall Profiles Monitoring Status fails with the following error:
  • 102 Method not found: 'Void com.nable.agent.framework.util.RemediationParameters.set_ActivityResult(com.nable.agent.framework.serverproxy.T_ActivityResult)'.

Environment

• N-able N-central

Solution

• The Windows Firewall Profiles Monitoring Status uses the following registry key to determine which profile is applied:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy
• If this is not present then the Windows Firewall Profiles Monitoring Status will show as misconfigured
• Please ensure the Windows Firewall Profiles are configured properly on the device(s)
• More information on this Monitoring Status can be found here:
  • https://secure.n-able.com/webhelp/NC_12-0-0_en/Content/Services/Services_WinFirewallAMP.htm?Highlight=windows%20firewall%20profiles