MSI Installer fails silent installs as SYSTEM

Question

Hi, 
 We're trying to deploy the LTSpice software (the MSI edition) with the All Users configuration. 
 Launching the installer via GUI on the device and selecting All Users works. 
 Deploying it in bulk (silently, etc.) via the SYSTEM account fails with the following error. The icons briefly appear on the desktop, before rolling back on failure. 
 Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4967.tmp, Entrypoint: OnExpandArchConfig MSI (s) (F4!2C) [15:51:32:795]: Product: LTspice -- The system cannot find the path specified. 
 C:\WINDOWS\system32\config\systemprofile\AppData\Local\LTspice\examples.zip 
 The system cannot find the path specified. 
 C:\WINDOWS\system32\config\systemprofile\AppData\Local\LTspice\examples.zip CustomAction AI_ExpandArchConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

GErgueta · Answer

Hi, 
 The LTspice installation makes use of two directories in Windows: one for the application and the second one for the libraries. Both directories are under the "user id" "%APPDATA%" ( as an example typically " C:\Users\USERNAME\AppData"). 
 As you can see from the reported error, your process is trying to make use of a directory that does not exist. If the script is meant to provide for a given "user", it will have to be aware in the location of those directories for the individual user who will run LTspice. Be aware that LTspice and its installation are making use of "%APPDATA%" as defined by Microsoft and the previous paragraph..

GErgueta · Answer

As answered before. The current "msi" is built for individual users to install. It is not implemented for what you are requesting. I understand you would like to be able to install via SCCM, a feature to be considered but currently not supported.

raju487068 · Answer

Create an mst. Use the custom action called AI_ExpandArchRollback and set the directory to a temp folder which is accessible to all users. I was able to deploy it using MECM.