In the following post:
http://forum.voidtools.com/viewtopic.ph ... =768#p2801
a Service/Client configuration is mentioned that allows running everything without administrator privileges. Can somebody tell me how to enable it?
Alternatively, is there a way to run two instances of everything:
1. One (hidden) with admin privileges in the background that monitors the volume and fills the database
2. One (visible) with user privileges which uses the database provided by the first.
I tried the above an linking them via ETP but that requires sharing the entire hard drive as windows share to be able to open any found files.
How to use Service/Client configuration
How to use Service/Client configuration
Last edited by marvin1 on Wed Feb 13, 2013 4:57 pm, edited 1 time in total.
Re: Hwo to use Service/Client configuration
It has not been released yet.a Service/Client configuration is mentioned that allows running everything without administrator privileges. Can somebody tell me how to enable it?
For now, Everything is administrative use only..
Re: How to use Service/Client configuration
Thanks for the answer. I know implementing a service/client architecture is a pain...
May I suggest an alternative, easier to implement solution?
Everything could check on startup under which user account it is running. If it runs as LocalSystem (i.e. as a service) it could launch any child process (e.g. for opening a found file) as the currently logged in user. The implementation effort would be much less than for a service/client architecture.
Instead of just starting a process, the procedure would be as follows
1. Use WTSGetActiveConsoleSessionId to get the access token of the currently logged in user. (http://msdn.microsoft.com/en-gb/library ... 85%29.aspx)
2. Use DuplicateTokenEx to derive a new access token. (http://msdn.microsoft.com/en-us/library ... 85%29.aspx)
3. And finally start the process as the currently logged in user with CreateProcessAsUser and the derived token. (Must be LocalSystem to do this!) (http://msdn.microsoft.com/en-us/library ... 85%29.aspx)
Let me know if there is anything I can do to help. I would love to allow my users access to Everything.
May I suggest an alternative, easier to implement solution?
Everything could check on startup under which user account it is running. If it runs as LocalSystem (i.e. as a service) it could launch any child process (e.g. for opening a found file) as the currently logged in user. The implementation effort would be much less than for a service/client architecture.
Instead of just starting a process, the procedure would be as follows
1. Use WTSGetActiveConsoleSessionId to get the access token of the currently logged in user. (http://msdn.microsoft.com/en-gb/library ... 85%29.aspx)
2. Use DuplicateTokenEx to derive a new access token. (http://msdn.microsoft.com/en-us/library ... 85%29.aspx)
3. And finally start the process as the currently logged in user with CreateProcessAsUser and the derived token. (Must be LocalSystem to do this!) (http://msdn.microsoft.com/en-us/library ... 85%29.aspx)
Let me know if there is anything I can do to help. I would love to allow my users access to Everything.