108 wrote:What kind of a reply was that?
The user attempted to use the published method for disabling UAC and it failed to work; Now he is attempting to troubleshoot the issue. Your reply did absolutely nothing to answer his question or to further the discussion.
Not to be rude but c'mon... This is a complex knowledgebase here with a lot of potential for confusion amongst users. A response like that is little better than frustrating to have spent time reading.
You're completely mistaken. The user did not use "the published method for disabling UAC" at all. The "published method for disabling UAC" would be one provided by Microsoft (feel free to Google); it has unfortunately <b>nothing</b> to do with the DIS_UAC option in UltraVNC. <b>All</b> that option does in UltraVNC is suppress additional UAC prompts after the first one during an installation - the user still needs to authorize the first UAC escalation, and have the credentials to do so. (Yes, if anything, that UltraVNC option should probably have a less confusing name.)
The user <b>still</b> needs Window administrative rights to accept UAC elevations, and again, that is out the scope of anything UltraVNC does.
The original poster is complaining "it still requires the end user to provide administrator details". Of course it does; it's the whole point of "limited user" privileges, even aside from UAC escalation. This where both the OP and you, apparently, are mislead.
So as supercoe very aptly answered, "That's how UAC works, you can't disable it without admin access..."
So to answer your question, that reply was appropriate, if perhaps too short.
