AutoStart 5.4 can not start the process with privilege elevation

I tried two ways to elevate privilege of my process on Windows Server 2008 with AutoStart 5.4

First one is embedding the UAC manifest into my application/process. Direct clicking this application exe can start this application successfully with privilege elevated. -- BTW, my application is UI based, so it can not be started as Windows Service to work around the session 0 problem. With this manifest it is no longer taged as "Virtualized". But this process can not be started by AutoStart with the error "Could not OpenProcess". I am supposing that whether AutoStart has the ability to support privilege elevation on Windows Server 2008? Or can AutoStart handle the UAC dialog that prompt for confirmation before privilege elevation?

Second way is to create one vbs script as following:

Set objSh = CreateObject("Shell.Application")

objSh.ShellExecute "C:\Program Files\××× Inc\××× Server\Routing Manager\×××Rm.exe","", "","runas",1

And invoke this vbs from AutoStart by "Batch Command", process/my application can be started with UAC confirmation prompt successfully. But here comes two problems

(1)Even this process is started up but its process status is red -- Anything I missed?

(2)Why the operation type of "Batch Command" can not be stored? After switch tabs of process setting -- apply button is clicked, the operation type be empty.

I apologize that too many questions together, but such problems do exist in our system and it will affect whether we will need to upgrade the OS. All in all we need to use AutoStart to manage our dual servers and run the processes with elevated privileges.

Thanks

Responses(3)

tribicic

157 Posts

1

November 30th, 2010 02:00

Thanks for the useful info. Regarding the last two questions, I'd say that you may want to set up your own existence monitor to be used instead of built in existence monitor. My experience is mostly based on UNIX environment where I had to use my own existence monitors, so I suspect that on Windows a built in monitor checks the process ID as returned by the system and maybe it is not getting the correct one, if any if set up this way? Either way, your own existence monitor is a valid workaround.

About the batch setting from a drop down disappearing, I can confirm the same. I suspect it might be a problem on AS 5.4. Does it still work, meaning it is a cosmetic problem only or it is being completely ignored? I might try with AS 5.3 later today to verify this.

daniel_vongehr

34 Posts

1

November 30th, 2010 10:00

Hello,

For question 1, I'd agree with Tomislav that AutoStart's default existence monitor may not be picking this process up correctly. Possibly due to the way you are starting it. You may need to create your own existence monitor as he suggests.

For question 2, I believe that this is a known Bug/Defect in AutoStart 5.4. It is currently under investigation in Development. As I understand it, the functionality should still work even though it disappears from the GUI on a close/re-open or tab switch. Please let us know if you are seeing something different.

Best Regards,

Daniel Vongehr

EMC Technical Support

EnvisionPlus

79 Posts

0

November 30th, 2010 18:00

For the second way, yes it works fine. Just a minor GUI problem.

Do you guys have any comments about my first way? Embed manifest and encounter the open process fail problem.

Thanks

View All

No Events found!

Replication Manager

AutoStart 5.4 can not start the process with privilege elevation

Was this post helpful?