After Cloning and Deploying XenApp 6.5 Servers in VMware in the Farm, IMA Fails to Start and Servers Cannot Join the Farm With Error 2144534512

After Cloning and Deploying XenApp 6.5 Servers in VMware in the Farm, IMA Fails to Start and Servers Cannot Join the Farm With Error 2144534512

book

Article ID: CTX134759

calendar_today

Updated On:

Description

After cloning XenApp 6.5 servers in VMware and deploying them to the farm, IMA fails to start and servers are unable to join the farm and the following error appears:
User-added image

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Complete the following steps to resolve the issue:

  1. Open the registry editor on the cloned server having the issue and find the following registry key: 
    HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\RUNTIME\HostName
    User-added image

  1. Notice the hostname of the VM on the top left corner is a different name from the hostname in the regitry key. The hostname on this server is the hostname of the template server. Change the hostname key to match the actual hostname of the server.
    User-added image

  1. Reseal the server with the new information after the hostname is changed. This can be done by opening the XenApp Server Role Manager.
    User-added image

  1. Open the XenApp Server Role manager, select the Edit Configuration option.
    User-added image

  1. Select the option Prepare this Server for Imaging and Provisioning.
    User-added image

  1. Uncheck the option Remove the Current Server Instance from the farm, and Click Next.
    User-added image

  1. Once completed “Server configured successfully!” is displayed.
    User-added image

  2. Now you must select the option to Reboot the server, once selected and the server is backed up, the server should now be placed in your farm.
    User-added image

Problem Cause

This error may occur if when cloning XenApp 6.5 servers from VMware through a template, the hostnames of the servers either hold their original hostname, or the hostname of the template server.

Issue/Introduction

This article provides resolution when cloning XenApp 6.5 or 6.0 servers from VMware through a template, the hostnames of the servers either hold their original hostname, or the hostname of the template server.
Powered by Wolken Software