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.
Device Links
Kicking someone from a Discord channel doesn’t have to be permanent. Sometimes you do it just because an individual was annoying, spamming heavily, or being rude and just needed a short-term ban. These kinds of things happen on servers all the time.

It’s up to the server’s owner and admins to keep the peace and dole out punishment as needed to ensure theirs is a server worth being a member of. Though it may suck to be the guy (or girl) who has to make these decisions, they do have to be made, and I’m going to tell you how to pull it off.
PC & Mac
To remove a user from a Discord channel on PC:
Android & iOS
To remove a user from Discord on a mobile device:
Moving A User To A Different Channel
Sometimes you may not want to kick a user from the channel, but move them to a different one. This can occur if someone has stepped away but left their microphone on and all of their background noise can be heard on the channel. This is also useful for admins conducting interviews on would-be hopefuls to join their clans or any other “business-like” proposals that take place on Discord.
You have two options to move a user from one channel to another:
Have a chat with the server owner if you find you’re unable to move a member but feel you should have the permissions. They can add you by visiting the server settings and click on ‘Roles’. Once the ‘Move Members’ permission is toggled on you can happily move the members you’d like between channels.
Banning A User From Channel
If you’re an admin or the server owner and you feel that moving or kicking a user from a channel simply isn’t enough, you could instead choose to ban them from the channel. This clearly has a bit more permanence to it but if you feel that there is no other alternative for the user in question, then this is how you do it:
Only those with the proper role and permissions can reinstate a user who has been banned. If the user violates Discord’s community guidelines you can report them resulting in a ban from the platform altogether.
Pruning You Server
For those with too many members to keep track of, there may come a time when members will simply stop coming on. This can lead to a super long list of members that are really just taking up space. If you have a need to kick stale users who haven’t logged into your server for an extended period of time, you can mass kick them all with the Prune option.
You’re able to set up an automatic kick option based on a preset period of time. Instead of policing each member individually, you can mass kick every user that has been a no-show within this period. To prune:
Pruning will only work on those members without a currently assigned role. You’ll need to remove the role prior to pruning if you’re trying to get rid of certain members. This is a really great tool to keep your servers clean of freeloaders, just be sure that you don’t accidentally boot your friends.
There are many ways to customize your Discord servers and improve the user experience. While scrolling through each member’s options in the pop-up menu take note of the mute option. If there’s a user you’d like to mute for a bit without kicking or banning, take advantage of this option!
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.














