How to enable WMI in Endpoint Firewall?

Tonito Dux 996 Reputation points
2022-08-25T07:48:09.737+00:00

Hi,

I would like to know how to setup an allow rule for Windows Management Instrumentation (WMI-in), aka this:

234757-wmi-gpo.jpg

into Endpoint Firewall:

234807-wmi.png

I dont know why but the interface is complicated and i cannot just simply "transfer" the rule from client to Endpoint.

I have tried also the migration tool (https://learn.microsoft.com/en-us/mem/intune/protect/endpoint-security-firewall-rule-tool) but the PS is hanging about 20min as i am writing this so that is a no go.

Thank you

Microsoft Security | Intune | Other
{count} votes

5 answers

Sort by: Most helpful
  1. Tonito Dux 996 Reputation points
    2022-08-30T09:22:37.203+00:00

    Hi,

    to answer to myself:

    236000-1.png
    236047-2.png

    In screenshot nr.1 under "Network Types" I have selected FW_PROFILE_TYPE_DOMAIN and PRIVATE.
    Protocol 6 can be found in windows local firewall under "advanced settings":

    236065-3.jpg

    Cheers!

    0 comments No comments

  2. Konrad Gawronski 1 Reputation point
    2022-09-13T18:03:17.537+00:00

    We're battling the same issue...
    I think I'm missing something, how exactly do we get to screenshot #1? We've tried ""Network Types" I have selected FW_PROFILE_TYPE_DOMAIN and PRIVATE." but don't see the same options.
    Can you please explain it as you would to a 5 year old. I'd really appreciate it.

    Thank you!


  3. Tonito Dux 996 Reputation points
    2022-09-14T06:21:58.717+00:00

    So Konrad, if i understood you correctly you are wondering how to get to MY 1st screenshot in my ORIGINAL question.

    When this is the case then you need to create or edit an existing policy in Endpoint Manager -> Endpoint Security - > Firewall

    240874-fw01.png

    If you are referring to my screenshot in my ANSWER then:

    You click on your existing rule:

    240779-fw02.png

    Scroll down until you see "configuration settings"->Edit:

    240884-fw03.png

    240848-fw04.png

    After you click edit your are presented with the possibility to add your rules or edit the existing ones:

    240797-fw05.png

    editing an existing rule or creating a new one - it is all the same and then you will be on the correct path to "configure instance" like in my answer:

    240860-fw06.png

    Cheers!

    0 comments No comments

  4. Konrad Gawronski 1 Reputation point
    2022-09-14T11:32:57.483+00:00

    Very much appreciated Sir! Thank you!
    Will be implementing this on Friday. Hopefully the Nessus scan goes without a hitch after these changes.


  5. Nick N 0 Reputation points
    2025-07-14T20:06:13.35+00:00

    Came across this while looking for an answer, and just want to note that in your screenshots you are really just creating an "any any" rule for TCP. Protocol 6 is TCP, not WMI specifically. This would be opening pretty much everything up, and not what you would likely want to do.

    I ended up exporting a GPO policy with the WMI set there, and then used the group policy analytics tool to see what to set. In the end, these are the settings I have and feel comfortable its locked down in intune and seems to have worked for me.

    set to enabled

    interface types all

    filepath: %SystemRoot%\system32\svchost.exe

    then network types I just did Domain.

    set the local port ranges to 135,49152-65535

    Set a Description to something that made sense to me

    Set the direction to inbound traffic

    Enabled protocol, set the protocol to 6

    Enabled service name, set to "winmgmt" (this was found by looking through the output of Get-Service in powershell on my local pc)

    I set my remote address range to just the IP of the server I wanted WMI access

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.