Knowing that we're not alone with this, looking for another sanity check. We're finding the thorniest issues with PEAP Supplicants (MSCHAP v2, WPA) to be the desire to deploy preconfigured supplicants, or to preconfigure native clients, with some uniformity across all platforms (XP, Vista, Mac). The Mac has been fairly easy, with some Applescript leveraging what's built into the OS. With a home-rolled utility based on the generously-provided Aruba script, we come close to desired functionality on the native supplicant on XP/Vista, but XP falls down hard when wireless utilities like the Intel ProSet, Broadcom, Belkin USB, and others are in play where Windows is not "driving"- we can't seem to find the magic to globally shut these down and enable the Windows wireless client reliably. Lenovo seems to be its own issue- the Lenovo wireless utility and the Windows built-in are pretty well interwoven, not sure if there is any way to "disable" the Lenovo utility. Also we are looking at ID Engines as a commercial answer to these challenges, but many of the same issues above seem to hold true in our early testing- though they do have a nice approach worth looking at. Finally, the Odyssey client comes up frequently in conversation- and I have used it myself and can attest to its power- but like ID Engines, they do not yet have code for Mac and Vista (though both have roadmaps for these). So that leaves using different approaches for each OS, or simply providing manual guidance on how to configure each one, guided along by screenshots- low tech, but arguably just as viable of an option as the others. The question- What are others doing from the "get it configured" standpoint now that there are enough Vista/Lenovo/other curve-balls out there to add some complexity to supplicant configuration in heterogeneous wireless client environments? Lee H. Badman Syracuse University
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
