How to Deploy Slack via Microsoft Installer: Step by Step Guide

Slack offers two distinct Microsoft Installer (MSI) x64 packages for IT administrators to install Slack for Windows on multiple users or machines. These packages support all msiexec commands and are recommended for large-scale deployments. The two MSI packages use different deployment and update mechanisms, so careful consideration is needed. For individual or small-scale use, the standard desktop app is recommended.

For Windows on ARM devices, an MSIX package is available with equivalent functionality to the x64 MSI installers, currently only as an arm64 build.

Tip: For managing user settings in your organization, consider using Slack’s streamlined desktop app configurations.

MSI for Per-User Deployment

This MSI package installs the Slack installer machine-wide, rather than installing Slack for Windows individually. The Slack installer will only add Slack for Windows if it was never installed for the currently logged-in user.

Ideal for:
Companies where employees use their own devices and update Slack automatically.

Not suitable for:
Organizations where multiple users share machines (e.g., terminal servers) or need to control specific Slack versions.

Key Considerations:

• Slack for Windows installs to %LOCALAPPDATA%
• Each user maintains their own Slack version
• Automatic updates download and install for each user
• No maintenance required – Slack self-updates
• Slack won’t auto-start unless configured
• Uninstalling the MSI doesn’t remove Slack from user accounts
• Slack installs upon user login

Installation Process:

1. Download the 64-bit MSI Installer for per-user deployment
2. Install the Microsoft Installer package
3. Sign out of your Windows user account
4. Sign back in to your Windows user account
5. The Slack app icon will appear on the Desktop and Start menu

The MSI for machine-wide installation is designed to install Slack for Windows across an entire machine, making it suitable for environments where multiple users share a device. This installation method is particularly beneficial for companies using terminal servers or where there is a need to control which version of Slack is used. Here’s a detailed overview:

MSI for Machine-Wide Installation

• Deployment: Installs Slack for Windows machine-wide, either to Program Files or a location of your choice.
• Multi-Client Capability: Allows multiple users on one machine, keeping their profiles separate in %ROAMINGAPPDATA%.
• Updates: Slack will not receive automatic updates with this method.

Who It’s For

• Best Suited For: Companies where multiple employees use the same machine, such as terminal servers, and/or need to control which version of Slack they use.

Who It’s Not For

• Not Ideal For: Companies where employees use their own machines and benefit from automatic updates. These organizations should consider the MSI for per-user deployment.

Considerations

• Single Installation: Results in a smaller hard drive footprint at scale.
• Data Storage: All user-related data, including workspace info, preferences, and logs, is stored in %ROAMINGAPPDATA%.
• Version Control: Teams must ensure that the latest version of Slack for Windows is installed.
• IT Maintenance: Required to keep Slack up-to-date and secure.

Installation Process

1. Download the Installer: Obtain the 64-bit MSI Installer for machine-wide installation.
2. Run the Installer: Follow the guided installation process.
3. Access: The Slack app icon will appear on the Start menu.

Keeping Slack Updated

• Manual Updates: Since Slack does not auto-update with this installation method, it is crucial to stay informed about new releases. Slack provides an RSS feed to notify users of new Windows Slack Desktop App updates.

By choosing the MSI for machine-wide installation, organizations can effectively deploy Slack across shared environments, ensuring that all users have access to the same version while maintaining separate profiles.

The MSI for machine-wide installation is designed to install Slack for Windows across an entire machine, making it suitable for environments where multiple users share a device. This installation method is particularly beneficial for companies using terminal servers or where there is a need to control which version of Slack is used. Here’s a detailed overview:

MSI for Machine-Wide Installation

Overview

• Deployment: Installs Slack for Windows machine-wide, either to Program Files or a location of your choice.
• Multi-Client Capability: Allows multiple users on one machine, keeping their profiles separate in %ROAMINGAPPDATA%.
• Updates: Slack will not receive automatic updates with this method.

Who It’s For

• Best Suited For: Companies where multiple employees use the same machine, such as terminal servers, and/or need to control which version of Slack they use.

Who It’s Not For

• Not Ideal For: Companies where employees use their own machines and benefit from automatic updates. These organizations should consider the MSI for per-user deployment.

Considerations

• Single Installation: Results in a smaller hard drive footprint at scale.
• Data Storage: All user-related data, including workspace info, preferences, and logs, is stored in %ROAMINGAPPDATA%.
• Version Control: Teams must ensure that the latest version of Slack for Windows is installed.
• IT Maintenance: Required to keep Slack up to date and secure.

Installation Process

1. Download the Installer: Obtain the 64-bit MSI Installer for machine-wide installation.
2. Run the Installer: Follow the guided installation process.
3. Access: The Slack app icon will appear on the Start menu.

Keeping Slack Updated

• Manual Updates: Since Slack does not auto-update with this installation method, it is crucial to stay informed about new releases. Slack provides an RSS feed to notify users of new Windows Slack Desktop App updates.

By choosing the MSI for machine-wide installation, organizations can effectively deploy Slack across shared environments, ensuring that all users have access to the same version while maintaining separate profiles.

Keeping Slack Up-to-Date

It’s crucial to maintain current versions of Slack to access new features and bug fixes. For installations using the machine-wide installer, automatic updates are not available. To stay informed about Windows Slack Desktop App updates, we provide an RSS feed at https://slack.com/release-notes/windows/rss.

Tip: Learn how to add RSS feeds to your Slack workspace for easy update notifications.

ARM-based MSIX for Windows

With Windows on ARM, we’ve introduced an MSIX package that combines the benefits of our x64 MSI packages. This package can be installed via Powershell, supports automatic updates, and allows secure machine-wide deployment.

To disable auto-updating, refer to our guide on managing desktop app configurations. Both installation methods below support this feature. Enterprise software distribution services like Microsoft Endpoint Configuration Manager and Intune support MSIX package deployment.

Installation Methods:

1. Per-user installation:

   Add-AppxPackage -DocumentPath ""

Refer to Microsoft’s Add-AppxPackage documentation for details.

2. All-users installation:
   This method is equivalent to deploying the per-machine MSI, allowing access for all current and future system users.

   Add-AppxProvisionedPackage -Online -PackagePath ""

Consult Microsoft’s Add-AppxProvisionedPackage documentation for more information.

This approach provides flexibility in deployment options while ensuring Slack remains up-to-date and secure across different Windows environments.

Launching Slack on startup:

• MSI-deployed applications don’t start automatically on startup by default
• You can configure this by adding INSTALLLEVEL to the installation command line
• Example command:

  msiexec /i "slack-standalone-[VERSION_NUMBER].msi" INSTALLLEVEL=2 /qn /norestart

• Adjust the version number to match your installation

Issues with per-user deployment:

• Slack deployment tool only installs if user hasn’t already installed Slack
• Tool may revert if it finds remnants of previous deployments
• Checks for folders: %APPDATA%\slack or %PROGRAMDATA%\slack
• %PROGRAMDATA%\slack installation (rare) affects all system users

Updating the deployment tool:

• Not necessary for existing Slack users (app auto-updates)
• New users get the version included in the MSI deployment tool
• Auto-updates apply after app restart or computer reboot
• Recommendation: Keep deployment tool version as up-to-date as possible

Key takeaways:

1. Use INSTALLLEVEL parameter for startup configuration
2. Be aware of potential conflicts with existing installations
3. Regular updates to the deployment tool are recommended for new user installs

Here is a guide to managing Slack installations, addressing common issues, and ensuring proper deployment and updates:

Managing Slack Installations

Launching Slack on Startup

To configure Slack to launch automatically on startup when deployed via MSI, use the INSTALLLEVEL parameter in your command line. The command should look like this:

msiexec /i "slack-standalone-[VERSION_NUMBER].msi" INSTALLLEVEL=2 /qn /norestart

Make sure to replace [VERSION_NUMBER] with the specific version you are installing.

Troubleshooting Installation Issues

Per-User Deployment Issues

If Slack is not installing for some users or all users on certain workstations, it may be due to remnants of previous installations. The deployment tool will not install Slack if it detects existing installations in the following folders: %APPDATA%\slack or %PROGRAMDATA%\slack. The latter is rare but impacts all users on the system.

Automatic Updates and Deployment Tool

For users already using Slack, the app updates automatically, so there is no need to update the deployment tool. However, for new users, the version included with the MSI deployment tool will be installed, and updates will apply upon app or system restart. It is recommended to keep the deployment tool updated.

Uninstallation Process

When the MSI for per-user deployment is uninstalled, Slack will no longer install for new users. However, existing users must manually uninstall the app. Automate this with the command:

"%LOCALAPPDATA%\slack\Update.exe" --uninstall -s

For shared machines, consider using the machine-wide MSI to remove Slack from all users.

Handling Multiple Versions

Even if multiple versions appear in the Apps and Features list, only the latest binaries are installed. Starting with version 3.4.0, older versions are removed before new installations.

Silent Updates and Reboots

Version 3.4.0 introduced a feature that removes previous MSI versions during updates. If an update or uninstall is initiated while Slack is in use, the MSI installer may require a reboot to complete changes. To avoid unexpected reboots, use:

msiexec /i "slack-standalone-x.x.x.msi" /qn /norestart

By following these guidelines, you can effectively manage Slack installations, address common deployment issues, and ensure that the application remains up to date and functional across your organization.