Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-7137: Centrify Windows Agent MSI installation hangs when creating a new server from an image

Centrify DirectAudit ,   Centrify DirectControl ,  

6 July,16 at 09:09 PM

Applies to: All versions of Centrify Server Suite installed on a VMware virtual machine.

Problem:
The Centrify Windows agent is installed from an msi right after the server is created from an image in VMware. The Centrify installation hangs and must be stopped an installed manually for the agent to install properly.

Resolution:
The problem appears to be related to VMware Tools 10. Other programs installed as an msi have the same issue. Downgrading to VMware Tools 9 resolves the issue.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-3925: How to add Centrify parameter to a group policy articleKB-2727: How to migrate SQL databases associated with a Centrify_DirectManage Audit 3.x installation from one database server to another articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleKB-5180: Does PowerShell module support with DirectControl in classic zones? articleKB-6041: How to show current license type in use by adclient? articleKB-6040: How to change the license type in use after adclient successful joined to the AD?