Using k2000 system images to image machines. On my latitudes, I'd like to add joining the wireless network preferably to a post installation task or other script that runs after sysprep. This is something that must get done, and too often gets skipped when done by hand.

I welcome any suggestions/scripts
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



Have you tried this?

Configure the wireless profile on one machine.

From the machine run:

netsh wlan export

That'll generate an xml file for each network.

You should then be able to import the config with

netsh wlan add profile filename="name of your xml"

To connect from the command line run

netsh wlan connect name="Name of your profile"

Hope this helps.
Answered 12/08/2011 by: dchristian
Red Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


That'd be a wonderful solution. I'll give that a try.
Answered 12/09/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
That works great in my tests. I'll add it as a post-install task on my images.

Thanks a lot.
Answered 12/09/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
Still need some help on this one. We thought we had it all working. Discovered (as posted above mentioned) that Network Settings are stored in XML. Took a copy of it, and put it as a post install task using -> netsh wlan add profile filename.

It seemed to work on the test machine, however I just started deployment a noticed it was not applying. I then took the profile into the K1000, created a script, and did some testing. Here is what I get:

Profile format error 0x80420011:
The network connection profile is corrupted.

However I can take that same profile, and apply it to the machine it was taken off of....which appears to be my problem. The XML I get, with the necessary settings will only apply on the computer it was taken from. If I try the profile somewhere else, it fails.

Any thoughts? This is a 802.1X profile (WPA2/AES/RAIDUS Server with Certificate -> authenticates to AD).
Answered 12/14/2011 by: hutcha4113
Second Degree Blue Belt

Please log in to comment
Wanted to double check that you are using Vista/7 and not XP. "netsh wlan" do not function in XP. Double check to see that your XML does not reference a specific network interface.
Answered 12/15/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment

I have a similar situation and needing to use this. What would be the easier and more reliable way to have this run automatically postinstall?

Answered 03/26/2013 by: aaronr
Green Belt

  • Have you seen this?

    Americas KKE Series - K2000 Koncepts: Including Network Interface Profiles in your K2000 Tasks

    • I have not, thank you! Going to try it out and see if I can get it to work.
    • All current recordings are accessible at www.kace.com/support/training/kke/archive
      The recording listed here is no longer available. A newer version of this may be available at the archive above.
Please log in to comment