FreeIPA server installation prerequisites
Preparing hosts for FreeIPA: ports to open, time synchronization with chrony, host name and reverse DNS rules, crypto policy, umask and fapolicyd pitfalls, and the packages for DNS and AD trust roles.

Installing FreeIPA servers and keeping them running: prerequisites, containers, platform choice, backups, disaster recovery, health checks, audit logs and ID range repair.
Preparing hosts for FreeIPA: ports to open, time synchronization with chrony, host name and reverse DNS rules, crypto policy, umask and fapolicyd pitfalls, and the packages for DNS and AD trust roles.
Running FreeIPA in Podman or Docker with the project's freeipa-server images: choosing the base OS tag, persistent data, registries, rebuild cadence and where containers make sense.
Picking the OS under FreeIPA servers: Fedora's fast cadence versus enterprise distributions, Red Hat support for RHEL IdM, client support boundaries, and lifecycle planning.
Backing up FreeIPA properly: full versus online data backups, running on a server with every role, storage locations, restore requirements, re-initializing replicas afterwards, and Ansible backup roles.
What to do when the FreeIPA server that renews certificates is lost: promoting another CA replica, cleaning agreements, installing a replacement, and the case where recovery is impossible.
Using VM snapshots to recover FreeIPA after multiple server loss or data corruption: snapshot-only, partially working and new-environment scenarios, and checking replication afterwards.
Running ipa-healthcheck on every server: what it checks, failures-only output, the systemd timer and log directory, and feeding results into monitoring and alerting.
Finding who changed users, groups, hosts and policies in FreeIPA: API calls in Apache logs, changes made directly against LDAP as root, and centralizing logs for audits.
Repairing users and groups outside configured FreeIPA ID ranges with the ipa-idrange-fix tool added in 4.13, and preventing range conflicts after migrations and AD trusts.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.