Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / Setup and Deployment / July 2008

Tip: Looking for answers? Try searching our database.

sysprep and USB keyb and mouse support

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Karl - 19 Oct 2007 11:33 GMT
I want to create a hardware independent image with Sysprep and ghost.
I have 2 machine models that cause a problem.
We use Dell Optiplex GX520 and Dell Optiplex 745
Both machines have an USB interface for keyb. And mouse.
Both the machines have the same HAL
When I create an image staring from the Optiplex 745 I end up with NO
keyboard and mouse during mini setup on the Optiplex GX520 and when I start
building the image from GX520 I end up with NO keyb. and mouse on the
Optiplex 745

Can anyone help?
Adam Leinss - 19 Oct 2007 15:43 GMT
> I want to create a hardware independent image with Sysprep and
> ghost. I have 2 machine models that cause a problem.
[quoted text clipped - 7 lines]
>
> Can anyone help?

Same problem here...how long are you letting the sysprep go?  Usually
after 10 minutes when it "locks up" it continues on without a problem
with keyboard support.

Adam
Karl - 21 Oct 2007 12:16 GMT
Hey
The problem was that the pc was blocked on the welcome screen in the mini
setup and I did not have a keyboard or mouse to continue. No matter how long
I waited I did not get any keyboard or mouse.
I have found 2 setting that I can add in the sysprep.inf file so that I can
skip the welcome screen and the EULA screen. The PC immediately starts
detecting the hardware and by the time it asks me to enter the computer name
the keyboard is detected.
This might not be the most perfect solution but it does the trick for me
[Unattended]
    OemSkipEula=Yes
[GuiUnattended]
   OEMSkipWelcome=1

> > I want to create a hardware independent image with Sysprep and
> > ghost. I have 2 machine models that cause a problem.
[quoted text clipped - 13 lines]
>
> Adam
Adam Leinss - 23 Oct 2007 16:33 GMT
> Hey
> The problem was that the pc was blocked on the welcome screen in
[quoted text clipped - 9 lines]
> [GuiUnattended]
>     OEMSkipWelcome=1

Ah, I already have those lines in my sysprep.inf.  That would explain
it.  Once the mini-setup enumerates the hardware, keyboard support is
not a problem.  I think this is "normal" behavior on the Dells.

Adam
Signature

Visit my PC Tech blog at www.leinss.com/blog

keanemeister - 24 Jul 2008 10:19 GMT
Had been banging my head against a brick wall here for days. Created a
image for 50 optiplex 755's. It was driving me crazy because when i go
to the welcome screen in the mini-setup about 60% of the PCs would hav
no funtionality in the keyboard or mouse. By adding:

[Unattended]
OemSkipEula=Yes
[GuiUnattended]
OEMSkipWelcome=1

..to the sysprep.inf file it caused the mini-setup to skip the welcom
screen which i can only presume gave windows that extra few seconds t
pick up the keyboard and mouse. So thanks for solving all my problems
TheChosen - 31 Jul 2008 11:10 GMT
Hay guys,

ive got the same problem here but  i cant solve it with the reason of
keanemeister. Its a Dell Optiplex 330. Anyone got some solutions?

-so long

> Had been banging my head against a brick wall here for days. Created an
> image for 50 optiplex 755's. It was driving me crazy because when i got
[quoted text clipped - 9 lines]
> screen which i can only presume gave windows that extra few seconds to
> pick up the keyboard and mouse. So thanks for solving all my problems!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.