psydii

I'm unclear quite what the benefit is in trying to separate Teams voice traffic into its own vlan. Most devices running teams are likely to be PCs and therefore on whatever vlan they exist on? You can apply QoS tagging to Teams traffic: https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams And then set up your switches and wifi to honour the appropriate prioritisation of this tagging. I think most modern wifi will automatically do best effort to honor DSCP tags these days. What we did was to separate staff devices from student devices at the the VLAN+subnet level* then at the network edge have the separate subnets route/NAT in/out of their own dedicated IP address. Our ISP does not officially honor DSCP so at that point traffic is at the mercy of the ISP's policies. *because this is actually a good idea generally. See also recent threads on improving security.

@uccert You are not the first, nor will you be the last to fall into this trap. I am guilty myself. I saw this thread on twitter recently, and it gave me pause for thought. https://twitter.com/KarimPalant/status/1405282612000686084 Sharing it here more as a reminder to me, but I hope others might find it useful also.

This is causing failures to connect to our Windows Shares https://talk.tidbits.com/t/security-update-2021-003-catalina-and-2021-004-mojave/15754 Anyone else seeing this?

I've found the team at https://www.bechtle.com/gb/ to be very helpful.

Windows 10 Current Branch (or what ever the non-LTSB/C is called these days) is supported for 18 months after release. Unless no newer version is released, in which case it is supported up to October 2025. The latest LTSC/B is supported up to 2029. If 21h2 is in fact "11" and it really is dropping devices that can't support hardware backed Secure Boot, then it is going to leave a lot of people (and small businesses, and education) stuck on 10 - increasing support costs and fragmenting the Windows userbase. This would be an odd decision.

That start menu is definitely taking design cues from the MS365 home page. I think if they are going to do that, they should really lean into it, making the productivity experience completely seamless. I've never been a start menu purist though.

So.... with Windows Feature updates I just roll them out (with a bit of testing)... no need to get sign-off from SLT because its just an update to the sanctioned platform (Windows 10) But Windows 11? I can just see it now... that's going to need a business case. and a damn good one - "Windows 10 works 'just fine' thank you", "why rock the boat?" I can see the version number name change being a huge barrier to adoption in enterprises that already have demanded slower release cycles. If they are serious about the name, it is a massive misstep.

We move leavers to the free A1 licences until such time they hit the end of our retention period (typically 2 years for students), then they get unlicensed.

We've found USB C to be awful Nothing works reliably after a while (typically after a Feature Update, but sometimes a CU seems to trigger the failures). DisplayPort is usually the first casualty. Usually about 3 months after a feature update and having updated all drivers and firmware things settle down. Not really a winning timeframe users. The fragility of the cables is also a killer - and it seems likely that failing cables can cause permanent electrical problems solvable only by replacement system boards. We have had a couple of ports physically break (much as even USB A ports can) but have not yet had one with the problem you describe.

From a commercial point of view you are absolutely right and if this isn't the primary focus of their development over the next few years, I despair. There is however I think a great deal of value on providing a great experience on the mac hardware. Running well on M1 Macs will bring significant cachet from certain power users/tech influencers (I apologies for using that term). Pretty sure getting this to work at all required dev work from the Windows team so they've got from

They couldn't get people to adopt Metro apps. There is no way there is going to be a successful new operating system. The last two big changes did not go well (Vista and 8). Pretty sure what ever comes next will still be vista/NT under the hood and Win32 derived apps on top. They have been making some really deep level changes over the last few years on a similar scale to how apple has been refreshing OSX, but with out the CPU and multi-platform story. I recon we'll see a refreshed UI, maybe some re-working at lower levels for better ARM **COUGH**M1**COUGH** support, and hopefully some great work on the re-unification of UWP and Win32 and DOTNET, but otherwise it'll be business as usual, but with a newer worse name.

This is a bad idea and brings no value. The only possible good name might be "Windows 365" But based on recent trends it will probably be "Microsoft 365 Operating System: Windows 11"

Take a look at Circle too.

We’ve restricted external inbound so only MS365 services can talk to it. Not noticed any quirkiness yet.

This sort of feels like NT where the initial secret sauce was Win32 (i.e. the apis that developers use was cross platform to the other major business desktop OS). It will probably be at least a decade before it almost takes over the world before being usurped buy a platform not owned by one of the big tech giants of the time. (NT started in 1989 but wasn't released until 1993 and it was 2003 before it really hit its stride with XP, only to start loosing ground to Linux (via Andriod) in 2009/10. NT was also a microkernel at this stage of its life.) I expect ChromeOS will be where Fuchsia goes before Andriod handsets. With Fuchsia acting a bit like a hypervisor to 'legacy' Chrome and Andriod layers. Strikes me that Windows with VBS and Fuchsia will end up being architecturally very similar. Of course they've got to persuade developers to move over - MS tried that and failed (8/Phone), and Apple isn't having the best time, though arguably owning the entire stack and being highly profitable for developers gives them (Apple) the edge. This is what might be called a hot take. I should probably go and read the article now.

We have sync issues with OneDrive about as often as we have with the CSC (which is a cache on the local machine that sit between the 'save' button and the fileserver in all versions of windows since Vista). OneDrive for us worked fine when we had a 500Mb/sec line. Fileserver performance these days is only critical if you have either thousands of clients to a server, or hundreds of devices with roaming profiles and/or appdata redirection, or workflow with HUGE files. (FWIW the students do a lot of video work with the bins stored in OneDrive) That said - our legacy fileservers were spread over three 8-disk volumes in a SAN. At the time we needed capacity over performance - however we *never* had complaints about performance related to the storage. If you are going to go local it might still be worth running the numbers on a large array of spinning plates of rust. SSD performance may paint you into a corner of disappointment when you eventually do go cloud based - nothing will come close to the responsiveness of a SSD based array for a long long time.

Yeah, looking back at the service desk logs here, I'm not sure it (and some other software in Maths) have been used since early 2019! But here we are.

It does seem to be a self expanding exe that launches and exe and some associated swf files. Which is par for the course on some old edu software... odd though that it triggers for us, but not for you. Particularly as the malware is listed as a trojan not an PE infector.

Thanks. It is the mymira2.exe flagged as Tiggre.

Hi, We've hit a problem with this software, it keeps getting flagged as malware. Has anybody else seen this, or do we perhaps actually have an infected file on our hands? P.

"Note Supervised chat protects new chats created after the feature is enforced. It doesn't protect existing chats." https://docs.microsoft.com/en-us/microsoftteams/supervise-chats-edu

No idea if they are comparable feature/management wise, but I refer back to the limitation 25 APs in AIO vs 125+ for an IAP cluster.

I have thoughts, but not the time right now to properly articulate them. Quickly: lean into the LGFL USOAutUpdate, LGFL offer is a big money saver so make the most of it. It is way better than manually managing your accounts. Local Profiles need to be recreated at first logon. Fast SSDs are required to make this not painful. Seating plans also help as students use the same computer each time they visit the room. You can strip lots out of Windows 10 to make the logon fast, but then you break lots of other things and fight with MS each time they release an update. Windows Shared PC config has been surprisingly good this year. Previously we had too many legacy apps that just wouldn't work - but most people have moved to web based resources, so the Chromebook-like (kinda) set up works well. Storage Sense does a good job if you have OneDrive client app in use. You should have it switched on regardless. Set old profiles to be deleted (via group policy) Move to Intune for device management - it is different to group policy but if you are putting the work in, better to build to the future than playing where the ball was ten years ago.

FWIF IAPs work just fine without Central or Airwave.

We found that if you *consistently* STOP the video playback before switching screens or adding cameras the software was more reliable. We have also implemented a policy that requires the computer to be fully logged off after a case has been reviewed. This has the benefit that the app is shutdown regularly. Since doing both these things, nobody has complained about it locking up or crashing.