Wireless management software

[dickchailey]

Today I was asked by a client to set up four new Dell laptops. This involves "upgrading" from Vista to Xp, removing all the "grapware", joining the company domain and installing applications. I normally remove the supplied wireless management software and let windows do its thing but I forgot and then decided to run with the Dell software. I then noticed an option to set up the wireless connection before loading windows and logging into the domain. IT WORKS. A small status box comes up as the laptop loads and shows the adapter searching for the WAP authenticating getting an IP etc. Then Windows completes loading and brings up the login box. No more failed to load profile errors and trying to explain to users about the need to allow time for the wireless connection to set up before login.
Does anyone know if any Thinkpad wireless management software has this option? Perhaps I should see if the Dell software will work with other laptops (doubtful).
This has been my first experience of Dell laptops for some years and a good start. The client buys £400 laptops on a 3 year rolling replacement programme and has given up on Acer machines following graphics problems. I will stick to my Z61t.

[RealBlackStuff]

FWIW, I use Dell software and drivers on several Thinkpads (T23/T30/T40), to run Broadcom BMC94306MP wifi cards.
No problems. However, I let Windows manage connections, and have uninstalled Thinkvantage Access Connections.
They always connect to my home network without any issues.

[Terrahawk]

There is an option in Access Connections to get it to load a profile and join a WLAN beofre domain logon but you can log in before it finishes the job. I wonder if there's a way to force it to wait a bit.

[dickchailey]

I downloaded the Intel software wireless management software which includes pre login option (providing you use the custom install and use administrator profile options), it works to ensure you get an IP address and finds the domain server but for some reason it messes up loading your profile and causes the laptop to load a temp profile (not a local copy of your roaming profile). Seems to be a local write permissions issue. Given up for now, may try again when the long dark nights give more time! Strange the Dell version worked "out of the box" with a domain amd roaming profiles.