Ah, I suppose other options could include:

* modify the registry directly with the new static IP (reg add .....) and then force a restart of the networking service (sc ....) to make it re-read the configuration

* try WMI programmatically to see exactly which API or method is failing and what the error code is

* debug the network properties GUI dialog to see how it sets the static IP (assuming the GUI works) then develop a program using those methods

MHL

On Mon, Jun 3, 2013 at 12:46 PM, George M. Garner Jr. <ggarner_online@gmgsystemsinc.com> wrote:

Does WinPE/WinFE have WMI and/or PowerShell? If so, you could try one of
those:

http://blogs.technet.com/b/heyscriptingguy/archive/2012/02/28/use-powershell-to-configure-static-ip-and-dns-settings.aspx
http://theinterw3bs.com/wiki/index.php?title=WMIC_Commands#Remotely_change_the_IP_to_a_static_IP_.28Index_is_Interface.23.29

WMI and powershell are optional components which may be added. In this particular case I do have both WMI and power shell available and already tried the WMI commands which you suggest, with the same result.

This is my own box that I am testing on, btw. (not the client's system :-) ) so no problem with malware interfering with the commands.

Thanks for responding.

_______________________________________________
Vol-users mailing list
Vol-users@volatilityfoundation.org
http://lists.volatilesystems.com/mailman/listinfo/vol-users