Looks like another MS bundling attempt. It might even work well, if you live in a Microsoft-centric environment. I bet as soon as you introduce a Mac or a linux box, it won't be able to handle it because of yet again proprietary protocols.
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Yes, perhaps another attempt
Yes, perhaps another attempt by Microsoft at a bundling effort. But, interestingly, it turns out this is likely not to be the case for a couple of reasons. First, Microsoft is weak on the enforcement side of network access control. For enforcement you need the inclusion of the network infrastructure devices (switches, wireless access points, VPN gateways, inline security devices, etc.). Second, as you appropriately point out, a complete solution needs to include non-Windows clients. Microsoft seems to have gotten this message (and perhaps for the first time is forced to acknowledge the existence of non-Windows clients) since they have an active NAP partner program designed to encourage third parties to address these holes in their solution. I know since they approached my company to build Linux and Mac NAP agents. They also do license their protocols to third parties and have submitted them (or some of them) to the TCG (Trusted Computing Group) for inclusion in the TNC (Trusted Network Connect) working group. Because of this, we have been able to build an alternative to NPS in an appliance form factor.
Michael Fine
http://avendasys.com
Post new comment