Full Stream ahead: Microsoft will end 'classic' method of recording Teams meetings despite transcription concerns Microsoft's technology for recording Teams meetings, Stream, will fully transition to a new version from 16 August, though some users have concerns over transcription features still under development. Stream is a service for uploading, viewing, and sharing videos. Among its most common uses is for recording Teams meetings. …
Remember when we first learned programming? You were usually taught to end you list of DATA statements with an "out of range" number, something that would never be in the actual data. 9's were almost always used, so maybe they used 99999 to mark the end of the meta-data. Or they are planning for five nines uptime.
Honestly, if you were in a relationship with such a controlling person in real life, and going by this, some would clearly class this an 'abusive/dominating relationship' by equivalence, you'd be taking them to court to get an injunction against them, to get them out of your life.
Does everything have to be by bloody powershell? Can anyone really say it makes their lives easier to have to piss about copying commands into powershell (that's if you're not of course blessed with a memory capable of typing everything without reference).
I couldn't care less if they had some kind of turgid interface they made admins use, at least it would be immediately accessible and searchable. They seem to be dumbing down windows on one side, making everything controllable by the crappy app interface, and making things stupidly complex on the other. I just want to change settings in the most efficient manner. Maybe it's just me, maybe some people are manically happy with it. It's odd perhaps, because I've never had a problem using Linux command shells.
Powershell is a mess:
- The syntax is horrible, they should have just used an existing language like python and extend it with a library;
- The Linux version of powershell isn't supported by all modules (like the O365 module);
- MS often abandons modules and then releases something new which lacks a lot of features of the old module;
- It's not backward compatible, sometimes you need to use an older version to get something done.
- The <verb>-<noun> idea messes up autocomplete, so instead of "Get-Module" they should have gone with "Module-Get" so you could see the available options through autocomplete after typing "Module-".
Perhaps it grows on you if you only use powershell, but when you're working with multiple languages then powershell is really awkward to work with.
This post has been deleted by its author
If the product is no longer fit for purpose, you should switch to another.
You don't have to use it, just because it is Microsoft.
If you all slavishly accept everything MS shovel out, you have nobody to blame but yourselves.
If the screencap is accurate, their auto-transcription is iffy. There must be an alternative.
Tech should obey the laws of the market. It is only different if you let it be. If you switch to a better product, or build a better product, a poorer product that deletes the features you need will lose market share.
Grow a pair and vote with your feet or accept your endless digital servitude in the sweaty embrace of Micro$oft.
There types a man who has never rolled out an application to several thousand users spread across several hundred sites.
You've obviously never implemented any major products, virtually every COTS package I have worked on relies on integration with office, if you need to transfer complex documents, spreadsheets etc between organisations you invariably come across compatibility issues if you use anything but MSOffice.
I have managed projects in an environment where the organisation "had transitioned" to Google Docs. Great idea in theory but in reality they still had a corporate licence for MSOffice and it was deployed in parallel on over 50% of machines so there was no saving to be had there.
On my personal machines I use a mix of Libre office and 0365. The older tattier laptops tend to have Libre office on them as they are used very occasionally and would struggle with later versions of MSOffice.
I've nothing against Libre Ofice I've used it since the first release of Open Office by Sun. But when I'm working with a corporate customer I need to use Microsoft products or 'glitches' in formatting appear in even the simplest documents.
Office P
It's not about "accepting", it's about "getting business done".
As a service provider you align with what your client provides, if LibreOffice fits that's fine, if it does not, MS Office's license is just part of the cost of doing business.
Adobe's licences are more less the same, your client provides photoshop files only compatible with the latest version that your free software can't handle right? Well, the Adobe license is part of your cost of doing business.
Sometimes you are in a position to recommend technology to a client, or help a startup pick what they will use, and you can then push as much as you like towards your preferred technology.
But if you try to take a stance and tell a client "yeah no, don't send me .docx files" or "don't send me psd files" and try to put it on them to align with your preferences instead of the other way around, you'll be "that weird guy they stopped doing business with".
There is a long list of missing features and bugs in Teams that Microsoft just does not address.
My crappy web cam gets confused by a bright background (it's called the sun) and gets the automatic white balance wrong, so that my face ends up black. In Skype for Business, I could just click on a button and adjust camera settings manually. Not in Teams. The recommended workaround is to adjust the settings using SfB while in a Teams call. Really?
More recently, my participant list keeps disappearing. According to the Microsoft user forum, there are thousands others with the same issue, but nothing has been happening there since April.
So I have very little faith that they will get around to adding transcript edititng anytime soon. They are far too busy redesigning the UX every other week, and adding new features so that they can keep popping up tool tips to keep their captive users engaged. Got it!
You can use the 5 year O365 Personal to Family upgrade method. To get 5 years Family for a fraction of the cost. Splitting the costs with 6 other people also increases the value.
The trick is waiting 1 month for personal if loaded 5 years’ worth then using the upgrade offer. The hard ceiling was 5 years of either plan.
After the 5th year any attempt to use 1 year Personal sub would only give 9 months increase in length to the Family plan you are on. So its better value for money to get the cheap Argos/ Amazon (track it with price spy and Camelcamelcamel) O365 Family Keys.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
