Anonymous

My feedback

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

    We’ll send you updates on this idea

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

    Some people like the feature, many people prefer not to see the squigglies. It's been an opt-out feature in all other MS apps for decades. Why isn't it an option in Teams Settings?

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

    We’ll send you updates on this idea

    17 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!

  3. 8,545 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.

    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  · 
  4. 290 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 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.

  5. 692 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    132 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base