Lee, Since your scenario directly calls for AD joined machiens, being operated by non local admins...
Can't you use group policy to push the wireless profile? (We looked at this option before, but 80% of our machines are NOT AD machines) http://technet2.microsoft.com/windowsserver/en/library/1f52744d-02d1-421d-bc85-af90cc0ddb261033.mspx?mfr=true On Tue, Jun 3, 2008 at 9:01 PM, Lee H Badman <[EMAIL PROTECTED]> wrote: > Is anyone using this combination: > > > > -Impulse NAC on the 802.1x WLAN > > -ID Engines AutoConnect for 802.1x supplicants -AD machines (in domain on > wired, not necessarily in domain on WLAN) on the same 802.1x WLAN? > > > > Primary question- how are you getting the AutoConnect (or other means of > building wireless profile with Windows supplicant) onto the AD machines when > under control of non-admins? Also- same question on Impulse/AD- how are you > getting Impulse policy key onto non-admin machines (wireless or wired)? > Pushed as part of AD build, "go see an admin" policy, or something else? > > > > Regards- > > > > Lee Badman > > > > Lee H. Badman > > Wireless/Network Engineer > > Information Technology and Services > > Syracuse University > > 315 443-3003 > > > ********** 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/.
