KACE Product Support

Imported wireless profile into Kace and got it to work.  We use AD server 2003 with Windows 7 machines, and WPA2 Ent/AES

Export wireless profile from known working machine:

netsh wlan export profile name="SSID"

Create online shell script and add the exported XML file as a dependency.

Under script text add:

Netsh wlan add profile filename="exported .xml filename/dependancy filename"

Change script file name to .bat extension

Hope this helps

 

 

Thanks everybody for the great information. Here is how I was able to get this to work as a post-install task:

On a computer which has the wireless priviles you want, open a privileged command prompt and export the profiles to a folder. In this example, I used c:\wlan

"netsh wlan export profile name="ABC" folder=c:\wlan key=clear"
*you will not be able to export the key unencrypted if you are not running an elevated command prompt

Once you have this done for the profiles you want, create a text file which you will save as a .bat file, in this case I named it wlan.bat

mkdir c:\wlan
copy * c:\wlan
cd c:\wlan
netsh wlan add profile filename="Wireless Network Connection-ABC.xml"
netsh wlan add profile filename="Wireless Network Connection-DEF.xml"
netsh wlan add profile filename="Wireless Network Connection-GHI.xml"
netsh wlan add profile filename="Wireless Network Connection-JKL.xml"
cd c:\
rmdir c:\wlan

Place this file in the folder you exported the files to, and highlight the profiles and .bat script and create an zipped archive. Add a post-install task to install an application. Upload the .zip archive, and the command line is wlan.bat

There may be better ways of doing this, but since we don't use Active directort, this is a huge time saver when I deploy machines to different remote school sites.

Hope this helps.

Are these registry settings that you need to change?

hutcha,

Are you wanting to use Windows 7 native tool to manage your wireless settings or a 3rd party configuration tool? Lenovo's Access Connections, for instance, is a "software utility for your computer that manages your network connectivity at multiple locations through location profiles."

If you use a 3rd party tool, in most cases, you can install it on a clean machine and create the profile or configuration, saving it to a network share. At this point, you should be able to run your deployment of the tool then import the profile for later use on the laptop. For example, Lenovo allows the use of a command line, "<network path> \qctray.exe/imp <location profile name>" All this could easily be scripted silently for any deployment method.

If you decide to use native network connections in 7, I'm not sure if 7 still stores wireless information in the registry. I believe 7 stores the information in .xml files under the following location:

c:\ProgramData\Microsoft\Wlansvc\Profiles\Interfaces\Interface Guid

You can extract the .xml files from a demo/clean machine that you've setup and try to copy them to a new machine, but I'm not sure if you can transpose the encrypted key material to other machines. I have not personally attempted to deploy our organization's wireless profile to a Windows 7 machine, but the time will come soon.

I could be way off on this information, but I hope it helps get you pointed in the right direction.

Rich

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).

Hi,

I've enabled 802.1x in Kace using a script. Here's how I did it.

1 I verifed the dot3svc was running
2) on Success I ran a batchfile which delivered the settings:

Here's the batch file portion

netsh interface ip set address "Local Area Connection" dhcp >> logfile.log
netsh interface ip set dns "Local Area Connection" dhcp >> logfile.log
sc config Dot3svc start= auto >> logfile.log
net start Dot3svc >> logfile.log
netsh lan add profile filename=lan.xml >> logfile.log


The xml file was exported from the system using this command:

netsh lan export profile folder=PathAndFileName [[interface=]InterfaceName]

Hope this helps,

M

I'm doing this through Group policy. You will need to set this through a windows 7 or Server 2008 system. Go to Computer Configuration>Policies>Windows Settings>Security Settings>Wireless Netowork (802.11) Polices and create your new policy there. Remember to create it for Windows XP or Vista/7 depending on the OS you are running.