Are we talking about Windows NAP here? If so, only works for Windows clients. There's more to it than "AD permissions" - you need policy servers to be able to define/enforce your policy.
Additionally, I'm not sure how flexible OP's needs are. How many different types of VLANs do you want to be able to support? NAP doesn't give you much flexibility I think. Cheers Ken From: Jon Harris [mailto:[email protected]] Sent: Thursday, 17 December 2009 11:50 PM To: NT System Admin Issues Subject: Re: NAC Device The NAC is bound to AD for permissions so I GUESS you would need some kind of process where the Linux box/account would use an AD account to get the permission. Jon On Thu, Dec 17, 2009 at 1:18 AM, Angus Scott-Fleming <[email protected]<mailto:[email protected]>> wrote: On 16 Dec 2009 at 17:17, Jon Harris wrote: > No agents the NAC relies on AD for what can or can not access through > the use of the NAC add to that it is part of Server 2008. It installs > on a DC. Displaying my ignorance about the Windows NAC here, but what if you have a device like a Linux box that ignores AD? Does the NAC rely on Windows's DHCP server to control who gets on the LAN? What if someone sets a static IP? I suppose it's time to go do some reading ... [sigh] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
