wlansetprofile works fine when symantec enforcement agent is NOT installed but fails with bad profile if it is



    Hi, this is pretty strange. Wlansetprofile for a PEAP-MSCHAPv2 profile works fine and connection is made.. However, as soon as the Symantec enforcement agent (?) is installed (which in turn causes installation of some other EAP method or inner EAP method within the Microsoft supplied EAP methods), the calls to wlansetprofile start failing. Any ideas?


    However, creating a PEAP-mSCHAPv2 profile via the Vista GUI works fine and exporting it via netsh returns the profile with a <configblob> so not possible to decode what (if anything) is missing in the <config> element when i call wlansetprofile.



    Will appreciate any ideas/previous experiences from anybody..

    Friday, September 26, 2008 6:00 PM