Remote Desktop - change in the way I am asked to logon - what's happened ?

[northof40]

Hi - I use Remote Desktop to access a machine on the same LAN. My
machine is XP Pro; the target machine is W2003. Both machines handle
their own logons (ie there's no domain controller involved).

In the last two weeks the way the W2003 machine behaves has changed.
Previously I ran %SystemRoot%\System32\mstsc.exe and what I saw on my
screen was an image of teh other machines logon screen (in other words
the normal logon dialog that I would see if I sat down at that
machines screen).

Now when I run mstsc.exe I got a dialog box appearing on my XP machine
which asks me to provider userid/password. When I provide that I am
then given an image of the W2003 machines desktop after the logon.

I presume that some sort of automatic update to the two machines has
changed the configuration but can anyone tell me how to get it back
the way it was ? Alternatively can anyone tell me the terminology used
for the 'remote desktop with logon handled through the RD session' as
opposed to 'remote desktop logon handled before RD session is
started'.

Thanks

Richard.

 

[Shenan Stanley]

Hi - I use Remote Desktop to access a machine on the same LAN. My
machine is XP Pro; the target machine is W2003. Both machines handle
their own logons (ie there's no domain controller involved).

In the last two weeks the way the W2003 machine behaves has changed.
Previously I ran %SystemRoot%\System32\mstsc.exe and what I saw on
my screen was an image of teh other machines logon screen (in other
words the normal logon dialog that I would see if I sat down at that
machines screen).

Now when I run mstsc.exe I got a dialog box appearing on my XP
machine which asks me to provider userid/password. When I provide
that I am then given an image of the W2003 machines desktop after
the logon.

I presume that some sort of automatic update to the two machines has
changed the configuration but can anyone tell me how to get it back
the way it was ? Alternatively can anyone tell me the terminology
used for the 'remote desktop with logon handled through the RD
session' as opposed to 'remote desktop logon handled before RD
session is started'.

Sounds like you manually installed (because it is not an automatic
installation unless you are connected to somone elses WSUS server) Remote
Desktop Connection Shell version 6.0 (Build Number 6000). You would have
noticed the change in the look of the window that appears pretty quickly.
It was published in December 2006.

http://support.microsoft.com/?kbid=925876

You can remove it from Add or Remove Programs (Control Panel) with 'Show
Updates' checked - Under Windows XP Software Updates...
"Update for Windows XP (KB925876)"

However - it has many features you might like - you may want to learn to use
it before you dismiss it our of hand. You also could have (still can) make
shortcuts with all the information about the connection to each computer
(rdp files) so when you want to connect - you double-click on the
shortcuts... etc.

 

[Vanguard]

Hi - I use Remote Desktop to access a machine on the same LAN. My
machine is XP Pro; the target machine is W2003. Both machines handle
their own logons (ie there's no domain controller involved).

In the last two weeks the way the W2003 machine behaves has changed.
Previously I ran %SystemRoot%\System32\mstsc.exe and what I saw on my
screen was an image of teh other machines logon screen (in other words
the normal logon dialog that I would see if I sat down at that
machines screen).

<snip>

Microsoft came out with version 6 of Remote Desktop. It sucks for 2
reasons: (1) It changes the interface so users now have to learn a
different setup to use it, and: (2) It often fails to push the login
credentials which results in you having to login TWICE!

Under Add/Remove Programs, select to show updates. Then uninstall
KB925876 (might need a reboot). I got returned to version 5.x of
Remote Desktop so I could get my work done rather than Microsoft
wasting more of my time again. I found that two-thirds of the hosts
to which I remote desktop will NOT accept the pushed login credentials
from Remote Desktop v6. However, I can no longer get RD v6 to simply
display the remote host's login screen (i.e., I do NOT want RD to
present its own login window). The result is that I am stuck with RD
v6's login screen (a local window) to enter login credentials that I
know won't work which end up failing on the remote host where I have
to reenter those login credentials again.

There is the option "always ask for login credentials". Stupidly
Microsoft forgot to add an option to "never ask for login
credentials". I don't want to enter my login in a local window. I
don't want the reduce security for servers by having a local shortcut
that someone might be able to use if I get yanked away from my PC. I
don't want the login credentials saved or otherwise cached up
locally.

Unfortunately for workstations at my current employer, they enabled
Windows Updates and used policy to disable me from disabling WU or to
have it prompt me before downloading and installing. This means that
my employer willy nilly farks over my Windows config. They have their
own SUS server for updates. Hopefully they will disable that update
from their SUS server just like they block IE7 from showing up there.
I can uninstall KB925876 but it will just show up again in the next
update which I'm not allowed to disable.

There is no good reason why this "update" wasn't put into the Optional
category (i.e., more fluff). This not a critical or even an important
update. Who gives a gnat's fart about extra fluff added to RD v6 for
Vista and Longhorn since those are obviously not pervasive platforms
yet.

 

[Sooner Al [MVP]]

<snip>

Microsoft came out with version 6 of Remote Desktop. It sucks for 2
reasons: (1) It changes the interface so users now have to learn a
different setup to use it, and: (2) It often fails to push the login
credentials which results in you having to login TWICE!

Under Add/Remove Programs, select to show updates. Then uninstall
KB925876 (might need a reboot). I got returned to version 5.x of
Remote Desktop so I could get my work done rather than Microsoft
wasting more of my time again. I found that two-thirds of the hosts
to which I remote desktop will NOT accept the pushed login credentials
from Remote Desktop v6. However, I can no longer get RD v6 to simply
display the remote host's login screen (i.e., I do NOT want RD to
present its own login window). The result is that I am stuck with RD
v6's login screen (a local window) to enter login credentials that I
know won't work which end up failing on the remote host where I have
to reenter those login credentials again.

There is the option "always ask for login credentials". Stupidly
Microsoft forgot to add an option to "never ask for login
credentials". I don't want to enter my login in a local window. I
don't want the reduce security for servers by having a local shortcut
that someone might be able to use if I get yanked away from my PC. I
don't want the login credentials saved or otherwise cached up
locally.

Unfortunately for workstations at my current employer, they enabled
Windows Updates and used policy to disable me from disabling WU or to
have it prompt me before downloading and installing. This means that
my employer willy nilly farks over my Windows config. They have their
own SUS server for updates. Hopefully they will disable that update
from their SUS server just like they block IE7 from showing up there.
I can uninstall KB925876 but it will just show up again in the next
update which I'm not allowed to disable.

There is no good reason why this "update" wasn't put into the Optional
category (i.e., more fluff). This not a critical or even an important
update. Who gives a gnat's fart about extra fluff added to RD v6 for
Vista and Longhorn since those are obviously not pervasive platforms
yet.

Have you seen this for possible work arounds?

http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...