Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Sign in to follow this  

Winpe 2.0 and static IP

Recommended Posts

Hi, I'm having trouble getting winpe 2.0 to work with static ip addresses.

My wpeinit.log complains about validation although i successfully validated unattend.xml in WSIM. The output is as follows:

Info WPEINIT is processing the unattend file [x:\unattend.xml]

Warning Validation of WinPE unattend settings failed with status 0x8022000f

Warning Applying WinPE unattend settings failed with status 0x8022000f; ignoring shutdown settings

My unattend.xml file is as follows:

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<settings pass="windowsPE">

<component name="Microsoft-Windows-TCPIP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">


<Interface wcm:action="add">


<IpAddress wcm:action="add" wcm:keyValue="1"></IpAddress>



<Route wcm:action="add">







<Identifier>Local Area Connection</Identifier>





<cpi:offlineImage cpi:source="wim://comp1/images/winpe.wim#Microsoft Windows Vista PE (X86)" xmlns:cpi="urn:schemas-microsoft-com:cpi" />


Anyone have any ideas as to what I may be doing wrong? Thanks!

Edited by khsh

Share this post

Link to post
Share on other sites

I also got the same error trying to run a good validated unattend.xml with wpeinit. Here is what I did however to get a static ip address, mask and gatway running in WINPE 2.0.

From the WINPE 2.0 command prompt run in the following order

netcfg /winpe

wpeutil InitializeNetwork

netsh interface ipv4 set address "Local Area connection" static youripaddress yourmask yourgateway 1

This gets me a static ip in winpe 2.0 you can add dns and wins as well.


Share this post

Link to post
Share on other sites

Can this be automated?

The reason I have this question is b/c we are thinking about going to WinPE 2.0 for automated builds using Altiris and we need a way to have Static IP's that can be changed on the fly.

Currently we have a VBscript that changes our winimage file.. But that will not work with .iso.

any thoughts?

Share this post

Link to post
Share on other sites

I think you could automate this. The following verbage came from the Winpe chm file.

Winpeshl.ini controls whether a custom shell is loaded in Windows PE instead of the default Command Prompt window. To load a custom shell, create a file named Winpeshl.ini and place it in %SYSTEMROOT%\System32 of your custom Windows PE image. The .ini file must have the following section and entry.


AppPath = %SYSTEMDRIVE%\myshell.exe


%SYSTEMDRIVE%\mydir\application1.exe, -option1 -option2

application2.exe, -option1 -option2

Set the AppPath entry to the path to your shell application. The path can be either fully qualified, or you can use environment variables, such as %SYSTEMROOT%\System32\Myshell.exe. The AppPath entry does not support command-line options.

Use the [LaunchApps] section to run applications with command-line options. The applications run in the order listed; separate the name of the application from its options with a comma.

When you exit the Command Prompt window or your custom shell application, Windows PE restarts.

Thus you could create a bat file with the commands I gave at it should do this. For Winpe 2005 we had a .net application that started with the above technique where a user could put in there own static IP address. I can not wait until someone figures out how to get the .net to work with winpe 2.0 then we can use our .net application again.


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.