Originally posted here by SawPer
Sorry, I think I confused myself!! :]

The only sadness is it only works on Win2003 not on Win2000...

Anyway, what confused me was when looking in TSADMIN, it still shows the remote console session as a RDP session, and the local console session is still "usused", but when looking closer the RDP session took over ID 0, which always is the console..
I guess TSADMIN is also getting some what confused over the whole thing.. hehe!

Started Windows Update locally, connected remotely with two admin connections, then tried a third to simulate you being locked out, then tried the /console option and voila! Took over the local console with Windows Update running in the background, awesome!

Very cool, thanks a lot zencoder!!
I don't think it is actually getting confused, and I don't believe the intent was ever to do a 'shared desktop' (like PCAnywhere). Microsoft already has a tool to do this in Remote Assistance (which is pretty much the same code base as Remote Desktop/Terminal Server). The point of /console is more of a policy issue. IIRC, the default setting for Remote Desktop/TS connections is 2 remote connections max. This can be changed, but I've seen it do some flaky things when too many users are connecting remotely with a full desktop. The /console option let's a Remote administrator connect even when the max. connections has been reached, by giving him the reserved session for the local console.

You folks having trouble will have to read up on the mstsc /? info for how to use it, I don't recall the details, but I consult it myself everytime I need to use this. I don't use anything older than XP/2003 nowadays, simply due to the environment I work in, so I haven't tried it in any other combinations. But it sure beats resorting to a tool like Dameware or VNC, if you need to do something on the fly!