netsh Command not running as FBA Command

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm trying to run a netsh.exe script as an FBA Command at phase 12000. The
components necessary for netsh exist and the script is in the system32
directory. I'm using %11%\netsh.exe as the command and the arguments are exec
ipscript.txt. The script should assign a static IP but doesnt. However, it
works fine from the command prompt after FBA has run. I'm executing other FBA
commands at phase 12000 and they work fine (creating users, assigning to
groups, setting password expiration params, etc). Anyone know what might be
the problem?

Thanks,

Tim Houle
 
Hi Tim

Don't use the %11% variables in the FBA.
Theese values works with TD and CD, but not
during the FBA phases.
Review the package "Set all user account passwordd ages to unlimited" under
www.xpefiles.com / Software.
This gives you an example to start a script during FBA.


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Martin said:
Don't use the %11% variables in the FBA.
Theese values works with TD and CD, but not
during the FBA phases.
Click to expand...

Sounds very very bad. Wasn't this fixed immediately by MS when this
problem occured first? Sounds really crappy.
Review the package "Set all user account passwordd ages to unlimited" under
www.xpefiles.com / Software.
Click to expand...

I tried this package half a year ago but it didn't change my user's
expiring dates. Is it updated now? Until now I disable expiring dates
via the command "acctmgmt /pwdexp [username] disable" in a runonce
script (acctmgmt is unfortunately not found in any XPE packages).
 
Martin said:
Don't use the %11% variables in the FBA.
Theese values works with TD and CD, but not
during the FBA phases.
Click to expand...

Sounds very very bad. Wasn't this fixed immediately by MS when this
problem occured first? I think one should be able to rely 100% to those
things. Otherwise it's presence is worse than not having pathvariables
at all!
Review the package "Set all user account passwordd ages to unlimited" under
www.xpefiles.com / Software.
Click to expand...

I tried this package half a year ago but it didn't change my user's
expiring dates. Is it updated now? Until now I disable expiring dates
via the command "acctmgmt /pwdexp [username] disable" in a runonce
script (acctmgmt is unfortunately not found in any XPE packages).
 
Hi J.S.

I should work.
But use it as an example how to start the script or batch.


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

J.S. said:
Martin said:
Don't use the %11% variables in the FBA.
Theese values works with TD and CD, but not
during the FBA phases.
Click to expand...

Sounds very very bad. Wasn't this fixed immediately by MS when this
problem occured first? I think one should be able to rely 100% to those
things. Otherwise it's presence is worse than not having pathvariables
at all!
Review the package "Set all user account passwordd ages to unlimited"
under
www.xpefiles.com / Software.
Click to expand...

I tried this package half a year ago but it didn't change my user's
expiring dates. Is it updated now? Until now I disable expiring dates
via the command "acctmgmt /pwdexp [username] disable" in a runonce
script (acctmgmt is unfortunately not found in any XPE packages).
Click to expand...
 
....and of course the cmd must be in the image...

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

J.S. said:
Martin said:
Don't use the %11% variables in the FBA.
Theese values works with TD and CD, but not
during the FBA phases.
Click to expand...

Sounds very very bad. Wasn't this fixed immediately by MS when this
problem occured first? I think one should be able to rely 100% to those
things. Otherwise it's presence is worse than not having pathvariables
at all!
Review the package "Set all user account passwordd ages to unlimited"
under
www.xpefiles.com / Software.
Click to expand...

I tried this package half a year ago but it didn't change my user's
expiring dates. Is it updated now? Until now I disable expiring dates
via the command "acctmgmt /pwdexp [username] disable" in a runonce
script (acctmgmt is unfortunately not found in any XPE packages).
Click to expand...
 
Thanks for the response. Your password unlimited component on xpefiles.com is
run at phase 6005. I'm running many FBA commands at default 12000. they all
seem to work fine. If i change them to 6005, what differences will it make?

thanks again,
Tim
 
Hi Tim

Phase 6005 is after security and user generation, but before
second boot, and system cloning phase.

In case, you use the system cloning tool, the batch in phase 6005
will be startet on the machine, before cloning.
In phase 12000 it will be startet after the cloning tool
stopped the fba. So the batch runns after cloning on every machine.
My batch is not machine dependent, so it's a wast of
clonong time in phase 12000.


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Martin,

All my FBA commands work successfully at 12000 except for static IP
assignments using netsh. Could it be that the network connection name has not
been generated yet? the script works fine after FBA. Should i do a runonce?
 
Tim

Do you use the "System Cloning Tool"?
If yes, there are some parametres like:
"RemoveNetSettings"
(Like the Sysprep on XP Pro)


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Back
Top