Anonymous

My feedback

  1. 62 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    How things should be, to support a real-world enterprise environment:

    - Teams supports centralized installation and managed updates
    - Teams cache is in %localappdata%
    - Teams settings are in the Registry, in HKCU, or if they have to be file-based, in %appdata%

    Anonymous commented  · 

    We're seeimg 300MB Teams data in %localappdata%, which includes the Teams install and can include a Previous folder with previous versions of Teams, making this folder grow to 600MB or more.

    We're also seeing a Teams folder in %appdata%, containing Teams caching as well as user settings. This directory can grow from tens of MB to multiple GB, and roams by default.

    THIS NEEDS TO CHANGE!

    In a roaming profile environment (for instance, free seating or Citrix shared desktop with multiple servers), Teams settings need to roam. Also, to avoid asking users to reinstall Teams after every logon, the installation should either be centralized, or the installation folder should roam.

    Conversely, the ginormous Teams cache should NEVER roam.

    This means that the installation directory is in the wrong place (%localappdata%) and the cache is also in the wrong place (%appdata%). Not to mention the settings, which are in %appdata%, where the cache is also stored.

    None of that makes any sense. Microsoft, your vision for the future of computing may be individualistic, with personal devices, but a HUGE part of the world works with managed devices and roaming profiles. Get with the program!

  2. 6,809 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    583 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.

    ~Alex

    Anonymous commented  · 

    How things should be, to support a real-world enterprise environment:

    - Teams supports centralized installation and managed updates
    - Teams cache is in %localappdata%
    - Teams settings are in the Registry, in HKCU, or if they have to be file-based, in %appdata%

    Anonymous commented  · 

    We're seeimg 300MB Teams data in %localappdata%, which includes the Teams install and can include a Previous folder with previous versions of Teams, making this folder grow to 600MB or more.

    We're also seeing a Teams folder in %appdata%, containing Teams caching as well as user settings. This directory can grow from tens of MB to multiple GB, and roams by default.

    THIS NEEDS TO CHANGE!

    In a roaming profile environment (for instance, free seating or Citrix shared desktop with multiple servers), Teams settings need to roam. Also, to avoid asking users to reinstall Teams after every logon, the installation should either be centralized, or the installation folder should roam.

    Conversely, the ginormous Teams cache should NEVER roam.

    This means that the installation directory is in the wrong place (%localappdata%) and the cache is also in the wrong place (%appdata%). Not to mention the settings, which are in %appdata%, where the cache is also stored.

    None of that makes any sense. Microsoft, your vision for the future of computing may be individualistic, with personal devices, but a HUGE part of the world works with managed devices and roaming profiles. Get with the program!

    Anonymous supported this idea  · 
  3. 192 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    This is a real problem. We have users whose cache grows to GBs. We also have roaming profiles on Citrix. The ginormous profiles cause no end of trouble. But it looks like the roaming Teams cache contains the user settings, so excluding the entire %appdata%\microsoft\teams would make our users very angry.

  4. 367 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  60 comments  ·  Public » Languages/Translation  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.