Forum Discussion

AadLutgert's avatar
AadLutgert
Brass Contributor
Sep 09, 2019
Solved

disable Multicast Name Resolution (LLMNR) with Intune

I'm looking for a way to disable Multicast Name Resolution (LLMNR) using Intune. I've checked the MDM Security baseline and all Device configuration policies, but was unable to find the setting. I rather do not want to use Powershell to deploy registry setting, but I do not know another option. 

 

Is there anyone who knows how to disable Multicast Name Resolution? 

 

Thanks in advance

 

 

  • Basher81 I haven't recieved an answer. The best way to do this is creating a powershell script to add the following registry setting:

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient]
    "EnableMulticast"=dword:00000000

     

    You can deploy this by either packaging with the win32 prep tool (application) or deploy it as a powershell script. 

     

    Hope this will help you.

9 Replies

  • nithilin's avatar
    nithilin
    Copper Contributor

    Hi everyone finding this thread from google,

    Intune has this setting in the Settings Catalog, so no need for the script anymore. 

    New Configuration Profile - Win10 and later Settings Catalog, Administrative Templates\Network\DNS Client\
    "Turn off multicast Name Resolution". 

    As far as I can tell, its still a good recommendation to disable this in enterprise environments as the setting leaves you open to Man-In-The-Middle attacks. 

    /Kevin

     

    • AadLutgert's avatar
      AadLutgert
      Brass Contributor

      SweJorgenMVP 

       

      Thanks for your suggestion. I've thought about this option, but ingestion is not allowed for the key location used by this setting. The location used is:

       

      software\policies\microsoft\windows NT\DNS client

       

      And it's not possible to ingest policies for the following key locations:

       

      System

      Software\Windows

      Software\Policies\Microsoft 

       

      And there isn't an exception for the key "windows nt" in the exception list. 

       

      Please let me know if this isn't correct.

       

Resources