Auto-configuring 802.1X for a user on first login

Hello all, I have a bit of a dilemma here as I'm building an image for a large School District utilizing 802.1X authenticated WiFi access points. The users are mostly student Active Directory users who are managed via MCX OD Groups. In Leopard, to setup 802.1X you need to logon as the user, go into System Preferences --> Network, authenticate as an admin user, go into Airport, go to Advanced, go to the 802.1X tab and configure a user 802.1x configuration, enter the users AD credentials, go to the Airport tab, click the + button to add a new wireless, type in the name of the Wireless network, select 802.1x in the Security drop down menu, then select the user 802.1x config in the 802.1x configuration. From this point forward when the user logs in they will be auto-connected to the wireless network, and if their computer sleeps it will reconnect on wakeup. However, we're talking about just under 3000 laptops scattered over a wide geographic area... I'm trying to find a way to create a login script that runs on first login, checks into a database server we have that contains the user id and passswords and auto-configures the network access. Or even something that gets everything configured and on first login asks for the username and password, but then configures things so it doesn't need to be entered again. Without going through the process we're having lots of problems - when you login you need to enter your credentials, but then if the computer goes to sleep when you wake it up it will show a connection but won't be authenticated so you have no wireless access and need to power off Airport then power on and re-authenticate. I've browsed through the Leopard Command Line Admin guide but was unable to find anything referencing Airport config, let alone 802.1x and keychain passwords that are needed. Even figuring out how to get this all working by hand was a pain as the 802.1x area seems poorly documented. I had a script on Tiger that did a lot of this by building up several plist files by hand using plistbuddy, but Leopard has changed things quite a bit and those scripts don't do anything for Leopard. Anyone out there more familiar with this than me? Any suggestions are greatly appreciated. Jeff