UAC - User Access Control

Question

Jkistner

UAC - User Access Control

We support many clients that do not have local admin rights on their machine. We have setup the Meeting Manager with SkySwitch to support those remote clients, however, when our clients need an admin change, or login to their UAC, that form hides itself remotely, and is only available to the remote viewer. We do not want to tell our clients the password, but have them connect with us for a remote session to install hardware or software on the machines as a service to them.

Do you have options we can change the Meeting Manager rights to be able to allow viewing access to this admin rights?
Please let me know.

John Kistner
John.Kistner@SkySwitch.com
817-898-7310

Status: Open Dec 18, 2017 - 04:08 AM

Troubleshooting

Comments (0) | New Comment

Do you have the same question? Follow this Question

Answer this question Report it

2answers

Answers

Bruce Maigatter

Dec 18, 2017 - 05:07 AM

Hi John,

In order to view the UAC, remote viewers needs to give TurboMeeting admin priviledges at the beginning of the remote support session. Without local admin rghts, these clients have no way of doing so. Unfortunately, there is no other way for Turbomeeting to view the UAC or make admin changes.

0

Report it

Comments (1) | New Comment

RHUB Support

Dec 18, 2017 - 07:29 AM

Hi! John,

The remote Meeting Manager client will show the "Run as admin" button in this case. Click the button and you can input the admin credential. Then the client will restart and you can remotely handle UAC from there.

Regards,

John

0

Report it

Comments (10) | New Comment

By

sensiblecinema

on 4/18/2018 12:11:09 PM | Like (0) | Report

Run as admin fails with user name or password error about half of the time. It has always done this and I have been a user for 10 years.

By

RHUB Support

on 4/18/2018 1:25:58 PM | Like (0) | Report

As I told you over phone, this is not a common case among our customers. TurboMeeting may have some conflict with your product or a third-party product your customers commonly use. We need to investigate it and let's work on it.

Regards,

John

By

sensiblecinema

on 4/18/2018 3:48:53 PM | Like (0) | Report

There's nothing there but Windows and it still does it. I get new machines in all the time. First thing on them is TurboMeeting. They all have Windows Defender with defaults. I will get with you as soon as I have a machine doing it or I have a cooperative customer.

By

RHUB Support

on 4/23/2018 11:48:38 AM | Like (0) | Report

As a follow up to this discussion thread, we have tried various ways to fix the issue and have not resolved it. Finally we are allowed to access the user machine and found the machine is an embedded Windows. An embedded Windows is not a full-version of Windows and it can miss some critical components supporting this function. Unfortunately, we do not know what it is missing at this stage.

By

sensiblecinema

on 4/23/2018 11:50:28 AM | Like (0) | Report

Believe me, that is not the problem. I have one sitting right by me that works perfectly. Two thirds of the machines in the field work perfectly. ALL our systems are embedded systems.

By

sensiblecinema

on 4/23/2018 4:29:08 PM | Like (0) | Report

So I am happy to report that deleting and recreating the Windows admin user account in question solved this issue. Some sort of corruption in the account itself was the cause even though we were always able to use that account when logging in locally. Since so many of the machines are set up using the same .ISO image, many machines we have in the field have a corrupted version of that administrator account. I will be replacing those bad accounts as I encounter them going forward.

By

RHUB Support

on 4/23/2018 4:53:11 PM | Like (0) | Report

Thank you for sharing the solution! However, this still does not explain why some machines in the field work for a whole and then do not work. The same trick applies to those machines also?

By

sensiblecinema

on 4/23/2018 5:46:06 PM | Like (0) | Report

I suppose some of the accounts may have become corrupted by an update or I am simply mistaken. I used the same .ISO as three I just sent out to the field and that new machine I imaged had the same issue. So the account was corrupt when it left here.

By

MTANDS

on 2/2/2022 11:42:33 AM | Like (0) | Report

THis is still a problem in 2022. While connected to the machine in the limited account the option for run as admin is selected but the UAC comes up and will not allow credentials to be entered without the admin password being entered.

By

sensiblecinema

on 2/2/2022 11:53:15 AM | Like (0) | Report

Well in my case I was entering the admin account credentials and it was saying it was incorrect when it wasn't. The faulty admin user account, which in all other respects worked fine, was to blame. You could log in to the account using the same credentials that just failed through TM. In my case I just deleted that user and created a new admin user and the dialog in TM accepted the credentials just fine. I can't say TM was to blame for this, but recreating the admin account and deleting the bad one did the trick. I haven't seen one revert back to not working again I must say. My chief complaint was that I imaged 100 machines with the bad user account and had to replace each one at a time. Ugh!

Add New Comment

Answer this question

Share Your Own Experience & Expertise

We look to ensure that every question is answered by the best people with relevant expertise and experience, the best answers include multiple perspectives. Do you have relevant expertise or experience to contribute your answer to any of these commonly asked questions?

Run as admin fails with user name or password error about half of the time. It has always done this and I have been a user for 10 years.
As I told you over phone, this is not a common case among our customers. TurboMeeting may have some conflict with your product or a third-party product your customers commonly use. We need to investigate it and let's work on it.

Regards,

John
There's nothing there but Windows and it still does it. I get new machines in all the time. First thing on them is TurboMeeting. They all have Windows Defender with defaults. I will get with you as soon as I have a machine doing it or I have a cooperative customer.
As a follow up to this discussion thread, we have tried various ways to fix the issue and have not resolved it. Finally we are allowed to access the user machine and found the machine is an embedded Windows. An embedded Windows is not a full-version of Windows and it can miss some critical components supporting this function. Unfortunately, we do not know what it is missing at this stage.
Believe me, that is not the problem. I have one sitting right by me that works perfectly. Two thirds of the machines in the field work perfectly. ALL our systems are embedded systems.
So I am happy to report that deleting and recreating the Windows admin user account in question solved this issue. Some sort of corruption in the account itself was the cause even though we were always able to use that account when logging in locally. Since so many of the machines are set up using the same .ISO image, many machines we have in the field have a corrupted version of that administrator account. I will be replacing those bad accounts as I encounter them going forward.
Thank you for sharing the solution! However, this still does not explain why some machines in the field work for a whole and then do not work. The same trick applies to those machines also?
I suppose some of the accounts may have become corrupted by an update or I am simply mistaken. I used the same .ISO as three I just sent out to the field and that new machine I imaged had the same issue. So the account was corrupt when it left here.
THis is still a problem in 2022. While connected to the machine in the limited account the option for run as admin is selected but the UAC comes up and will not allow credentials to be entered without the admin password being entered.
Well in my case I was entering the admin account credentials and it was saying it was incorrect when it wasn't. The faulty admin user account, which in all other respects worked fine, was to blame. You could log in to the account using the same credentials that just failed through TM. In my case I just deleted that user and created a new admin user and the dialog in TM accepted the credentials just fine. I can't say TM was to blame for this, but recreating the admin account and deleting the bad one did the trick. I haven't seen one revert back to not working again I must say. My chief complaint was that I imaged 100 machines with the bad user account and had to replace each one at a time. Ugh!

UAC - User Access Control

2answers

Answers

Share Your Own Experience & Expertise

Browse by Topic

Recently Active Members

Tools