Ensuring Teams Meeting Room Add-in Stability in VDI Setups


I am encountering a recurring issue where the Teams Meeting Room Add-in requires reinstallation after deploying it within a non-persistent VDI environment. This problem persists despite following the standard deployment procedures. Has anyone else experienced this, and if so, could you share any effective solutions? Additionally, are there any known fixes that can be directly applied to the Link Parent or Golden Image to prevent this issue?

Thank you for your insights,



The challenge of maintaining consistent functionality of the Teams Meeting Room Add-in within non-persistent Virtual Desktop Infrastructure (VDI) environments is a notable concern for IT professionals. This issue often manifests as a need for frequent reinstallation of the add-in, despite adherence to standard deployment protocols.

Non-persistent VDI environments are designed to provide a fresh, standardized setup at each login. This means any changes made during a session, such as the installation of add-ins, are typically not retained after logout. The Teams Meeting Room Add-in, essential for scheduling and joining meetings directly from Outlook, thus faces a persistence problem in such setups.

Exploring Solutions

To address this, IT administrators can explore several strategies:


Utilize Persistent Disks

: Implementing persistent disks that retain user data and settings between sessions can help maintain the add-in’s installation status.


Scripted Installation

: Automating the add-in installation process through logon scripts can ensure the add-in is installed at the beginning of each session.


Group Policy

: Leveraging Group Policy Objects (GPOs) to manage the deployment and maintenance of the add-in across the VDI environment.


Golden Image Updates

: Regularly updating the golden image to include the latest version of the Teams Meeting Room Add-in can minimize compatibility issues and reduce the need for reinstallation.

Direct Fixes for Link Parent or Golden Image

For a more permanent solution, IT administrators can apply fixes directly to the Link Parent or Golden Image:

  • Incorporate Add-in into Base Image

    : By including the Teams Meeting Room Add-in in the base image, it becomes a default part of the environment upon each session start.

  • Registry Tweaks

    : Modifying the registry settings within the golden image to automatically trigger the add-in’s installation process can provide a seamless user experience.

  • Vendor Support

    : Engaging with the software vendor for a specialized solution tailored to non-persistent VDI environments can also be beneficial.

  • Conclusion

    While the reinstallation issue of the Teams Meeting Room Add-in in non-persistent VDI environments is a recurring problem, the aforementioned solutions offer a starting point for IT professionals to tackle this challenge. It is crucial to test these solutions thoroughly to ensure they align with the organization’s IT policies and user needs. By doing so, organizations can enhance their VDI setups’ efficiency and reliability, ensuring smooth and uninterrupted communication and collaboration through Microsoft Teams.

    Note: The effectiveness of these solutions may vary based on the specific VDI setup and organizational requirements. It is recommended to consult with IT specialists or the software vendor for tailored advice.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    Privacy Terms Contacts About Us