Win2K Sysprep: laptop keyboard issue...

[Ed]

I've created a new base image for Sysprep that works one
every desktop within my company. Because our company
spans a couple of time zones we have a prompt to
the 'tech' to enter the correct timezone when the plug and
play portion of the sysprep process is complete. This is
where the trouble starts. Testing on all our laptops, the
keyboard and mouse are non-responsive, which means we
cannot finish the sysprep process. I have older images
that work fine, but do not encompass as many hardware
models.

Has anyone come across this? And how did you resolve it?

 

[Daniel Chang [MSFT]]

While there are not a lot of details available in your post, it's hard to
hazard a guess.

What kind of laptops are you experiencing this problem on?

How did you create your base image? Slipstreamed installation? of what OS?

What drivers are you including in your OemPnPDriversPath?

Are you using the -pnp switch?

Since your older images don't have this problem, I'm inclined to believe
it's something special you've done in this particular base image build.
--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.


: I've created a new base image for Sysprep that works one
: every desktop within my company. Because our company
: spans a couple of time zones we have a prompt to
: the 'tech' to enter the correct timezone when the plug and
: play portion of the sysprep process is complete. This is
: where the trouble starts. Testing on all our laptops, the
: keyboard and mouse are non-responsive, which means we
: cannot finish the sysprep process. I have older images
: that work fine, but do not encompass as many hardware
: models.
:
: Has anyone come across this? And how did you resolve it?

 

[Ed]

Laptops:
Toshiba 40XX, 42XX, 43XX, 46XX, 6000 & 6100, IBM R32, T30,
R50 & T41 series' are all experiencing this issue. I have
zero laptops that seem to work, but I have over 15 desktop
units that work perfect from this sysprep image.

Creation:
Standard installation with no drivers except what Window
2000 w/SP 3 built in provides. The base hardware used for
the creation of the base image is an NEC Direction SP
8350. I've attempted to add SP4 to the base image to see
if this affects the build with no change to the end result.

Sysprep:
I am using the identical 'sysprep' structure and files
that I use with the older base image. Drivers, folder
content and sysprep.inf have not changed. Using the
default sysprep.bat with the -pnp command.

I've attempted to build the base image several different
times attempting to leave out or possibly add things to
the process and nothing seems to resolve this issue. I
really find it strange that a desktop will build 100%
correct with this troubled image, but the second I try to
build a laptop I loose the keyboard and mouse during the
mini-setup process. This prevents me from saving the
settings and rebooting the system to get to the Windows
GUI. Since we have locations across time zones we have to
prompt for the time zone during the mini-setup process to
allow other apps to run correctly once the Windows GUI is
loaded...


I've also attempted to search the knowledgebase and forums
to find similar issues, the only ones I've found are
related to USB or the enhanced keyboards after the Windows
2000 GUI has been loaded and running. At this point I
can't get that far because the mini-setup of sysprep
doesn't detect the mouse and/or keyboard.