Teams Client installation options using FSlogix RRS feed

  • Question

  • Hi all,
    i've been send here by MS Teams support regarding Teams installation on a fslogix container.

    As per website:
    subject : Deploy the Teams desktop app to the VM

    Under Per-machine installation is mentioned the following:
    Installing Teams per-machine options is required for non-persistent setups.

    We are using a non-persistent Citrix VDI environment. 
    This means we would have to go for a per-machine installation as per-user would not be supported in a non-persistent install.
    However, if we would use FSlogix to supply a persistent location for both the teams client and it's data, would this count as a persistent setup, even on non persistent VDI's ?
    (I encountered this setup at another company and they use this to share the same teams client setup between VDI and local environment)

    So in this case (with install in fslogix container) both install types (per-machine and per-user) would be supported ?

    Thanks for any insights.

    Kind regards

    Friday, May 15, 2020 3:27 PM

All replies

  • You can deploy the Teams desktop app for VDI using a per-machine installation or per-user installation using the MSI package. Deciding on which approach to use depends on whether you use a persistent or non-persistent setup and the associated functionality needs of your organization. For a dedicated persistent setup, either approach would work. However, for a non-persistent setup, per-machine installation is required for Teams to work efficiently. See the Non-persistent setup section.

    With per-machine installation, automatic updates is disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates is enabled. For most VDI deployments, we recommend you deploy Teams using per-machine installation.

    To update to the latest Teams version, start with the uninstall procedure followed by latest Teams version deployment.

    For Teams AV optimization in virtual desktop cloud environments to work properly, the thin client endpoint must have access to the internet. If internet access isn't available at the thin client endpoint, optimization startup won't be successful. This means that the user is in a non-optimized media state.
    Friday, May 15, 2020 3:41 PM
  • Thanks, now that you mention it, the update precedure was the reason the other company was placing the install of client and data in a fslogix container.
    They figured by using the per user setup on a FSlogix container they would never have a version difference between de VDI and local environment as the same countainer would be used local and in VDI. The auto-updating of the client would make updating easier (no manual action required).

    With the suggested per machine setup in VDI and a per user in local you would always run the risk of having two different versions in place (not sure how a shared cache on fslogix would like version difference).
    Friday, May 15, 2020 3:58 PM
  • Question remains if a Per User setup which is completely installed into a mounted FSLogix container would be a supported scenario in a non-persistent Environment.
    If all Teams data and the teams application would be stored in a FSlogix container would this be seen as persistent, even while the VDI would be no-persistent.

    Not sure if it's the route we will take but we don't wan't to exclude any option and so I am looking for clarification on the issue of support in the case stated above.

    Tuesday, May 19, 2020 3:13 PM