LTspice
Production
LTspice® is a powerful, fast, and free SPICE simulator software, schematic capture and waveform viewer with enhancements and models for improving the simulation...
LTspice on Analog.com
I'm trying to deploy LTspice via SCCM.
The installation fails with the message
| The system cannot find the path specified. C:\WINDOWS\system32\config\systemprofile\AppData\Local\LTspice\examples.zip |
If I install by hand it works without even needing that path.
Has anyone else encountered this problem?
Hi OZellmann ,
It appears you have installed LTspice under the user "systemprofile" and LTspice, as instructed, put the library files the "systemprofile" user's appdata. This will not work. In this way, LTspice is not SCCM friendly; or, from another perspective, SCCM is not friendly to just regular old apps with appdata. Nevertheless, we have implemented a workaround, allowing you to install as an admin, i.e. logged in as "system", then, a local user can log in, and LTspice will finish installing its libraries for the local user.
Here's what you need to do:
1. Uninstall LTspice from any machines onto which they were installed under "systemprofile"
2. Run the installer using your normal SCCM install. You will have to use full UI mode, I believe. I did have a way to do it in background, but not sure of the values.
3. You must choose the "Server" option. This installs the software as if you had chosen "All Users", i.e. Root\Programs, but the installer does not expand the local LTspice libraries into appdata.
4. Log out of System Profile.
5. Have user log into their machine and Start LTspice. The LTspice libraries will be expanded into the local user's \appdata\, and LTspice will operate as if the user had installed it.
mike
Hi OZellmann ,
It appears you have installed LTspice under the user "systemprofile" and LTspice, as instructed, put the library files the "systemprofile" user's appdata. This will not work. In this way, LTspice is not SCCM friendly; or, from another perspective, SCCM is not friendly to just regular old apps with appdata. Nevertheless, we have implemented a workaround, allowing you to install as an admin, i.e. logged in as "system", then, a local user can log in, and LTspice will finish installing its libraries for the local user.
Here's what you need to do:
1. Uninstall LTspice from any machines onto which they were installed under "systemprofile"
2. Run the installer using your normal SCCM install. You will have to use full UI mode, I believe. I did have a way to do it in background, but not sure of the values.
3. You must choose the "Server" option. This installs the software as if you had chosen "All Users", i.e. Root\Programs, but the installer does not expand the local LTspice libraries into appdata.
4. Log out of System Profile.
5. Have user log into their machine and Start LTspice. The LTspice libraries will be expanded into the local user's \appdata\, and LTspice will operate as if the user had installed it.
mike