From within a service I am attempting to fork off a msiexec command (using createprocess) that will do a silent install. What I have noticed in my attempts are the following:
1. With the service running under the localsystem account, the msiexec process will fail and report error #1603 [a fatal error occured during installation] and MSI error number 2103 [could not resolve path for shell folder].
2. With the service running using an admin user account msiexec command finishes successfully.
It would seem that since the localsystem account does not have access to shell resources and thus cannot run msiexec? Has anyone successfully been able to call msiexec from a service that is using the localsystem account?
Any help is greatly appreciated,
Gabe
1. With the service running under the localsystem account, the msiexec process will fail and report error #1603 [a fatal error occured during installation] and MSI error number 2103 [could not resolve path for shell folder].
2. With the service running using an admin user account msiexec command finishes successfully.
It would seem that since the localsystem account does not have access to shell resources and thus cannot run msiexec? Has anyone successfully been able to call msiexec from a service that is using the localsystem account?
Any help is greatly appreciated,
Gabe