Sysprep changes settings (WLAN for instance)

[Jason Breeze]

Hi group,

First off, thanks in advance for any help with this topic. I don't believe
there is an answer for it, but it never hurts to ask (usually right?).

Onto the question: after running sysprep on a WinXP system, then rebooting
and going through the mini-setup, I notice two things:

1. the Wireless Zero Configuration settings for the wireless card on the
system are erased. For instance, I have our company SSID programmed into
the wireless card, after running sysprep and rebooting the settings are
gone. Kind of annoying when I need to re-image 25 systems and then have to
immediately turn around and enter the SSID on each one . How can I get
them to stay?

2. the same goes with the System Restore feature. I find it annoying to
have it enabled in a business enviornment so I'd like to have it disabled.
However, Sysprep, then run through mini-setup, and bam it's enabled again.
Anyway to keep it disabled after Sysprep is ran?

Thanks again for any help, it's appreciated!

Jason Breeze

 

[Amir Miller]

Hi,

I had a similar problem (different settings of network components) and I
added a runonce script to configure the stuff I needed.
You can take a look at netsh command and see if you have the options there,
and if not you can use WSH with VBScript. You can find reference in technet:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp

Good luck,

Amir.

 

[zeraphis]

I found this fix for the system restore within PC Review forum.
Just want to share it with you incase you had not found it yet. It work for me.

mendes9 wrote:
> Hello, on my XP image, I turn off system restore but after the pc is
> imaged and sysprep runs, it turns on System Restore. On my image, I
> have turned off System Restore, and we are using a local group policy,
> and I have turned it off there also, but everytime after sysprep runs
> when setting up a new pc, system restore comes back on ... anyone know
> why?


Yes, I have noticed the same annoying behavior. I suspect it's a bug in
Sysprep, but haven't pursued it because I came up with a workaround.

Try putting the following command in the [GuiRunOnce] section of your
sysprep.inf file:


wmic /namespace:\\root\default path SystemRestore call Disable
%SystemDrive%\


(all on one line)


Let me know if this works for you.


--
Bill Stewart

 

[gob4up]

*I found this fix for the system restore within PC Review forum.
Just want to share it with you incase you had not found it yet. It
work
for me.

Hello, on my XP image, I turn off system restore but after the pc is

imaged and sysprep runs, it turns on System Restore. On my image, I

have turned off System Restore, and we are using a local group policy,
and I have turned it off there also, but everytime after sysprep runs

when setting up a new pc, system restore comes back on ... anyone know
why?

Yes, I have noticed the same annoying behavior. I suspect it's a bug
in

Sysprep, but haven't pursued it because I came up with a workaround.

Try putting the following command in the [GuiRunOnce] section of
your
sysprep.inf file:


wmic /namespace:\\root\default path SystemRestore call Disable
%SystemDrive%\


(all on one line)


Let me know if this works for you.

 

[gob4up]

Hello, thanks for this tip...it worked. I also see anohter annoying
feature with the sysprep. I noticed the startup/recovery time changes
as well as any network settings like deselecting file/print etc.

Do you have any solution to this??


Thank you,
PRP.

*********************************************************

*I found this fix for the system restore within PC Review forum.
Just want to share it with you incase you had not found it yet. It
work
for me.

Hello, on my XP image, I turn off system restore but after the pc is

imaged and sysprep runs, it turns on System Restore. On my image, I

have turned off System Restore, and we are using a local group policy,
and I have turned it off there also, but everytime after sysprep runs

when setting up a new pc, system restore comes back on ... anyone know
why?

Yes, I have noticed the same annoying behavior. I suspect it's a bug
in

Sysprep, but haven't pursued it because I came up with a workaround.

Try putting the following command in the [GuiRunOnce] section of
your
sysprep.inf file:


wmic /namespace:\\root\default path SystemRestore call Disable
%SystemDrive%\


(all on one line)


Let me know if this works for you.