Guest
[Entry]
"Was looking for a method of opening a third party security program as Administrator on system startup, (several of its features require it be started in Admin mode for the features to function as configured).
Here's the process worked through to arrive at the desired result:
Changed the application launch properties to 'Run as Administrator': FAIL #1
Created a desktop shortcut with Admin privileges and added it to the 'Startup' group. While the application opened, it did not open in Administrator mode: FAIL #2
User Task Scheduler to open it on system start (using the method provided by the winaero blog) but as the application prompted a UAC question, it wouldn't load: FAIL #3
Lost an hour of life downloading, installing and working through 'Microsoft Application Compatibility Toolkit': FAIL #4
Won't class this as a failure, but looked at UAC Trust, found it didn't address the question posed here.
At this point, somewhat invested in the, '15 minute job' now morphed into, 'Day 2' status. Felt the needed components were at hand but was blind to them.
Reassessed the parameters of the problem and employing the Kalashnikov engineering rule #1 (whether the mechanism is clean or dirty, it should work) reconsidered each known element, not looking for what was missing, but for what parameters could be altered without shifting the desired goal, the 'automatic start of a 3rd party app in Admin mode'.
Returned to the Task Scheduler, reworking task switching the Trigger from on system startup to on log on and on the next login, the application started, in Admin mode. Huzzah! Success!
Kudos to winaero for providing the comprehensive visual and written documentation. If I weren't technically oriented, I would have tried their Tweaker. It's what I'll use on the Windows 10 systems."
|
