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. 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. Change the Master vRealize Automation Appliance Host NameWhen maintaining an environment or network, you might need to assign a different host name to an existing master vRealize Automation appliance. Change a Replica vRealize Automation Appliance Host NameWhen maintaining an environment or network, you might need to assign a different host name to an existing replica vRealize Automation appliance. 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.