The 2019 version of the installer was unpacked in the MSI - everything is understood with it, standard keys
2020 version is packaged differently, but did not find deployment help on the main page
installation help is also not displayed with standard keys /?, /HELP, ,?, -h, -help, --help
the / SILENT key worked, but how to display the progress bar for example, or remove shortcuts from the desktop?
DEVELOPERS SKETCHUP (or who is responsible for the final stage of the product?) - please do normal installation help, please !!!
we pay for the product is not small money!
you make life difficult for system administrators
not everyone buys SketchUP for one PC
dozens of sketchups can be purchased at the organization
and you suggest us to put it on each PC?
A colleague has written up instructions for doing a silent install, which mainly shows the silent key you mentioned. Iâm not sure how many of the Install Shield parameters also would work, so I will check if someone can pop by here to let you know.
Same problem here. I am well versed in application deployment using SCCM, using .exeâs and MSI installers. Nothing conventional works with this exe. I am a very unhappy system admin.
@colin Can you please share the instructions your colleague has written up? Need to deploy to 75+ computers here and with the packaging change it appears to be an entirely different process than in years prior.
Here is the full text of what we are telling people:
The SketchUp 2020 exe installer is designed with a silent mode. You will need to make sure the following prerequisites are installed:
These will automatically install with SketchUp if an internet connection is available.
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.23.27820
KB2999226 - Windows 7 Only
Microsoft .NET Framework 4.5.2
How to run the silent installer with default options
1.) Download a SketchUp 2020 installer. The full installer includes all of the language packs. To download the installer please see: Downloading SketchUp | SketchUp Help
2.) From an elevated command line or script run
SketchUpPro2020-0-363-132.exe /silent
This will install with default options. English as the language, C:\Program Files\SketchUp\SketchUp 2020 as the install directory.
While the install is running no windows will open. After a couple of minutes, SketchUp will be installed.
Troubleshooting Steps:
The installer creates an InstallShield.log from the directory where it was run. This can contain information useful for troubleshooting. If you are having issues, please share this file with us so we can best assist you.
Thanks for the helpful post. Just a couple of things to add.
Use <double backslash>\servername where youâre calling the installer from a network location and use exclamation marks where your folder path includes spaces:
The silent install works but how do you silently uninstall SketchUp Pro 2020? Using the msiexec /x uninstall command doesnât remove everything. The desktop shortcuts remain, the application remains visible in Programs and Features, running the Programs and Features uninstall still runs an uninstaller which leads me to believe components are still installed.
It was much easier to manage deploying SketchUp Pro on a large scale when a MSI could be extracted from the exe.
I think I figured out the silent uninstall command after digging through the registry a bit. If anyone else needs to do a silent uninstall the following command should work:
Thank you all for your active participation in this topic!
the deployment issue was clear with the key /SILENT
but at least the issue of deleting shortcuts at the deployment stage is left open
so that you can select âdo not add shortcuts to the desktopâ in the installer - after all, they cannot be removed from the user, and admin rights have been removed from users on the machines!
as a result, then on the userâs desktop there is a garbage can from such âdeploymentsâ and not deleted shortcuts.
just âprobably you need to use another installer, not installshiledâ
so that there is a key /NOICONS or something like that.
This is what I am writing about because I know that they are there, and to remove the shortcut you need administrative privileges, which users do not have. (and never will be)
therefore, in a normal installer, you must have a checkmark in the GUI installer in order not to create shortcuts, or a deployment key, indicating that /DO NOT CREATE SHORTCUTS! (my indignation towards the developers:))
I understand writing a complex code of the product itself, it is difficult, time-consuming and expensive.
but make a normal installer that can be deployed painlessly and flexibly in workgroups
this is a passed stage, there is nothing new and supernatural to come up with. everything has been written for a long time. you just need to implement it.
what is the difficulty ??
It isnât as convenient as having the functionality built into the installer but you could write a PowerShell script to perform the installation and then remove the desktop shortcuts later.
I thought Iâd post my experience with the installer, as deployment would be a right pain without an MSI.
I managed to extract an MSI from the temporary folder created, it does take quite a while to generate. The temp folder created with a GUID eventually creates another subfolder with a GUID (including a second one if Visual C++ Runtime are required). Below was the easier way to grab the files, without having to catch them during install running - probably best to do from a VM.
Uninstall the Visual C++ 2015-2019 runtime from your PC (or just have a version lower than is required, 14.23.27820)
Run the installer normally (not silent)
Eventually, once the files have extracted it will first attempt to install the Visual C++ Runtime and halt, prompting for a reboot.
At this point you can navigate into the %Temp% location and find the folder containing the MSI. Iâve attached a screenshot to show this.
I think two folders are created when the installer is run, one containing just the Install Shield file (i.e. _isB653.exe) and the other containing some of the extracted Install Shield files, plus the subfolder with a GUID containing the MSI.
Of course, if you set this up in SCCM it will still require the Visual C++ Runtime to be added as a Dependency, but having the MSI allows me to have more control on what the install does in terms of rebooting, etc.
Iâve not had any issues with shortcuts, mentioned above. When I run the uninstaller (MsiExec /X â{4c8537c3-c896-1bca-d37f-3a0c4c460134}â /QN /NORESTART - for version 20.0.373) the shortcuts are removed as expected.
Yes, but if you require English I donât believe itâs required. The only item added by 1033 (en-us) is âInstallShieldTempProp = 0â and as Iâm not actually using the InstallShield method I donât think itâd do anything. The other transform files add this entry plus update all the language in the MSI.