7.4

2 In Windows, change the IP address.
Look for the IP address in the Windows network adapter settings, under Internet Protocol properties.
3 Refresh your local DNS with the changes.
Refreshing DNS ensures that the IaaS Windows servers can find each other and that you can
reconnect to a Windows server if you are disconnected.
4 On the Manager Service host, inspect the following file in a text editor.
install-folder\vCAC\Server\ManagerService.exe.config
The default install folder is C:\Program Files (x86)\VMware.
Verify IP addresses or FQDNs of vRealize Automation appliances and IaaS Windows servers.
5 On all IaaS Windows servers, inspect the following file in a text editor.
install-folder\vCAC\Management Agent\VMware.IaaS.Management.Agent.exe.Config
Verify the IP address or FQDN of the vRealize Automation appliance.
6 Log in to the SQL Server host.
7 Verify that the repository address is correctly configured to use FQDN in the ConnectionString
column.
For example, open SQL Management Studio and run the following query.
"SELECT Name, ConnectionString FROM [database-name].[DynamicOps.RepositoryModel].
[Models]"
8 Start the vRealize Automation appliance.
9 Start vRealize Automation services on IaaS servers.
10 Inspect log files to verify that Agent, DEM Worker, Manager Service, and Web host services started
successfully.
11 Log in to vRealize Automation as a user with the Infrastructure Administrator role.
12 Navigate to Infrastructure > Monitoring > Distributed Execution Status and verify that all services
are running.
13 Test for correct operation by checking appliance services, testing provisioning, or using the vRealize
Production Test tool.
Change an IaaS Server Host Name
When maintaining an environment or network, you might need to assign a different host name to an
existing vRealize Automation IaaS Windows server.
Procedure
1 Take a snapshot of the IaaS server.
Installing vRealize Automation
VMware, Inc. 139