Restore VM agent connection to CloudLink Center If an encrypted VM uses an incorrect IPv4 address for CloudLink Center, the VM may not start. The boot screen displays the IP address of the encrypted VM along with the hostname or the IP address that the VM is using for CloudLink. After few minutes, the encrypted VM automatically searches all the IPs in the subnet the VM is located, and tries to identify the correct IP address of the CloudLink Center. If the encrypted VM is unable to locate the CloudLink Center, perform the following workarounds: Applies for IPv4 address—Deploy a new CloudLink cluster member on the subnet in which the encrypted VM failing to restart is located. If the VM restarts, ensure that the agent has the correct CloudLink Center hostname or IP address. If the correct hostname or IP address is not displayed, decrypt the VM and reinstall the agent with the correct CloudLink Center hostname or IP address. Applies for IPv4 and IPv6 addresses—If the VM does not restart using the preceding workaround, then: Power off the VM and attach the encrypted boot drive as a data drive on a Windows VM that has the CloudLink Agent. Use CloudLink Center to decrypt the data drive. The data drive displays the status as Pending. Manually accept the data drive in CloudLink Center. After the drive is decrypted, remove the data drive from the Windows VM and power on the VM. NOTE: Do not attach a Windows boot drive to a Windows VM that has the same disk signature. Microsoft operating system changes the disk signature which corrupts the data drive. NOTE: If the preceding workarounds do not work, then contact Dell Technologies Support to Install the redirect application.