Remote Desktops - UAC control - Why?

[steveb]

Why would running "Remote Desktops" require UAC approval?

There is nothing that you can break on "your" machine when running this tool.

Please remove this "feature" in the next Service Pack as it is not really a security issue.

Please advise if I am mistaken.

 

[Paul Smith]

Why would running "Remote Desktops" require UAC approval?

There is nothing that you can break on "your" machine when running this
tool.

Please remove this "feature" in the next Service Pack as it is not really
a security issue.

Please advise if I am mistaken.

Remote Desktop doesn't require elevation here.

Try running %systemroot%\system32\mstsc.exe directly, does that request
elevation?

--
Paul Smith,
Yeovil, UK.
Microsoft MVP Windows Shell/User.
http://www.dasmirnov.net/blog/
http://www.windowsresource.net/

*Remove nospam. to reply by e-mail*

 

[steveb]

Not remote desktop, Remote Desktop"S" that comes in adminpak.msi.

I use this for the connect to console option, as some apps and patches will hang as a RD session instead of a console session.

 

[Sandeep]

mstsc /console lets you connect to a console.

Sandeep

 

[Guest]

Sandeep, you are avoiding the original question. the Rempte Desktops MMC
allows for access to multiple desktop connections to multiple servers within
a single window. One might argue that this is not unlike tabbed browsing
allows you to have multiple websites open in a single browser window.

I think it is probably not the desktops snap-in causing the UAC prompt, but
rather the launch of mmc.exe itself, which seems to require administrative
priviledges to run regardless of the snap-in open.

 

[steveb]

Correct,

MMC itself can not break you system, but snap-ins used can.

I can see this and why mmc triggers UAC.

I remember when MMC first cam out, MS was telling everyone, "Use MMC, you do not need to write you whole console, just the working
parts."

I wonder how many non-admin programs are using MMC.

 

[Mark Bourne]

I find the opposite, that opening MMC does not ask for admin privileges,
and then some snap-ins don't work properly because they do need it. I've
ended up creating a shortcut to "Computer Management", and checking the
"Run as administrator" box in its Properties > Shortcut tab > Advanced.
You might want to make sure that box is not ticked on the shortcut you
use to launch Remote Desktops.

Mark.