MSI Error 1920 when pushing via SCCM, works fine when "pulled"
Hi all, I'm having an issue that is driving me nuts. I have received an MSI that installs a service. It works fine when I just run it locally on a PC but when I deploy it using SCCM I keep getting this error 1920: "Service ... failed to start. Verify that you have sufficient privileges to start system services." The rest of the MSI seems to install successfully but then rolls back because that service doesn't start.
The service has no dependencies, so missing dependencies can't be the cause.
Anyone had a similar issue or knows how to solve this please?
Thanks!
Answers (6)
Thanks all for your feedback. I don't really have an explanation for it, but I solved the problem by first copying the MSI locally and then launching it from the local folder instead of launching it from the DP.
On your PC you would be running it under the logged in users context. Are you downloading the package to the workstation or running it from a remote share?
If you want to cross check this scenario, run the msi under system user credentials with no user logged in.
Thanks for your feedback, adilrathore! On the pc I'm logged on with an account that has admin rights (it's VMware pc running Windows XP). The MSI is located on a mapped drive that in fact points to a folder on the host pc (so the pc that has VMware Workstation running).
What is the best way of running the MSI under system context with no user logged in?
The limitation here would be to run the MSI from the network location.
You need to first copy the MSI to the PC (just stage it on that workstation) using a network account.... And then it would be easier to run the MSI using the system account.
Have tou tried running the msi locally on the machine using a tool like CMDAsSys.exe, to test a localsystem push?
I don't think the network paths per se are causing problems because then the install wouldn't run at all..
Is it really possible to perform actions on a network resource using the SYSTEM account?
Comments:
-
yes, as long as either the locations are mapped using LocalSystem credentials, or, in an AD environment, the 'Domain Computers' group has access to the location. - pjgeutjens 11 years ago
-
Thanks! This is very helpful. Further I think the the network share should have atleast read permissions for everyone group... - adilrathore 11 years ago
Thanks all for your feedback.
I don't really have an explanation for it, but I solved the problem by first copying the MSI locally and then launching it from the local folder instead of launching it from the DP.