We want to use Canopy in our University. Now i need a option for a silent installation. Hopefully this does exists. ;-) I'm able to install Canopy silent with the msi package with this command:
msiexec.exe /i canopy.msi /q
But the problem is that this is a user install. I can't find any Option to install Canopy for All Users. Have someone any idee?
Thanks a lot!
I have not tried this, but it looks as if adding ALLUSERS=1 should do it. Also, you must explicitly run the command in a terminal with escalated privileges, as described at https://support.enthought.com/entries/23736288-Windows-on-some-systems-admin-users-cannot-immediately-install-for-all-users-
Finally, whether you are installing for one user or many, note that running the MSI only installs Canopy Core. For a user to actually use the Canopy application or Canopy User Python, you must also run the application's initial setup. For scripting this, see this section of the user's guide: http://docs.enthought.com/canopy/configure/canopy-cli.html . You might find the final section most pertinent to your requirements.
Related
I am a complete Noob on Windows and, for the first time of my life, I have to make a Powershell script to install various services on a server. From what I understood, silent installations are made this way:
Start-Process "C:\Path\To\some_installer.exe" -ArgumentList "/some /argument" -Wait -PassThru
But I cant figure a way to identify what the arguments should be for this given .exe. On Linux, I would launch the installer and answer to the prompts one by one to know what the arguments are supposed to be. Then:
(echo arg1; echo arg2) | my command
But since Start-Process does not display a similar behavior (or I am not using it properly), I am lost. I tried the -RedirectStandardOutput but getting nothing in the output file. How do you identify the argument list to provide?
Just like Linux, Windows has many package installation tools. The difference is that the Windows installers are mostly designed for GUI. So there is no standard for CLI. For each installation, you need to check for the installer.
If it's an MSI file, you can use the Microsoft docs. If it's an executable, you need to check for the installer. Many software use common installation wizards, but many of them use custom ones.
If you want to use it like Linux, you can use scoop or chocolatey. You can have a local repository in your network then share. Or just use internet. Then you can have silent installation by default.
Installing Canopy 2.1.9 for Windows 64-bit on Windows 10, and the installer fails immediately after clicking the Install button, with the message "Enthought Canopy (64-bit) Setup Wizard ended prematurely because of an error." Same result using 2.1.8. Same result using the run-as-administrator command line msiexec instructions, same result running the installer as administrator, same result installing for current user or all users.
Enthought support here. Sounds like there's something unusual about your current system status. Most likely would be interference from a 3rd-party anti-virus program, or similar. If temporarily disabling that doesn't help, then please run msiexec /Lv*x canopy-msi.log ... etc..., then zip and send the resulting log, with a link to this SO question, to support#enthought.com. We'll look at it as time permits, though we do not have the bandwidth to help you debug your system setup.
I am going for a silent installation for one of my msi exe. The goal is to get the installer to run silently. I understand and know how to run it silently. The task at hand is that when I run it silently the OS restarts. So I implemented an additional flag to take care of the restart along with my silent flags. Below is the command I run for silent and no restart.
JumpyJackGame.exe /s /v/qn /norestart
The problem I am running into is the .exe does not even run when I add the /norestart command
What project type are you using? And do you use a Suite project (essentially a bundle of several setups delivered as a single setup.exe) or just a regular project wrapped in a normal setup.exe launcher?
See the official help for these different setup.exe types:
Setup.exe and Update.exe Command-Line Parameters
Advanced UI and Suite/Advanced UI Setup.exe Command-Line Parameters
If you use a regular Basic MSI (which you should for its standards compliance), then you might be able to do this:
Setup.exe /s /v"/qn REBOOT=ReallySuppress"
See more samples in the documentation. The REBOOT=ReallySuppress should stop rebooting from "normal causes". A custom action designed to do so may still be able to force-restart the system, but that is terrible design if implemented in such a manner (it should register the need to reboot only).
I will add a link in the morning - when I get time - to a previous answer on the different setup.exe types.
I have installed anaconda. I added the anaconda path to my system variables but each time I fire up ipython notebook or jupyter notebook, it says terminals unavailable.
Has something gone wrong with my installation? I am someone out of academia and I am hoping for the kind help of a pro. Thank you,
Would you by any chance be under windows ?
If so you are out of luck, the ability to have an in-browser terminal is not available on windows for the moment. There is no active plan of making this work on windows either, unless someone with the technical knowledge and a windows machine, improve the underlying package
I am running a silent install of an msi driver install, at the end it has a popup that requires the user to hit "OK". I am unable to see this during silent mode or passive mode, is there a way in powershell that I can execute this and force it to pass-through? Anyway to hit "ok" to this without showing the user it is running will be the best option.
PowerShell simply invokes the installation process. The Windows Installer service is responsible for interpreting the MSI file and handling installation correctly. If Windows Installer is preventing the window from being displayed, then PowerShell won't be able to see it either.
Make sure you're calling msiexec.exe correctly:
msiexec /i <path to MSI> /q /l*v "$env:TEMP\install.log"
That runs it quietly (use /qb for just a simple, passive dialog-based install). If it still pops up a dialog, you need to contact the owner of the MSI package and have them fix it. They're breaking the Windows Installer guidelines and there's really no good workaround for it.