This guide explains the steps required to deploy Workplace Chat application via Windows installer (or
.msi is an installer package file format used by Windows for installation, storage, and deletion of programs. The files are stored within a package, which is then used with the program’s client-side installer service to open and install the program.
The system administrator of a company will typically deploy
.msi packages via the Windows Server group policies objects (GPO) or through a third party software deployment tool.
The main idea is that an application will be automatically installed the next time a user logs in to their computer. This means that the application will automatically be installed without the need for an end-user, who might not have permissions to install applications, to run the executable manually.
Deploy Workplace Chat MSI by using group policies (GPO)
In order to deploy Workplace Chat MSI by using group policy objects, follow the steps below:
.msito a shared folder so that the installer can be deployed over the network.
.msiand click on Open.
gpupdate /forceto update the group policies.
Workplace Chat MSI deployment features
.msi deployment follows a sequence of steps:
.msiis running by some provisioning system across many PCs), then run with
msiexec /i WorkplaceChat.msi START=N
msiexec /i WorkplaceChat.msi INSTALLEROPTS="/S"which runs the installer in silent mode.
When you want to deploy an
.msi, you can use the
.msiexec to run a couple of commands in a terminal prior to deploying the
.msi in the group policies or third party deployment tool. The
msiexec has the possibility to run install, display, restart and most importantly logging options.
Trigger a normal installation
Trigger an administrative install
Advertise the product to the current user
Advertise the product to all users
Specify the language identifier used by the advertised package
Apply transform to advertise package
Uninstall the package
Quiet mode (there is no user interaction)
Unattended mode (installation shows only a progress bar)
UI level: no UI
UI level: basic
UI level: no UI (except for a modal dialog at the end)
UI level: basic (except for a modal dialog at the end)
UI level: basic (with no modal dialog)
UI level: reduced
UI level: full
qb!+to hide the Cancel button.
Machine will not be restarted after the installation
User will be prompted if a reboot is required
Machine will be restarted after the installation
Include status messages in logs
Include non-fatal warnings in logs
Include all error messages in logs
Mention when an action is started in logs
Include action-specific records in logs
Include user requests in logs
Include the initial UI parameters in logs
Include out-of-memory or fatal exit information in logs
Include out-of-disk-space messages in logs
Include terminal properties in logs
Generate a verbose output
Include extra debugging information in logs
Append output to an existing log file
Flush each line to the log
Log all information, except for