Hi.
MECM environment in a college.
I see this is a NSIS installer but running theexe.exe /S is not firing away on Windows 10.
I had a colleague reproduce this independently. Updating from 4.2
I see the app is fully portable so I am going to copy the directory and some icons by hand. It would be pleasant if the silent install function was repaired.
Thank you
On Windows 10, I was able to successfully silently install Slicer 5.2.2. Since it takes several minutes to install, you will see it silently show up after that amount of time.
PS C:\Users\james\Downloads> ./Slicer-5.2.2-win-amd64 /S
Hi Folks,
Thanks for the reply. We are a MECM / SCCM shop.
Try simulating a MECM deployment by running the installer as nt system.
pstools from microsoft
elevated command prompt; psexec64.exe -i -s cmd.exe
that will launch a new window. whoami will return the system value. slicerinstallexe /S This is where the error occurs. Had another engineer try, too.
I can try the install /wait to see what it does. In the last version the extensions were okay as is.
I also read that this can be a portable app since a current version. I wrote a PS script that basically up and copies everything. However when attempting to install an extension, we are getting
“Extensions install directory is expected to be readable/writable/executable: C:/Program Files/Slicer/NA-MIC/Extensions-31382”
And underneath it says “Check that 3D Slicer is properly installed.”
one more update with permission fix - looks like we have to give explicit read write execute permissions on the folder.
I am guessing it is not fully portable.
The last version we had to install was 4.1.1202102.
Thanks - appreciate everyone.
The application is fully portable, including all data and settings.
However, you need to install in a writable location if you want to allow your users to install extensions (as all the extensions and additional Python packages that they pull in must be all available to all users). It might be possible to remove this requirement (e.g., install additional modules and Python packages in the user’s folder), but it may not be easy to implement this and there has not been very strong demand for it (but you can submit a feature request and see how much support it gets).
If you want prevent your users from from installing extensions then install Slicer into a read-only folder (e.g., in C:\Program Files). You can disable the extension manager in application settings to prevent the extensions manager from showing up in the application. You can pre-install selected extensions by starting Slicer as administrator. Users that have admin access can also launch Slicer as administrator and then install extensions.
Since each user may want to use different set of extensions and settings, I would generally recommend to install Slicer per user. In some institutions a Slicer shortcut is added that launches a script that downloads and installs Slicer in the user’s folder if Slicer is not installed there already.
How your users are expected to use Slicer? Do they need to install extensions? Are your users generally allowed to install any software (applications, Python packages, etc.) and you just pre-install Slicer for convenience?
Install directly to C:/ (e.g., C:/Slicer-5.2.2), which by default is writable by all users. That was the solution that worked for us.