Workplace from Meta is going away. You will be able to continue using Workplace until August 31, 2025. Visit our Help Center to find out more.
English (US)
Log in
صفحه اصلی
صفحه اصلی
TECHNICAL RESOURCES CENTER
Get help with setting up Workplace, managing domains and other technical issues.
Mastering Workplace Features
Ready to become a Workplace pro? Learn all the ins-and-outs of our key features with in-depth guides, step-by-step user instructions and resource hubs.
Technical Resources
You don't have to be an IT genius to launch Workplace, but if you are then these technical resources are for you.
Help Center
Find step-by-step instructions and answers to frequently asked questions.
Support
Still can't find what you're looking for? Get in touch with a team of experts for more hands-on support.
News Archive
Workplace innovations, feature announcements and product updates.
Set up Guides
From adding a domain to inviting users, follow this step-by-step guide to set up your Workplace.
Domain Management
Find out why domain management matters - and how to do it properly.
Workplace Integrations
Discover how to bring all your tools together. Something missing? Learn how to build your own integrations.
Account Management
Keep your Workplace up to date by creating, maintaining or deactivating user accounts.
Authentication
Make sure you only give access to the right people by integrating with your current identity solutions.
IT Configuration
Learn how to keep Workplace running smoothly with info on networks, email whitelisting and domains.
Account Lifecycle
Understand the process of inviting members of your organization to claim their accounts.
Security and Governance
Get the lowdown on how we keep your people and information safe on Workplace with added technical terminology.
Workplace API
Learn how you can automate and integrate your custom solutions with Workplace using our API.
Getting started
From launching Workplace to paying for it, learn more about those crucial first steps.
Using Workplace
This is where we reveal the hidden depths Workplace has to offer with tips and info on key features.
Managing Workplace
Got a specific question about managing content, data or employees? This is the place to ask it.
IT and Developer Support
Looking for answers to more technical questions about security, integration and the like? Start here.
Support
Still can't find what you're looking for? Get in touch with a team of experts for more hands-on support.
Get in touch
Need help with your Workplace account? Fill out this form to get all the answers you need from our customer support.
Security
Security
    Start Using Workplace
      Mastering Workplace Features
      Work Academy
        Podcasts
          English (US)

          IT Configuration > Workchat MSI

          Be sure everything around IT works smoothly for Workplace.

          Overview

          Overview

          This guide explains the steps required to deploy Workplace Chat application via Windows installer (or .msi package). .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

          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:

          1
          Download the Workplace Chat MSI.

          2
          Copy the .msi to a shared folder so that the installer can be deployed over the network.

          3
          Open the Group Policy Management tool.

          4
          Expand the Forest - Domains - <your domain>.

          5
          Right click on <your domain> and select Create GPO in this domain, and Link it here....

          6
          Choose an appropriate name for the Group Policy and click OK.
          7
          Right click on the group policy that you have just created and click on Edit.

          8
          Go to Computer Configuration - Policies - Software Settings - Software installation.

          9
          Right click on software installation and select New - Package.

          10
          Browse to the shared folder, select the Workplace Chat .msi and click on Open.
          11
          Close the Group Policy Management Editor.

          12
          Right click on the group policy again and select Enforced.

          13
          Open up a command line prompt and enter gpupdate /force to update the group policies.

          14
          Restart the server when asked by the command line.
          Workplace Chat MSI deployment features

          Workplace Chat MSI deployment features

          Workplace Chat .msi deployment follows a sequence of steps:

          1
          Installs an installer in program files.

          2
          Sets a registry setting to run the installer on login.

          3
          Optionally runs the installer. If you don't want this step (e.g. the .msi is running by some provisioning system across many PCs), then run with "START=N". E.g.: msiexec /i WorkplaceChat.msi START=N

          4
          By default the app will run on first start which we recommend, but you can disable it with msiexec /i WorkplaceChat.msi INSTALLEROPTS="/S" which runs the installer in silent mode.
          Troubleshooting

          Troubleshooting

          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.

          Installation Options

          msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_msi>

          /i Trigger a normal installation
          /a Trigger an administrative install
          u Advertise the product to the current user
          m Advertise the product to all users
          /g Specify the language identifier used by the advertised package
          /t Apply transform to advertise package
          /x Uninstall the package

          Display Options

          msiexec.exe/i[/quiet][/passive][/q{n|b|r|f}] <path_to_msi>

          /quiet Quiet mode (there is no user interaction)
          /passive Unattended mode (installation shows only a progress bar)
          n UI level: no UI
          b UI level: basic
          n+ UI level: no UI (except for a modal dialog at the end)
          b+ UI level: basic (except for a modal dialog at the end)
          b- UI level: basic (with no modal dialog)
          r UI level: reduced
          f UI level: full
          ?
          The modal box is not displayed if the user cancels the installation. Use qb+! or qb!+ to hide the Cancel button.

          Restart Options

          msiexec.exe/i[/norestart][/promptrestart][/forcerestart] <path_to_msi>

          /norestart Machine will not be restarted after the installation
          /promptrestart User will be prompted if a reboot is required
          /forcerestart Machine will be restarted after the installation

          Logging Options

          msiexec.exe [/i][/x] <path_to_msi> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log] <path_to_log>

          i Include status messages in logs
          w Include non-fatal warnings in logs
          e Include all error messages in logs
          a Mention when an action is started in logs
          r Include action-specific records in logs
          u Include user requests in logs
          c Include the initial UI parameters in logs
          m Include out-of-memory or fatal exit information in logs
          o Include out-of-disk-space messages in logs
          p Include terminal properties in logs
          v Generate a verbose output
          x Include extra debugging information in logs
          + Append output to an existing log file
          ! Flush each line to the log
          * Log all information, except for v and x options