Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
Security and Windows Vista A forum for discussion on security issues with Windows Vista. (microsoft.public.windows.vista.security) |
|
LinkBack | Thread Tools | Display Modes |
|
|||
Remote Desktops - UAC control - Why?
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. -- -- Steven http://www.glimasoutheast.org |
|
|||
Remote Desktops - UAC control - Why?
"steveb" wrote in message
... 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* |
|
|||
Remote Desktops - UAC control - Why?
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. -- -- Steven http://www.glimasoutheast.org "Paul Smith" wrote in message ... "steveb" wrote in message ... 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* |
|
|||
Remote Desktops - UAC control - Why?
mstsc /console lets you connect to a console.
Sandeep "steveb" wrote in message ... 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. -- -- Steven http://www.glimasoutheast.org "Paul Smith" wrote in message ... "steveb" wrote in message ... 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* |
|
|||
Remote Desktops - UAC control - Why?
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. "Sandeep" wrote: mstsc /console lets you connect to a console. Sandeep "steveb" wrote in message ... 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. -- -- Steven http://www.glimasoutheast.org "Paul Smith" wrote in message ... "steveb" wrote in message ... 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* |
|
|||
Remote Desktops - UAC control - Why?
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. -- -- Steven http://www.glimasoutheast.org "Onlyodin" wrote in message ... 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. "Sandeep" wrote: mstsc /console lets you connect to a console. Sandeep "steveb" wrote in message ... 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. -- -- Steven http://www.glimasoutheast.org "Paul Smith" wrote in message ... "steveb" wrote in message ... 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* |
|
|||
Remote Desktops - UAC control - Why?
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. steveb wrote: 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. |