WinXP OEM not saving network settings across Sysprep -reseal...

M

Midi

I'm working with XP OEM, and the end resulting computer configuration
needs to have a specific static IP address. I've tried including the
network adapter settings in unattend.txt, winnt.sif, and sysprep.inf
to no avail. I've also tried running Sysprep -factory, changing the
settings, then doing a Sysprep -reseal... EVERY time it resets to
obtaining a DHCP address automatically. I need it to keep the static
address. Can you tell me what I need to be doing, or what I'm doing
wrong?

Here are the details:
The network adapter (which I cannot swap out) is NOT included on the
default Windows CD. I have to install the drivers either with an
installation program or via a floppy. Ergo, I'm running the Windows
XP installation off of the CD since I have no network connectivity on
the box (and cannot add any) until the driver gets installed. Once
the XP installation is completed, I then install all my drivers, all
my user-end software, and do a Sysprep -reseal for disk duplication.
It would be BEST if there were a way to ensure the settings would
stick from this point on, as all the boxes need to have the same
identical network settings.

Anyway... after the disks are duplicated, I'd like to put the disks in
their respective PCs, type in their individual keys, activate Windows
XP for the end user, and then run Sysprep -activated -reseal so that
the end user still has to accept the Windows license agreement, but
doesn't have to go through the steps of activating the product.
Buuuut... the end user needs to receive the box with the
pre-configured static IP address for the network adapter, without the
end-user doing anything.

Can anyone help?
 
K

Kevin Anderson [MSFT]

Midi,

Sysprep does not keep static IP information. Please check out: Q271369 -
Statically-Entered TCP/IP Settings Are Not Present After Sysprep
http://support.microsoft.com/default.aspx?scid=kb;en-us;271369

You can use NETSET.EXE to enter in your IP address. This can be done with a
login script or in your GUIRUNONCE key in the registry.

KevinAnd [MSFT] - "This posting is provided "AS IS" with no warranties, and
confers no rights."
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top