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
Anonymous
January 01, 2003
Matt, the file format for using DHCP PowerShell to import MAC address filter list is - List,MacAddress,Description 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 blogs.technet.com/.../dhcp-mac-address-filter-management-made-easy-with-dhcp-powershell.aspx.Anonymous
January 01, 2003
Can use this tool remotely from my Win7? This tool will have a Select DHCP server option?Anonymous
January 01, 2003
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 technet.microsoft.com/.../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.Anonymous
January 01, 2003
Great tool! Would be even nicer if it could import wild cards.Anonymous
January 01, 2003
Hi Keith, Could you please try importing this using the DHCP PowerShell cmdlets. See blogs.technet.com/.../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.Anonymous
January 01, 2003
BizTalk Adapter Pack Website | RSS Feed Adapter Pack 2.0 Beta released - 20-Feb-2009 Windows Mobile WebsiteAnonymous
January 01, 2003
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.Anonymous
July 14, 2009
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?Anonymous
February 26, 2013
Is there a way to overwrite an existing allow when importing deny MACs or vice versa?Anonymous
April 11, 2013
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?Anonymous
September 17, 2013
What does the text file need to look like?Anonymous
January 15, 2014
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:Allow,F0-CB-A1-4A-F2-4C,name.wmrsd.lanAllow,E8-39-35-4A-A8-22,LESRM37LABJ.wmrsd.lanAllow,E8-39-35-45-9F-F4,LESRM37LABE.wmrsd.lanAnonymous
January 16, 2014
@ keith : you have to run the tool as administratorAnonymous
May 23, 2014
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.Anonymous
June 23, 2014
@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.Anonymous
December 12, 2014
The comment has been removedAnonymous
January 12, 2015
Thanks to rosemary. Runas administrator solve my issue.