Messages

😂 Thank you.

Note what I said in an earlier post though, I was caught out initially.. if like me you deploy redirected desktops to your users, I fired out a shortcut to the original installation directory which soon changed after an update and broke the shortcut.  As with all these WindowsApps, you can create a long-term shortcut by running shell:appsfolder from the start menu, then create from there.

Frankly your like or dislike of what another might view as quite helpful advice is largely irrelevant. As the OP for this thread, I felt I was helpfully offering up how I myself have (very successfully) chosen to deal with this issue after being the person asking for the advice initially. (As a sidenote, I never told any other poster I didn't like their comments. I'd probably feel quite rude doing so.)

For info.. just because I can't help myself.. the new Teams app has the same look and feel of the old. On Windows 11 in particular its pretty seamless as it seems far better at simply maintaining itself, and I no longer have to keep replacing the exe and json in the old Teams installer directory which I was doing previously.  It seemingly removes all of the hassle and admin-overhead of having to maintain the application entirely and above all you know what its like once Microsoft decide they're going in a new way with an application/OS, etc... you've just got to suck it up really and not keep trying to flog a dead horse as they say in trying to keep an older version ticking over.

We all have problematic users, and I completely get that all organisations are different and have their own challenges, but I'm a firm believer in (obviously where possible due to technical considerations) not allowing the users to lead on progress. If something is going to make my (and my teams) jobs easier in the long run, it's happening.. and the users will be told why in a polite but firm manner.

You really shouldn't have to worry about it any more. Just migrate to 'New Teams for Work or School' which is a WindowsApp and moves to C:\Program Files\WindowsApps\*  using a new directory for each version release - So that does mean you need to get your user shortcuts from 'shell:appsfolder'

This is something we might need to do given the latest update that MS Teams is now going to be rolled out as part of the MS Office 365 bundle. That will no doubt install it somewhere completely different and result in 2x versions on the client.

Completely get that this is a shocker of an application to maintain. The MS recommendation is a million miles away from my own thoughts, in an estate of thousands of computers it's just really not manageable, especially in a shared environment with multiple users on computers in an average day (Schools.)  So.. what I've found is that the auto-update for individual user profile isn't always reliable so I have set my own powershell to compare the exe versus that in the program files(x86) folder and force an update that way.  As my program files dir isn't up to date however, thats where the problems lie. Can't update it... without having a perfectly lined up supersedence path in SCCM, so I'm just wondering if anyone else has come up with a more innovative idea than what I'm thinking now, which is just overwriting the program files Teams folder periodically via Group Policy files...

I'm having an issue with each new release PMP is pushing out of the machine-wide Teams application. Obviously this isn't coming as an 'update' but as an application.  Unfortunately what I've just realised is that its detection method is way off and if it targets a PC with an older release, it says it's installed without actually doing anything.  I've had this issue when deploying manually in the past and had to completely edit how the detection methods work and set up supersedence. The PMP release does none of this..

Surely I'm not the first to come against this and wondered what workarounds people were using to negate this?