Microsoft is unlocking the "Full Potential" of Private Channels in Microsoft Teams: What You Need to Know

on
It has been a while since I posted something just about a Microsoft Teams update, as a lot have been Copilot in Teams to be honest. But here is a real Microsoft Teams update I think is worth knowing about, and it involves Security and Compliance as well. Microsoft is rolling out a "major" update to private channels in Teams, starting in late September 2025 and continuing through mid-December. This biggest change in this update is a shift in how private channel data is stored from individual user mailboxes to a dedicated channel mailbox. Not only will this simplifie compliance management, it will also and align private channels with shared channels, making governance and experience more consistent across Teams. This update promises to increase the support up to 1000 channels per team and 5000 members per channel, removing previous limitations. Teams will also allow meetings to be scheduled directly within private channels, enhancing collaboration.  For organizations using Micr...

RDP 6.1 in WinXP VS Win2008

on
Why oh why do they do it this way....?

I am not always impressed by the implementations from Redmond. But this one actually gave me something to think about, and stole a few hours of work....

First of all, Included in WinXP SP3 is the RDP 6.1, but the file version states 6.0? What is that about. The version number was the first thing I checked when the RDP client told me NLA was not supported.

I found quite a few posts where people asks about the same thing, but no answers.

but ok, I have the right version of RDP, which is supposed to support NLA. Why doesn't it work. Well apparently MS decided to include the 6.1 in SP3, but not to turn the feature on by default.
What you need to do to RDP into a NLA enabled Win2008 servier, is to do some regediting.

Here is the article I used to solve my issue:
http://support.microsoft.com/kb/951608/