MAC Filter Import Tool

Hello Everybody,

Thanks for all those who tried the MacFilterCallout dll. As you all must have checked out by now that Link Layer Filtering feature is a part of Windows Server 2008 R2 DHCP Server. DHCP Server team has come up with a GUI based tool which will let an administrator import the MAC addresses specified in MACList.txt file (used by MacFilterCallout dll), into the allow/deny list of Windows Server 2008 R2 DHCP Server.

This tool will work only on Windows Server 2008 R2 or above. DHCP Server role must be installed and the service must be up and running. Comments corresponding to each MAC address entry can be edited in place before you import the entries into the DHCP Server database.


Raunak Pandya

DHCP Server Team

Comments (17)
  1. teamdhcp says:

    Matt, the file format for using DHCP PowerShell to import MAC address filter list is –


    Allow,1a-1b-1c-1d-1e-1f,Filter for Computer1

    Allow,2a-2b-2c-2d-2e-2f, Filter for Computer2

    Deny,3a-3b-3c-3d-3e-3f, Filter for Computer3

    Allow,4a-4b-4c-4d-4e-4f, Filter for Computer4

    This is documented in the blog at…/dhcp-mac-address-filter-management-made-easy-with-dhcp-powershell.aspx.

  2. Anonymous says:

    Can use this tool remotely from my Win7?

    This tool will have a Select DHCP server option?

  3. teamdhcp says:

    If you are using the inbox MAC address filtering feature which has been shipping inbox since Windows Server 2008 R2, you can do so using the DHCP PowerShell cmdlet Add-DhcpServerv4Filter with a -Force parameter. See…/jj590713.aspx

    For using DHCP PowerShell, you will need a Windows 8 client/server with RSAT installed. DHCP PowerShell in DHCP RSAT of Windows 8 works with DHCP server running on Windows Server 2008 and above.

  4. Anonymous says:

    Great tool!

    Would be even nicer if it could import wild cards.

  5. teamdhcp says:

    Hi Keith,

    Could you please try importing this using the DHCP PowerShell cmdlets. See…/dhcp-mac-address-filter-management-made-easy-with-dhcp-powershell.aspx

    You will need a Windows 8 client with RSAT installed to use DHCP PowerShell. This will work with DHCP Server on Windows Server 2008 R2 – I presume that's what you are using.

  6. Anonymous says:

    BizTalk Adapter Pack Website | RSS Feed Adapter Pack 2.0 Beta released – 20-Feb-2009 Windows Mobile Website

  7. teamdhcp says:

    Joey, if you have a Windows 8 client, please install RSAT (Remote Server Administration tool) and use the DHCP PowerShell cmdlets and PowerShell pipelining to perform export/import of MAC address filters. DHCP PowerShell cmdlets work with Windows Server 2008 R2.

  8. Joakim Agermark says:

    Where do I find info about this tool? Can I synchronize 3-4 different win2008 R2 DHCP MAC-databases using this tool. Or which API can I use to program the synchronize?

  9. Jus Wondering says:

    Is there a way to overwrite an existing allow when importing deny MACs or vice versa?

  10. Keith Liew says:

    Error occured when running the import tool.

    Error: DHCP Server role not installed.

    But my DHCP server is running and serving end user.

    Please advise the requirements of this import tool and how to solve this?

  11. Matt says:

    What does the text file need to look like?  

  12. Joey says:

    Hi There,

    I'm trying to export an allow list from one dhcp server and then go to another dhcp server on another subnet and import the list. But I get the following error: Error: File format not proper. Missing MAC_ACTION in beginning of file. This is how the file is set up:


  13. rosemary says:

    @ keith : you have to run the tool as administrator

  14. Merala says:

    Dear Team,

    I'm trying to import allow mac list on dhcp server 2012 . But I get the following error: Error: File format not proper. Missing MAC_ACTION in beginning of file.

    Please help me any one.

  15. Samuel_R says:

    @Merala, make sure you have MAC_ACTION = {ALLOW} spelled correctly, it seem to be case sensitive. I had to correct it for the import tool to work fine, although the feature was running smoothly.

  16. Mark says:

    For those wondering on the file format.
    Tab delimited
    First line has to be MAC_ACTION = {ALLOW} or MAC_ACTION = {DENY}
    subsequent lines have the mac address formatted with no spaces or separaters in one column and then a tab and an option comment. The comment has to start with a #. Anything after the # will be considered a comment until EOL is reached

    001122334455 [tag:Mr]. Un's laptop.

  17. Keith says:

    Thanks to rosemary. Runas administrator solve my issue.

Comments are closed.

Skip to main content