Enable FIPS Mode on SLES 15 and Verify the Boot State
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Low bandwidth can hinder the connection in Microsoft Teams between teachers and students when teachers and students work remotely together. In this article, I will suggest some ways for teachers to reduce bandwidth used when using Microsoft Teams .
Note: The term bandwidth refers to the amount of data that can be transmitted over an Internet connection per second.
In the case of low internet bandwidth, avoiding or minimizing the use of live video is the best way to cut down on excessive bandwidth usage. And if you've recorded video or audio to share, it's better to upload it to OneDrive or Microsoft Stream and then share the link to that file (rather than embedding the large file itself in an assignment or notebook). ) .
Ways to save bandwidth when using Microsoft Teams
1. Limit the use of videos in face-to-face lessons
During in-person sessions, turn off the computer camera completely if possible. In addition, teachers only allow students to turn on the camera at the beginning of class and then actively turn off all students' cameras.
If teachers need to share documents and images for students during the lesson, they should share in a window format instead of sharing the desktop.
2. Use pre-recorded content instead of face-to-face sessions
Instead of presenting your content to students directly, teachers record a lesson as a video and save it on Microsoft Stream or another channel that they love. Send the video link to the student, and the student can use the video at another time when there are fewer internet users.
This is like a reverse class approach. Teachers can send a recorded Stream of the lesson before class with background material for homework and then use the class time to complete the assignment. Teachers can create channels for groups of students to collaborate on those assignments. Students can interact and ask questions with teachers through Chat activities.
If teachers create their lessons with PowerPoint slides, it's easy to convert them into videos using the features available in Powerpoint and then upload them directly to Microsoft Stream .
3. Manually upload videos to Stream
> select Stream. If the list is not there, the teacher selects All Apps , then selects Stream 3. Make workouts small by not attaching media files
Teachers should avoid giving Handouts that require students to attach large files, such as videos. If the assignment requires a video, instruct students to upload it to Microsoft Stream instead of attaching the video to the assignment.
Work offline with Class Notebook
Another small suggestion for teachers is that teachers should create lesson plans and develop exercises in OneNote Class Notebook when offline and then go online to distribute exercises to students. Or use Microsoft Teams to distribute assignments and assess students while on the Internet.
Here are some other ideas for minimizing bandwidth when working with Class Notebooks:
What students can do to save bandwidth
1. Do not use Camera when joining Microsoft Teams class
When joining a class meeting live on Microsoft Team, avoid using the camera entirely; Just turn on the microphone when necessary, such as when giving an opinion or participating in a Q&A. Or just turn on the Camera when students need to take attendance
Synchronizes with computers so students can read materials offline
Sync files with mobile devices for offline reading
When you open a file in Teams on your mobile device, you can download it to your device so you can reopen it later when you're offline:
Above are some suggestions to help teachers and their students still have the best experience and enjoyable lessons when bandwidth is limited.
Reference: Microsoft Teams – Frequently asked questions
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
.
