Importing wifi-xml-profiles via OSD TS

[hans.swolfs]

Hi,

I'm creating/testing an OSD TS for our school's laptops and netbooks and I'm stuck at a certain step.

This step should import profiles of our school's wifi-networks so that the laptops & netbooks can automatically connect to them after deployment.

How should this work...

I have 2 xml profiles called "sjib_1.xml" and "sjib_2.xml".

I tried to import them with :

- a batch-file calling : netsh wlan import command (tried them standalone on a laptop and they work). I created a package with a program (the batch-file) and inserted that one in the OSD TS but no joy

- instead of a batch-file, I tried to import them via 2 command-lines in the TS : netsh wlan import profile name="sjib_1.xml" and another one for the sjib_2.xml file.

 

When the TS tries to perform this step, it exits with error "0x8007010B".

 

Any clues would be welcome!

 

This one is for real opposite to the one I mistakenly have posted about Office :s

 

best regards,

Hans

[Peter33]

Hmmmm, rather try "netsh wlan add profile". There is no "import" command.

[hans.swolfs]

strange stuff... must have mistyped it when I was creating the scripts because it's indeed add instead of import.

will test that later and comeback with feedback...

 

Should I insert the %~dp0\ in the filepath of the xml's or shouldn't this be needed?

 

First finish installing SCCM 2012 after having too much problems with my current sccm 2007 setup.

 

Thanks already!

[Peter33]

The %~dp0 is not needed as long you don't use a batch file or a command line task sequence step. These two will start in the home path of the user. So batch files should always contain a "pushd %~dp0" as first line and "popd" as last line.

[hans.swolfs]

Will they also start in the home path if this step is performed during OSD?

Since this is a command-line instruction, there's no other choice than to do it via a batch file of command line TS step right?

[Peter33]

CMD sessions are always executed in the home path of the user running it, also during OSD.

You only need to use the command line step if you want to apply the setting during the PE phase. If the machine is already rebooted to the installed OS you can use a regular "install software" step.