Identify 802.1x clients in an AD domain
270 pts.
0
Q:
Identify 802.1x clients in an AD domain
I'm designing an 802.1x wired deployment with MAC Authentication Bypass for Windows workstations without the 802.1x client. I need to identify which workstations have the client and which do not. I also need to configure the 802.1x client on the workstations that do have it.

The 802.1x client is part of the workstation's NIC driver. It is configured via the authentication tab in the Local Area Network properties.

I can obviously go from workstation to workstation identifying the workstations with the client and configuring them but it is labor intensive project.

These workstations are all part of a windows server 2k3 active directory domain. Is there a way to identify the workstations with the client remotely?
ASKED: Aug 15 2008  6:20 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
720 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
Maybe use some tools from the Sysinternals suite. They could permit you to query a machine to see what processes are running. It sounds like you need some type of inventory tool. WMI scripting is meant to be able to do that exact thing. One scripting resource site is here. Another good resource would be the Microsoft Technet magazine website. Lanspy from Lantricks may be a quick little utility that can help also.


I would recommend using GFI LANguard Network Security Scanner. It should be an ideal solution for what you are trying to accomplish.
Last Answered: Oct 8 2008  3:44 AM GMT by BrienPosey   720 pts.
Latest Contributors: Labnuke99   26290 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



0