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...

Installing CUCM 7 on Hyper-V

on
*Updated at the bottom*

#WARNING#
Information here is for educational purposes, do not apply to any production environment! This blog post is a result of me wanting to run CUCM in an environment not supported by Cisco or Microsoft in any way, and is intended for LAB purposes only.

If you have read my earlier posts, you know I am trying to study to a CCIE Voice certification. I have been forced to slow down a bit by things at work and in my life, but the goal is still there.

As Cisco has moved to their v3 blueprint, one of the first things I have to do is to install CUCM 7 into a virtual environment. We already have a Hyper-v installation at work, and that's where I wanted to install the server. This proved harder than I though.

If you have tried the same thing, you'll probably end up with the error message:

'The hardware you are using is not supported for this product. Installation will now halt.'

I know CUCM is supported as a virtual machine, but it is obviously not supported by hyper-v. Since I do not have a license for vmware server, I found myself in a tight spot. But I found a way around my problem, and I do have CUCM 7 running on Hyper-V. Here is a short drill down of what I did:

- My first obstacle was not having a virtual server where I could create a machine, I only have the free player at my disposal. After a few attempts at Google, I found a site called easyvmx where i can create a blank VMware machine online (then download and mount it with player). With the empty machine (remember to allocate enough ram (2gig), disk space (120Gig) and to create it as a RED HAT ent. image) it was easy to start the player and boot from the CD-ROM (mounted ISO image of CUCM 7). The installation was straight forward, but my USB disk was to slow. I ended up installing the vmware image on my local HD instead of the USB drive. Don't know why, other VM's been ok on the USB.

- Next I had to convert the virtual HD from VMDK to VHD. I came across a tiny tool called Vmdk2Vhd from the vmtoolkit. Make sure you get v 1.0.13, as the version I found first was unable to read my VMDK.

- After converting and moving to hyper-v I was then stopped by an error message during "starting local" which prompted me: "Hardware not supported" and an option to shutdown the computer.

This is where I needed to get creative. I booted the Hyper-v image with an Ubuntu live CD and edited the file /usr/local/bin/base_scripts/hardware_check.sh by adding Exit0 as the first command in "function hardware_check_display_error_shutdown()".

I am uncertain if could have skipped the entire hardware_check.sh script, so I just ignored the error.

Thank you colleagues for helping me with the Linux stuff... You know who you are :)

**I'm sorry, there was a typO in this post. It is supposed to be "exit 0" not exit0.**