Re: Keyboard Madness in TS Environment

I was afraid so, but wanted to make sure that you had seen this.
Since the problem seems to occur on one client device only, and for
all users on that client, I would stop troubleshooting the issue
and simply re-image / reinstall the client from scratch. Not very
satisfying to never know what caused the problem, but probably the
fastest solution.
Otherwise the only thing that I can think of is to call Microsoft
Support.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"cbrunet" <darthkorn@xxxxxxxxx> wrote on 13 jul 2006 in
microsoft.public.windows.terminal_services:

I saw that during my searches. Also not the case as the user
isnt getting capital letters when typing in the TS environment.
It just acts as if the shift key is held down simply when the
d-pad is utilized.

Vera Noest [MVP] wrote:
Check if this applies:

885350 - User connected to Terminal Services must press the
SHIFT key two times to turn off Caps Lock
http://support.microsoft.com/?kbid=885350
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"cbrunet" <darthkorn@xxxxxxxxx> wrote on 13 jul 2006 in
microsoft.public.windows.terminal_services:

I've gone to everything from a most basic keyboard to a full
out multimedia keyboard to a USB keyboard. All with the
exact same results.

Vera Noest [MVP] wrote:
Try switching keyboard anyway, with a different brand if
possible.
I have seen both keyboards and mouses which work 100%
correct on the client but behave irrational in a TS session.
This is especially true for keyboards with some sort of
extended functionality, like a built-in rollermouse.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"cbrunet" <darthkorn@xxxxxxxxx> wrote on 12 jul 2006 in
microsoft.public.windows.terminal_services:

Ii is a workstation computer that has been rebooted
multiple times since. I will give the driver effort a try
though. Thanks for the input.

Brad Pears wrote:
I have seen this behaviour when connecting to a users
session from the terminal services manager. I believe it
only
happened
on the Win2K server though - not the Win2K3 server -
although I'd have to confirm that again... Basically, a
user would
call
for some help, I would connect to their session, then
once I ended my connection, they would complain their
keyboard was
all
whacked out - similiar to what you described. Usually a
reboot
on their end solved the problem...

Likely not any help to you but another thing for you to
think about... Is the user using a different keyboard
driver than everyone else by any chance? Maybe try
installing a differnt
or
reinstalling the keyboard driver? Is it a laptop?? I seem
to have had more problems with the laptop users...Both
our
Compaq
and Dell laptop users have complained about it...

Brad
"cbrunet" <darthkorn@xxxxxxxxx> wrote in message
news:1152124349.010251.15090@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
..
This is far too strange for me.

I have a user who, when in a Terminal Services
environment (ICA/RDP), his keyboard acts as if he
constantly has the 'Shift' key pressed down when using
the directional buttons (but not when typing). When
'NulLock' is turned off, it
acts
normal, but then the NumPad obviously does not work.
So, when the user is typing up documents in Word
through
Citrix,
whenever he presses the directional button, it will
select the text he has written rather then simply move
the cursor. Same happens in a Remote Desktop
environment, wherein the user moves the cursor between
files or folders and it would select them all rather
then just move between them
normally.

1- I dont see it being anything PHYSICALLY wrong with
the keyboard, as it would also affect the local
desktop, not simply the Terminal Service connections.
2- I dont see it being any settings on the local
desktop
for
the same reasons, though I did check sticky keys and
keyboard
settings as my first stop. CAPS LOCK dosent have
anything
to
do with it either as characters written in Citrix
connected Word are still lower-case (i.e. acts normal)
3- I dont think it has anything to do with server
settings, as it would happen with the ICA connection
AND with an RDP
to
my own workstation, which I've RDP'd to from MANY
different terminals before with no problem.
4- It's also not a single profile issue, as any user
logging
into a TS connection from that PC receives the same
type of environment.

At my wits end. Thanks a bunch for the input.
.