Make sure you adjust the version number to the version you’re installing. You’ll want to use something like: msiexec /i "slack-standalone-.msi" INSTALLLEVEL=2 /qn /norestart. How do we do that?īy default, MSI deployed apps won’t launch on startup but you can set this up by adding INSTALLLEVEL to your install command line.
💡 Learn how to add RSS feeds to your Slack workflow. In order to stay current with new Slack releases, we have provided an RSS feed to notify you of new Windows Slack Desktop App updates. When installed using the machine-wide installer, Slack does not auto-update. It is important to stay up to date on new releases, as they provide users with valuable features and fixes.
However, despite this task working on Windows 7 (ie it does indeed start Slack) the task doesn't get notified so just waits and eventually times out. Then my own post-script Command: "C:\Program Files\Slack\Slack.exe"īecause the pre-built PDQ package kills the running slack.exe this post-script was meant to start it up again after the installation. PDQ has a pre-built package for Slack, so I started with that and added my own pre-step to remove the per-user installation Command: "%LocalAppData%\slack\Update.exe" -uninstall -s Removing the per-user installation was important, as when having both installed on the same computer, the user would find two shortcuts on the start menu, both potentially different versions of Slack. Their user installation ended up in %localappdata%\slackĪfter a while we decided to standardise this, so wanted to remove the per-user installation and replace with the per-machine installation. When we started using Slack, we left it to users to install themselves (which they could do without admin rights). I'm just throwing my experience out there.
0 kommentar(er)
