UAC Stopp Autostart of Workplace
We are setting up the new 188.8.131.52. After every login we have to retype the Password for the UAC.
So, Problem is well known, but I do not see a real Solution for that. If I disable UAC for in the Administrator Account, it has no change for the Operatoraccount.
Is there any Solution without disable UAC? We have also about 50Clients, so a GPO would be very nice.
How is ABB doing this for new Plants?
This Problem only if logover setting enabled in Logover Settings aspect
Solution:disabling UAC - useing reg setting
it specifies to set the following:
in above location set EnableLUA to 0.
When the non-administrator user is not added to the impersonate list as explained
in the Windows Settings for Log over and User Account Control (UAC) is
disabled for that user. In such a condition if Log over is enabled and the user
starts the Workplace Application, then the red background on the User Control
tool would appear indicating that the log over is not possible.
Windows Settings for Log over
The Log Over function will not work properly for other users than those with
Windows administrator rights.
To resolve the problem assign the “Impersonate a client after authentication” user
right to the user or user group that should use the logover function. To do this, follow
the steps below:
1. Go to Control Panel > Administrative Tools and then select Local Security
2. Expand Local Policy, and click User Rights Assignment.
3. In the right panel, double-click Impersonate a client after authentication.
4. In the Local Security Policy Setting dialog box, click Add.
5. In the Select Users or Group dialog box, click the user account that you want to
add, click Add and then OK.
For Example: Add IndustrialITUser Group
6. Click OK.
Do as the Workplace App does when clicking the ”Set as autostart” button!
= create a Scheduled Task (trigger=at login of a user) to launch the workplace with appropriate parameters and the ”Run with highest privileges” option enabled.
The above button requires that the workplace was launched with ”Run as administrator” (and only when setting up the auto launch)
See also this thread for remote configuration of auto launch: