CAT-hs

My feedback

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

    We’ll send you updates on this idea

    24 comments  ·  Public » IT Pro - Controls and Knobs  ·  Flag idea as inappropriate…  ·  Admin →
    CAT-hs supported this idea  · 
  2. 469 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    74 comments  ·  Public » IT Pro - Controls and Knobs  ·  Flag idea as inappropriate…  ·  Admin →
    CAT-hs supported this idea  · 
  3. 81 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    CAT-hs commented  · 

    Frankly whoever at Microsoft thought installing software in the user's profile was a good idea should be fired and banned from using Windows for life.

    I've seen the response from the feature team that it is not installed in Program Files to ensure users get the newest features and fixes quickly and ensure all users are getting the best experience possible from MS Teams, and that they feel that their updates and features are being released too quickly to provide a god experience if admin credentials are required to install and update. This is lazy, short-sighted, and unfriendly to (what seems to be) the primary audience for the Teams application (enterprise).

    Many applications exist that are installed in the proper location (program files) and still automatically update themselves without additional administrator prompts, and there are many methods to do this. For example, you can publish updates as frequently as you want to Microsoft Store or Windows update (granted the later will still update most users weekly at best with default config). There are also options like the Google Chrome for enterprise MSI model with an updater installed and configured during the initial install so that admin rights are not needed after the first install.

    This design choice is driving my company away from Office 365 and towards Slack. Yes, they are basing the decision to go to subscription model for office vs keeping stand alone install and internally managed servers heavily on the the collaboration tool they decide on, and they figure that if either tool will be difficult to control properly (compared to normal office apps) then they might as well NOT pay the huge user subscription fee.

    CAT-hs 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.