Will there be MSI deployment packages available for Rhino 6?
We’re currently not planning on it. There are four or five MSIs embedded in the EXE and chaining them together with the right settings isn’t easy. However, you can fully automate the EXE installer using these instructions: https://wiki.mcneel.com/rhino/installingrhino/6
Is there a reason the EXE doesn’t work for you?
I’m having problems with the EXE-installer, does not pick up:
and does not handle Pendingreboot state correctly.
I prefer being fully in control when creat installation package, so I want to prefer MSI deployments.
I can use: rhino_en-us_6.5.18155.13161.exe -layout
then I have all prereqs in Redist folder
put these Redist packages in SCCM
then with Wix Toolset (http://wixtoolset.org/) I use:
dark.exe “C:\Temp\rhino_en-us_6.5.18155.13161.exe” -x “C:\Temp\Output”
and will have all MSI’s in C:\Temp\Output\AttachedContainer
When I install Rhino.msi then it looks OK,
Do I need to install en-us languagepack LanguagePack.msi (only need English) and Rhiexex.MSI?
The installer does as little as possible to make Rhino run (and it does a lot). All the redistributable packages, and all the appropriate MSI files for the language files your users will run must be installed. Yes, RhiExec needs to be installed.
Can you tell me more about what doesn’t work with “pendingreboot” state?
I understand your desire to be in control. Please also understand that that control requires understanding and responsibility to do things properly. We don’t document the process of doing what you’re doing because, frankly, it changes from release to release, and the EXE file handles it for you. I discourage you from using the results of layout to do the install, but cannot prevent you from doing it. If you run into problems with things not working because you’ve chosen to do the deployment by hand, please don’t be surprised if we can’t help you get things working in Rhino.
As for SEND_STATISTIC and ENABLE_AUTOMATIC_UPDATES - these parameters only apply to the installation itself. They are not used to disable these features in Rhino during installation. If you want to disable automatic updates and statistics, it needs to be done per-user in Options. You can also disable the McNeel Update service to prevent Rhino from being able to check for updates.
I started to use the EXE (that’s also our preferred way of putting it in SCCM) but when using the bootsstrapper.exe it happened that it runs without error (log files show install result code = 0) but Rhino was not installed. After a reboot running again and then it worked. I managed to deal with this behaviour by using the MSI’s and dealing with the MS prereqs on forehand. The RhiExec.msi is the Rhino Installer, is that really necessary for using the product?
If you don’t install it, and your users want to install plug-ins for Rhino or Grasshopper, they won’t be able to. So, no, it’s not necessary for running Rhino - but my guess is that your users will contact us with these kinds of problems before they contact you. Please install everything the EXE installs.
Regarding the reboot - can you tell me which parameters you used when scripting the EXE install? Were you expecting the exe to return a specific exit code that would tell you to reboot the computer, or initiate the reboot on its own?
The Zoo license server parameter doesn’t work either
The Zoo parameter problem was fixed in SR9.