Re: RDP and pcAnywhere

Tech-Archive recommends: Speed Up your PC by fixing your registry

Here are differences that I found between -console and -admin. This applies to "servers" though (not workstations).

-console: Say, I'm physically logging on at a server (in my own account) and I have the My Documents folder opened. Now, I go to a remote computer and do mstsc -v:servername -console to connect to the server using the same account, I will NOT see that My Documents folder opened. I will just see the plain desktop after login. At the physical server, the screen does not say that it is LOCKED or anything (ie. the screen still shows the My Documents opened as-is). If I now log off from the remote computer, my remote session disconnects, but the screen at my physical server remains the same (ie. My Documents folder still there). So, apparently the server created a separate session for me to connect remotely using the -console (or lack of it - hence "ignored" in Vista). Again, this only applies for servers (not workstation). If I use mstsc to remotely connect to a workstation, that workstation WILL show that is is LOCKED.

-admin: Same scenario...I have the My Documents folder opened at the server, but now from a remote computer I do mstsc -v:servername -admin. When connected from a remote computer, I now see the My Documents folder opened as if I were in front of the server. That's one difference. And, here is another difference. At the server, the screen now shows that it is LOCKED; whereas, when using with -console, the screen is NOT locked. If I now click Start | Log Off (at the remote computer) and log off, the physical server will also log off as well. The physical will give me the Ctrl+Alt+Del screen. Again, that's one more difference.

As far as Shadowing goes, I have never used it, and I'll definitely check it out.

Through all these (and again, thanks to your input), I can now say I don't have to rely on pcAnywhere - not because RDC is more powerful. The -admin switch gives enough access to meet my needs. pcAnywhere, however, can give certain accesses that RDC (or RDP) cannot. This is a bit outside of this discussion, but I'll touch on it anyway. For example, after connecting using pcAnywhere, say, I right-click on the Desktop and select Properties | Screen Saver tab. Here I can get access to the Power button where I can change various settings relating to system standby/hibernation, etc. With RDC, the Power button is nowhere to be seen.

I would appreciate any further feedback you might have.

Enjoy your Memorial weekend!
Steve



"Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23q4iEC02JHA.3476@xxxxxxxxxxxxxxxxxxxxxxx
"SP_1" <none@xxxxxxx> wrote in message news:eW82rRz2JHA.5816@xxxxxxxxxxxxxxxxxxxxxxx
Just a quick update...

Based on KB278845, the command is: mstsc -v:servername /F -console

That works (to the extent of getting me connected, yes), but still...I can't
see what is on the screen as if I were there in front of it. In this case,
I'm expecting to see the popup message.

Further searching, I came across this link:
http://forums.firedaemon.com/accessing-shadow-console-via-t397.html

According to this link, instead of using the parameter -console, I would use
the parameter -admin. This time, I do see the message. As the link
mentioned, this is due to the version of my RDC Client. It is 6.01.6001
(with RDP 6.1 Supported).

Perhaps you can help me get the terminologies straight. If I used -console
(or lack there of), I would be connected as a regular session; whereas, if I
used -admin, I would be connected as a shadow. Right ?

Thanks
Steve

The console switch allows you to connect to the console as long as either no one else is logged on to it, or your own account was previously logged on but locked. Test it out. It will give you the same screen if you were previously logged on to the console and you locked it and walked away.

Shadowing allows you to log on to someone else's session. You would need to know the currently logged on session ID. This way you and the other person can use it simultaneously, such as in a support scenario. The other person would need to Ok it when you attempt the connection, unless you set it to otherwise barrel on in, so to speak.

As for the -admin switch, I've never used it. I didn't even know it was a switch until I read that article you mentioned. It states the -console switch is being ignored in Vista, but I've found that is not the case, and it works fine. The -admin switch works as well, but I didn't see a difference, but then again, I was only connecting to a session I had previously had opened under my own account, and have not tested it further to shadow another user's session by barrellin in (forcing a shadow session to connect), as the article implies.

I actually use Remote Desktops, but to use that, you need the 2003 adminpak tools installed, or extract the necessary msc and dll files and register them independently. I actually use that on Vista, even though it is not *necessarily* supposed to work or supposed to do it that way, and supposedly use the RSAT tools, which are not the same. I like Remote Desktops because I can run multiple sessions within the results pane and toggle back and forth between them.

Here are some other switches. You can actually create a connection file for other administrators to use.
http://www.geocities.com/rick_lively/MANUALS/COMMANDS/M/MSTSC.HTM

Ace




.

Quantcast