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.
Zalo's Backup and Sync feature makes it easy to sync old messages even when changing phones or deleting apps. How to do it is quite simple, you can refer to how to synchronize Zalo messages from your phone to your computer and vice versa.
When you are about to change your phone or delete an app, you need to do 2 steps:
- With old phones / old Zalo: Backup messages
- With new phones / new Zalo: Synchronize messages
If you have not turned on Backup and sync messages
Step 1: Go to Settings
Step 2: Select Backup and sync messages

Step 3: Turn on Backup and Sync
Step 4: Complete Backup and sync messages
If you have turned on Backup and sync messages every day, but still need to back up the latest messages, tap “Back up & sync now”.
You switched to a new phone and never recovered your messages. You will receive a message from Zalo asking "Do you want to restore old messages?" Just press "Agree" to restore.
If you press Ignore or do not receive the above message, synchronize the message by:
Step 1: Go to Settings
Step 2: Select Backup and sync messages
Step 3: Turn on Backup and Sync
Step 4: Complete Backup and sync messages
For Android phones, you can also sync photos by “Click to add an account”, then enter your Google Drive account.
With the SMS Backup and Restore feature, you can comfortably use your new phone or reload Zalo without having to "fret" about losing important messages.
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.