Re: [WIRELESS-LAN] What do you do for 3rd Party Client Configuration Tools and SecureW2

[Michael Griego]

We only "officially" support the built in supplicant for Windows and Mac OS X (we're using PEAP). Sometimes our helpdesk will configure the client that comes with the card, though. The default and only officially supported connect mechanism is to turn all that off and use MS' supplicant.

--Mike


On May 3, 2007, at 12:10 PM, Matt Ashfield wrote:

Hi


are running into a bit of snag. We require our users to use SecureW2.
However many of our uses are experiencing issues because of 3rd party
wireless connection tools from Intel or IBM or Dell, etc..

I'm just wondering what others are doing to deal with this? Are you

tool?

Any advice is appreciated.

Thanks

Matt
[EMAIL PROTECTED]

**********

We're preparing to roll-out our new wireless system to users on campus and mandating that you only support connections using Windows as the connection Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http:// www.educause.edu/groups/.

**********
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/groups/.

smime.p7s
Description: S/MIME cryptographic signature