Update on this issue. We had another Laptop with the same issue, however it had a Dell Wireless card. This lead us to start looking at the OS as the issue, rather than the hardware.
Appears that Windows was the problem, or more importantly the startup of Windows Services, in relation to actually logging into the computer. In testing we have now turned on the following GPO Policy:
Computers\Administrative Templates\System - > Always wait for Network at Computer startup and logon.
When this policy was applied to a test machine, it finally showed the "will try to connect to -> Network Name" at Windows Login, which previously was not working. NOTE: This was with the intel drivers installed, but the intel software not installed -> windows managing the connection.
Next test involved installing the Intel Software (14.2) enterprise. This test so far has failed, but at least we appear to be on the right track.
Another Update. Every time we install Intel Proset, and try to setup a Pre-Logon profile, wireless will no longer connect at crtl-alt-del. It always connects after.
This is not going to help us going forward. I have tried the Admin version of 14.2 and 13.5. Both did the same thing. However once Proset is removed, the drivers for the Adapter reinstalled, I can create a profile with Windows that will do Pre-Logon/Connect to wireless.
Did you ever find a solution? According to the software manual at http://download.intel.com/support/wireless/wlan/sb/intel_prosetwireless_software_v13_user_guide.pdf there's no way to use persistent profiles with Win 7. Seems crazy that Intel doesn't support the 50% of PCs in the world running Win 7.