After you install vRealize Automation, there are post-installation tasks that might need your attention. Configure Federal Information Processing Standard Compliant EncryptionYou can enable or disable Federal Information Processing Standard (FIPS) 140–2 compliant cryptography for inbound and outbound vRealize Automation appliance network traffic. Enable Automatic Manager Service FailoverAutomatic Manager Service failover is disabled by default if you install or upgrade the Manager Service with the standard vRealize Automation Windows installer. Automatic vRealize Automation PostgreSQL Database FailoverIn a high availability vRealize Automation deployment, some configurations allow the embedded vRealize Automation PostgreSQL database to fail over automatically. Replacing Self-Signed Certificates with Certificates Provided by an AuthorityIf you installed vRealize Automation with self-signed certificates, you might want to replace them with certificates provided by a certificate authority before deploying to production. Activate FQDN for RabbitMQ After InstallationYou can activate FQDN support in vRealize Automation RabbitMQ post-installation. Changing Host Names and IP AddressesIn general, you should expect to keep the host names, FQDNs, and IP addresses that you planned for vRealize Automation systems. Some post-installation changes are possible but can be complicated. Removing a vRealize Automation Appliance from a ClusterIn some cases, you might need to remove a vRealize Automation appliance in the course of maintaining your environment. Licensing vRealize Code StreamA vRealize Automation license can enable vRealize Code Stream for your vRealize Automation environments. Installing the vRealize Log Insight Agent on IaaS ServersThe Windows servers in a vRealize Automation IaaS configuration do not include the vRealize Log Insight agent by default. Configure Access to the Default TenantYou must grant your team access rights to the default tenant before they can begin configuring vRealize Automation.