UAC and Administrator privileges

Thinking back that could have been the case with my instance - unless they (MS) have closed the loophole in the RTM

Barman58 said:

Hi Wally,

The way to get around the admin problem at start-up is by use of the task scheduler.

Create a task to start the program at start-up for the standard user accounts, (I think you will need one for each ), using your credentials, and make sure you select run with highest credentials

Has got me out of similar problems in the past

Thanks Nigel, and sorry for the delay. Busy day today.
I ended up reverting the whole ownership and " Run as Admin" settings, it made my computer slower overall.
Do you guys recommend I try the task scheduling you suggested, given SS's situation? I am running RC 7100.
Tks

I think that this "trick" needs more research.

Theoretically if the task is set up to run the application as the admin user with the correct password and with the highest credentials - it should run without the elevation prompt

If the task is then set to run at the login of another user the access level of the user should not matter

This is I'm sure what used to happen with the "AT" command which the command underneath the task scheduler GUI, Obviously there is the now extra step of the UAC.

Will try to find an app that has the issue and try various task set-ups, though not sure when time will be available - there is also the issue of apps that are written pre UAC and those which are UAC aware - will these behave differently

It may be that this is an oversight, (OK Bug! ), on Microsoft's part - if so I can see this causing major issues in the enterprise where this requirement is a common one

I somehow got it to work. I am not sure how; if the problem was that the tasks were not actually running at all or if they needed to run under Admin privilieges.

First, they were not in Startup, they were Scheduled Tasks to run at log on. They were showing at Scheduled Tasks for the Standard users. I tried to have them run under the Admin account, with highest privileges, didn't work.

Then I went into the Admin, Scheduled Tasks and noticed they had errors, they apparenlty had not run. I then chenged to run under the Admin with highest privilieges, now they are running and they do not pop up anymore at the Standard User log on.

All in all it was a solution. I don't know if applicable in the cases where the task is running normally and UAC is asking for permission under a Standard User, maybe...

Thanks Nigel, thanks SS
10-3

Hi SS
Yes, that is how it is working