Need to have Admin privileges after WinActivate

[Zog]

I work at a chemical processing company.  I am on the selection team for a new piece of shop floor process control software which will control a number of disparate machines - essentially controlling valves based on other properties (temperature, pressure, other proprietary things.)  We have found a program that except for one thing meets our goals.

We have a foreman 'super console' application which extracts data from many such control programs (not all machines are controlled by the same software).  We like this new potential software because it can replace several other proprietary control programs into one.

When trying to integrate this new potential software into our 'super console' and/or our startup regression test programs (both written in Autoit) we ran into a problem (similar to what is discussed here https://www.autoitscript.com/forum/topic/194860-mouseclick-not-working-after-winactivate/)  The only way I can gain Autoit control of the application is if I run the Autoit code as an Administrator.  For many reasons we do not allow shop floor control software to run in administrator mode.

Has anyone else had this problem before?  Any solutions to try?

Summary

Does not work:

WinActivate("New Proprietary Program")
MouseClick("left,xpos,ypos)

Does work but unacceptable due to security reasons:

#RequireAdmin
WinActivate("New Proprietary Program")
MouseClick("left,xpos,ypos)

 

[argumentum]

13 minutes ago, Zog said:

The only way I can gain Autoit control of the application is if I run the Autoit code as an Administrator.  For many reasons we do not allow shop floor control software to run in administrator mode.

Has anyone else had this problem before?  Any solutions to try?

That is not a problem, rather a solution.
Admin level is god level. User level is not-god level.

No, no way around it.

[mLipok]

17 minutes ago, Zog said:

Does not work:

WinActivate("New Proprietary Program")
MouseClick("left,xpos,ypos)

Does work but unacceptable due to security reasons:

#RequireAdmin
WinActivate("New Proprietary Program")
MouseClick("left,xpos,ypos)

This is the normal Windows security behavior, when accessing the GUI using functions like:
WinActivate("New Proprietary Program")
MouseClick("left,xpos,ypos)

Meaning,
The controlled program and the controlling/automating program must have the same security level for the controlling/automating program to be able to access the controlled program.

In your case 

Lower the security level/runtime environment of the controlled program.
or
Raise this level for the control/automation program.

In your case as you showed to us, the

#RequireAdmin

did the trick
 

Edited 16 hours ago by mLipok

[Zog]

That is, unfortunately, what I determined as well.  The control software does require admin level access, however, once installed it never asks for admin privileges again.  Unfortunately every time I run the Autoit code the #RequireAdmin pragma forces someone with Admin rights to type in their passwords.  Shop foremen NEVER have admin rights.

Is there a way to have Autoit code have a one-time Admin logon then 'carry this forward' for every time it runs?  Somehow this software does that - we do not need to use admin logons after the initial install.  I'd like to have a similar thing for my 'super controller' and startup regression test software. wrottem om Aitpot/

[argumentum]

If use something to make an entry in task scheduler then it  will not ask every time.
 

Spoiler

or make one manually.

[mLipok]

5 hours ago, argumentum said:

If use something to make an entry in task scheduler then it  will not ask every time.

It is an options, but it will be fired at time, and not at demand.

[mLipok]

The best one is to run service which will give you an oportunity to run different process on demand.
But of course at first you must have Admin Rights to install and run such service.

[Nine]

What about a simple IPC ?  Foreman (non-admin) script can ask a IPC server to perform tasks under admin rights.  The server could be launch at logon with task scheduler.

Edited 1 hour ago by Nine