When using an Autologon, wireless utility does not start soon enough

[grumpyfccc]

We have some wireless laptops (Dell E4300)that are set up via the registry (HKLM\Software\Microsoft\WindowsNT\currentversion\winlogon AutoAdminLogon)to log in under a specific user name and password. This works with non Dell laptops utilizing Intel Wireless. The Dells are using the DW WLAN Utility.

If we remove the Autologon and log in by keying in the password, the DW WLAN Utility runs during the logon and everything works (downloading of roaming profile, etc). If we readd the Autologon and reboot, the login process starts, but the DW WLAN Utility does not run during the logon process, and the roaming profile does not come down because the server can not be found.

Any suggestions to get the DW WLAN Utility to work with the Autologon?

 

[linney]

Can you set up the Laptops to allow Windows to manage the Wireless connections rather than the third party program?

"As for configuring your wireless, with each of the last four laptops I've gotten over the years, I've ended up eventually stripping out the vendor's proprietary wireless access management software and letting Windows manage the connections on its own. In XP especially, the wireless connection tools are pretty good and not hard to use. And, with only one tool trying to monitor and manage the wireless, things are much simpler. For example, you can tell the Windows tool NOT to try to connect to just any network it happens to find; to forget about networks you'll never see again; to connect automatically only to networks you know about and preapprove; and so forth. I keep hoping that some vendor will ship a truly effortless tool, but none in my experience has even come close; instead, the built-in Windows tool is still the best I've found."


"Turbulence In The Ether"

http://windowssecrets.com/L060403-03-Turbulence-In-The-Ether

 

[goombawaho]

Wireless network connect + roaming profile = more opportunity for a corrupted profile. In other words - not the best practice to go wireless in that environment.

 

[cdogg]

If linney's suggestion to use the built-in Wireless Zero Configuration to manage wireless networks is an option, they I would suggest as well that you try that.

Also, there is a local policy setting you can set that tells Windows to wait for the network before logging in. Not sure that will help with 3rd-party utilities, but you can try:

1. Start -> Run, type gpedit.msc and hit enter
2. Go to Local Computer Policy -> Computer Configuration -> Administrative Templates -> System -> Logon
3. Enable "Always wait for the network at computer startup and logon"

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.