Sysprep Makes Unwanted Changes to Settings

T

TS

Are there bugs in Sysprep?

I am creating sysprep images of XP SP2 workstations and notice the
builds are not as I configured them after the machines come out of
Sysprep.

Besides the problem of the administrator account profile overwriting
your default profile unless you rename the administrator account, I
noticed another problem.

I wanted all our workstations to have the setting for in Device
Manager network cards, Properties, Power Management to have the box
checked "Allow this device to bring the computer out of standby" to be
checked. (Many of the workstations do not work with Wake On Lan and
we would like to be able to use that function to wake up machines with
a simple ping.)
After setting this option, and sysprepping the machines, the option is
unchecked again after rebuilding from the sysprepped image.

Why is this?

Is there another method to check the box "Allow this device to bring
the computer out of standby" on each machine other than having to log
on to each machine and configure that option on each system manually?
 
J

Johan Arwidmark

Syspreps wipes the network config (this is by design). You may be able
to set this using s script (netsh or wmi) during the in the sysprep
mini-setup process...

regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net
 
T

Torgeir Bakken \(MVP\)

Johan said:
Syspreps wipes the network config (this is by design). You
may be able to set this using s script (netsh or wmi) during
the in the sysprep mini-setup process...
Hi

A registry update is maybe the easiest way to do it. Note that the
registry key path is for my 3Com 3C920 network card, it will be
different for other network cards/drivers.

Doing a registry monitoring/before-after difference comparison, this
is what was set for me when checking the box "Allow this device to
bring the computer out of standby":

Under the key path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class
\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001

the value "PnPCapabilities" (type REG_DWORD) was created with a value
of hexadecimal 20 (32 decimal).
 
D

Darrell Gorter[MSFT]

Hello,
SP2 includes powercfg.exe.
You should be able to use that to change the wake settings.
Powercfg /deviceenablewake
/DEVICEENABLEWAKE <devicename> enable the device to wake the system
from a
sleep state. <devicename> is a device retrieved using
the '/DEVICEQUERY wake_programmable' parameter.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
 
T

Torgeir Bakken \(MVP\)

Darrell said:
Torgeir said:
A registry update is maybe the easiest way to do it. Note that
the registry key path is for my 3Com 3C920 network card, it will
be different for other network cards/drivers.

Doing a registry monitoring/before-after difference comparison,
this is what was set for me when checking the box "Allow this
device to bring the computer out of standby":

Under the key path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class
\{4D36E972-E325-11CE-BFC1-08002bE10318}\0001

the value "PnPCapabilities" (type REG_DWORD) was created with a
value of hexadecimal 20 (32 decimal).


Hello,
SP2 includes powercfg.exe.
You should be able to use that to change the wake settings.
Powercfg /deviceenablewake
/DEVICEENABLEWAKE <devicename> enable the device to wake the
system from a sleep state. <devicename> is a device retrieved
using the '/DEVICEQUERY wake_programmable' parameter.

Thanks,
Darrell Gorter[MSFT]
Hi

Great tip, Darrell! I tend to forget about powercfg.exe...
 

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