To better protect those users who are members of the local Administrators group, we implement UAC restrictions on the network. This mechanism helps prevent against loopback attacks. This mechanism also helps prevent local malicious software from running remotely with administrative rights.
The user has no elevation potential on the remote computer, and the user cannot perform administrative tasks. If the user wants to administer the workstation with a Security Account Manager SAM account, the user must interactively log on to the computer that is to be administered with Remote Assistance or Remote Desktop, if these services are available.
A user who has a domain user account logs on remotely to a Windows Vista computer. And, the domain user is a member of the Administrators group. In this case, the domain user will run with a full administrator access token on the remote computer, and UAC won't be in effect.
This section, method, or task contains steps that tell you how to modify the registry. Unlike previous versions of Windows, Vista makes a distinction between the built-in Administrator account and members of the Administrators group. UAC administrators are also members of the local Administrators group, but they run with the same access token as standard users. Need more help?
Expand your skills. Get new features first. A subscription to make the most of your time. Try 1 month free.
Was this information helpful? Yes No. Thank you! However, my customer does not want to grant any of the support people for this application administrator rights. This boils down to the following question:. Can I distinguish between two non administrator user types within my VB application?
If so, what would these account types be and how would I request their access level from the system. I'm not sure if this is what you are looking for, but it was something that I played with once and it may get you closer to your goal. Sorry, I should have tested this on Vista since that is what you indicated you wanted; I primarily work on an XP machine.
I believe that you are bumping into Vista's UAC. I know very little about this subject, but if I understand the documentation correctly, all programs will by default run with just "User" access even if logged in as Administrator in Vista. You can configure your program to request to run with the highest available access level by modifying your program's UAC settings. In VS this is done by modifying the "app. If you are using an older version, this post may help, but I would use.
Based on my research, I would like to suggest that trying the following to narrow down the issue:. You can disable the sharing of the target and share it again with the default settings. To configure the share, you can refer to this:. File and Printer Sharing in Windows Vista. Hope this helps.
Office Office Exchange Server. Not an IT pro? Script Center. Sign in. United States English. Ask a question.
0コメント