View best response. This is great, ChristianBergstrom Thanks for posting! Thank you, ChristianBergstrom Just to emphasize two limitations posted at the links you shared:. ChristianBergstrom Given the client is in user land is there any good way to detect the existing version and then install silently via login script? I have the stuck update on about users. ChristianBergstrom I don’t think this is a very good idea, it’s quite possible you could get a version that isn’t going to be deployed to your deployment ring and therefore wouldn’t be supported.
It’s pretty unlikely that anyone is stuck, I’ve only seen it where there are firewall blocks preventing download. I would suggest the following to check if updates are fine.
As long as that’s there then there are no updates being offered to your client at the moment, so you are fine as you are. Teams versions are an increasing number, but only certain version make it to the widespread deployment ring which is supported. For example if you opt in to Public Preview or TAP programmes then you get more frequent and less tested client versions.
There has been a long gap in updates, it’s entirely correct, don’t mess with it. There would be an article on Docs if this was a supported proceedure. Steven Collier Hey Steven, fair enough. But tend to disagree to some extent. I’m not saying it’s a supported procedure. Not being able to add another account. Steven Collier we have users with the error “Looks like you’r on an old version of Teams. Update in X days to continue using the app” I’m sure the issue is environmental, but Premier support has been running in circles for the last 2 weeks.
I’m pulling the version number from an updated machine in our tenant, so hopefully that version is good for us. ChristianBergstrom , I have also updated my Windows desktop Teams client using this ‘forced’ method and ongoing updates are indeed working.
Good to hear that you also used this procedure and that the updates are working as intended afterwards. I would really appreciate some input from Steven Collier on that. Come on Steven, you can do it! It should be a first step. The main reason I posted the above was only to provide an option to “force”. Not to recommend it as something you should do as a routine to bypass the automatic update flow. ChristianBergstrom Yes the updates would continue, and Teams will offer you an update available to your ring with a higher version number, so effectively you will fall back in line with support from that point.
This is both to avoid load at the Microsoft end and to allow rollouts to be paused if a significant support issues is created. I don’t know but assume that is what happened in December, a versions was rolling out then deployments stopped. The point being the mechanism is there to protect people and the service. PDSDavid I’m sure that Premiere will come up with a supported answer, that warning means you are reaching the limit, 90 days I think.
If you just download the Teams client again doesn’t that take you back to more recent version? You can deploy that however you like. Also if you look in the log you will see the URL that Teams is checking for a version it looks a lot like those Bec is creating but with your current version number , if you log into Teams in a browser then open a tab to that page you might be able to see what in your infra is causing the block, the service will return some JSON if there is an upgrade, and the location the client should fetch it from.
Steven Collier well we got hit with some bad update in the past. Steven Collier Your faith in MS to just get everyone onto the best version for them is.. Given MSs history of just abandoning clients with major issues due to bugs, it seems unlikely that they are going to do any differently with Teams. Indeed, I manage around desktops and I see a wide range of versions installed going from 1. I reinstalled my own desktop yesterday with the latest version on the MS page and I’ve ended up with 1.
My machine also says I have the latest version, which is obviously wrong as I had a more recent version before the wipe and reinstall. I was forced to wipe Teams from my own machine because it was crashing every few hours. Nothing was displayed when it crashed. The window just closed. Wipe and reinstall has made no difference. It still crashes.
So do colleagues. I would like to get everyone up to the same version and to not use the profile installed version In theory when you install the machine-wide version then the profile version should be removed.
Never happens. Updating the machine wide will sometimes result in the profile version also updating, sometimes not. IanMurphy48 Hi, thanks for your input.
Bear in mind that it isn’t necessary to all be on the same version though as it’s the availability of features that really matters. But I do understand your frustration. My personal opinion is that C2R and the update channels is a massive improvement compared to MSI installations. Unfortunately Teams has it’s own update flow which is kind of out of control, even though you can choose to deploy it with M apps for ex. ChristianBergstrom I have no problem with having the users running 1.
Most installations just update, but you end up with a significant number which are just orphaned and never update. With win10 you download an iso and update from that and I’m seeing the same with Teams. Hundreds are running a more or less recent version, but then maybe a couple of dozen machines are seemingly ‘stuck’.
The msi installer simply does nothing to either the machine wide or profile installed versions when executed on these machines. IanMurphy48 the MSI “machine wide” installer included with o just creates a run once scheduled task in all local profiles including the default to triggers the profile install on login.
This is why a login script is required to do any maintenance. Unsupported or not, the OP is quite useful info. I would use the version from a healthy version in your environment.
I would suggest you check out the recently shared blog that explains a little about the update process at Why do I not see a feature but my colleague does? As explained it’s entirely normal to have different versions while deployments are happening slowly, things are a little complex at the moment due to some delays, an apparent rollback and new versions through TAP and Public Preview.
So if your users are guests in other tenants that may be in TAP you could be getting versions from there, I’m a guest in the microsoft tenant so my versions vary wildly.
As PDSDavid correctly explained the Machine Wide installer is more like a stub to create the installation for each user. Also the regular msi will be a little behind the newest version you may see, it trails rollout and doesn’t lead. It is quite unlikely that any specific build would cause the issues you describe, and that would seem to be largely verified by it remaining after a reinstall. I would be looking into driver versions perhaps. Teams update process is unorthodox in enterprise, more like a consumer app, but this is deliberate from Microsoft to manage the far faster pace of change in what is really a web application in a wrapper.
In my experience across Teams at many organisation it is very robust, the only issues I’ve seen are in locations where network restrictions are preventing access to the download service.
Microsoft were planning to provide some more admin control, allowing you to control the day of the week and so on, but I think this has been pushed down the list due to priority works to support Teams being used by schools during the pandemic. Its called a bug. Thats why we update software. Its the principal reason for updating software. Drivers being out of date is just being ridiculous.
You can always say that about anything. Why would only Teams, not much more than an advanced chat app, be affected by this magic driver issue when all the other stuff, using more advanced system features, is stable. Also, in my own case I know my driver set is up to date as I do update whenever something is available. On a client machine it would be less often, but in my case its all up to date and Teams still crashes constantly with no log. I’m basing this on supporting hundreds of desktops.
If applications like Solidworks, office or the myriad of programming tools people use crashed, the users would be on the phone.
They’re not, but a lot of people do report that they missed teams chat messages because it was closed. Just Teams, which makes it pretty unlikely that all those desktops with different models, different makes and different drivers have issues which just happen to affect Teams and only Teams.
Products 68 Special Topics 42 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Microsoft FastTrack.
Microsoft Viva. Core Infrastructure and Security. Education Sector. Microsoft PnP. AI and Machine Learning. Microsoft Mechanics.
Please guide me the way forward how to better achieve it with the steps. We have SCCM version Attachments: Up to 10 attachments including images can /28874.txt used with a maximum of 3. SarfrazAslam Here is sccm teams update answer to your question that hopefully you find helpful!
Agree sccm teams update what GaryBlok said, we could deploy the latest version of the Teams MSI files to install Teams but not to deploy voice tuner logic pro, this is because the client will auto update when it detects a new version is available from the service.
We cannot control or manage Teams updates. If the response is helpful, please click ” Accept Answer “and heams it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the texms email notification for this thread. Uninstall the Teams app installed for every user profile. For more information, see Uninstall Microsoft Teams.
Thank you for your teamss, but i am looking for a client uninstall and then reinstall auto process through SCCM. Above mentioned steps are the manual steps to perform.
It does not fulfill my requirement. SarfazAslam, unless you want someone to come into your job and do it for you, all your answers are here. Teams auto-upgrades, so you should only have to updatee it once. I have a super old version of teams in my task sequence and it just updates itself when the task sequence is over, taking a bunch of time to constantly update источник isn’t really necessary. Also, you will notice that Teams is a per-user install, so automated uninstalls don’t really work.
So, as everyone has upadte already updte. You put the installer in your task sequence, doesn’t really matter what version because it will auto-update after the TS is done. Everything in your environment will then stay auto-updated, corrupted clients have to be addressed manually. Oh scm, job sccm teams update for your help sccm teams update. Читать статью loves employing people :-D. Application installation Status. Skip to main content. Find threads, tags, and users Comment Show 0.
Current Visibility: Visible to all users. In the provided link sccm teams update information regarding the re-installation using SCCM. Redeploy the MSI package to that particular computer. Then moving forward you allow the built увидеть больше self-updater keep Teams Current.
Regards, Sarfraz Aslam. So, as everyone has basically already said: You put the sccm teams update in your task sequence, doesn’t really matter what version because it will auto-update after scm Sccm teams update is done. Related Questions.
Leave a comment