DirectManage™ Deployment Manager 5.4.0 Release Notes

© 2008-2017 Centrify Corporation.

This software is protected by international copyright laws.

All Rights Reserved.

Table of Contents


1.      About This Release. 1

2.      Feature Changes. 2

2.1.       Feature Changes in Deployment Manager 5.4.0 (Suite 2017) 2

2.2.       Feature Changes in Deployment Manager 5.3.1 (Suite 2016.1) 2

2.3.       Feature Changes in Deployment Manager 5.3.0 (Suite 2016) 2

3.      Bugs Fixed. 2

3.1.       Bugs Fixed in Deployment Manager 5.4.0 (Suite 2017) 2

3.2.       Bugs Fixed in Deployment Manager 5.3.1 (Suite 2016.1) 2

3.3.       Bugs Fixed in Deployment Manager 5.3.0 (Suite 2016) 3

4.      Known Issues. 3

5.      Additional Information and Support 5


1.    About This Release


DirectManage Deployment Manager is part of Centrify Server Suite.  It enables you to identify non-Windows computers within your environment and analyze their readiness to integrate with DirectControl and Active Directory, as well as perform deployment of editions of Centrify Server Suite to these computers.


We recommend that you download the latest Centrify product catalog from Centrify Download Center in case it contains a newer catalog than what is provided with this release.


For a list of the supported platforms by this release, refer to the “Supported Platforms” section in the Centrify Suite release notes.

For a list of platforms that Centrify will remove support in upcoming releases, refer to the “Notice of Termination Support” section in the Centrify Suite release notes. 

The Centrify Server Suite release notes and documents are available online at

Centrify software is protected by U.S. Patent No. 7,591,005, 8,024,360, 8,321,523, 9,015,103 B2, 9,112,846, 9,197,670 and 9,378,391. (Ref: CS-40830)

2.    Feature Changes


2.1.        Feature Changes in Deployment Manager 5.4.0 (Suite 2017)


·        Allow deployment to some newly supported platforms for Centrify Server Suite. For a list of the supported platforms by this release, refer to the “Supported Platforms” section in the Centrify Suite release notes. (Ref: CS-41271)

2.2.        Feature Changes in Deployment Manager 5.3.1 (Suite 2016.1)


·        Centrify product catalog is separated from Deployment Manager setup package. The product catalog will only be imported into the repository when Deployment Manager is installed from Centrify Server Suite ISO. (Ref: CS-37610).

2.3.        Feature Changes in Deployment Manager 5.3.0 (Suite 2016)


·        Deployment Manager now supports public key authentication using AES-128-CBC encrypted keys (Ref: CS-38600).

·        In manage software wizard, installed components will be automatically selected for upgrade (Ref: CS-38266).

·        In “Manage Audit”, Deployment Manager now supports change of DirectAudit Installation name on computers allowing locally configured installation (Ref: CS-38035).

·        Termination of support of Deployment Manager on platform: (Ref: CS-38998)

-   All 32-bit Windows platforms

3.    Bugs Fixed


3.1.        Bugs Fixed in Deployment Manager 5.4.0 (Suite 2017)


·        N/A

3.2.        Bugs Fixed in Deployment Manager 5.3.1 (Suite 2016.1)


·        N/A

3.3.        Bugs Fixed in Deployment Manager 5.3.0 (Suite 2016)


·        Deployment Manager fails to discover computers supporting SHA256 KEX algorithms in SSH connection on FIPS-enabled environment previously (Ref: CS-38314). The issue is now fixed.

4.    Known Issues


The following sections describe common known issues or limitations associated with DirectManage Deployment Manager. 

·        Please note that Deployment Manager requires the Centrify product catalog to be imported first before using the "Download Software" feature. For example, when you download the software bundles from the Centrify Server Suite ISO into a local or network drive which is then specified as the software location, if Deployment Manager was installed from Centrify Server Suite ISO, Deployment Manager will detect only the adcheck packages if the product catalog is not imported; if Deployment Manager was installed by standalone package downloaded from Centrify Download Center, Deployment Manager will not be able to detect any package if the product catalog is not imported. You can import the product catalog manually in the Deployment Manager console root node context menu.

·        In the Centrify Profile tab of the Properties page of a computer joined to a hierarchical zone, you cannot move this computer to a classic zone. Nor can you move it to a zone in another domain. There are no such problems with a computer joined to a classic zone.

·        When joining a computer to a zone, if the container's name starts with a '/' or contains space(s), the join operation will fail.

·        Deployment Manager may not be able to discover a HPUX 11.23 machine if it’s DNS is not configured properly.

·        The "UNIX name" field on the Properties dialog for a local user or local group on an AIX computer is disabled. This is because the chuser and chgroup commands do not allow for name change.

·        Deployment Manager will report an error when creating a local user on a HPUX machine in trusted mode. This is because it cannot set the password for the new user. The newly created user also cannot login since the password is not set.

·        On some platforms such as Red Hat, you cannot change a local user's password when the user name is the same as an AD user.

·        The Reset Password feature is disabled for a local user on a HPUX machine running in trusted mode. This feature is not allowed in trusted mode.

·        On a HPUX machine, it is possible that some actions to add, edit or map local users may fail due to the length of the command that Deployment Manager sends to HPUX to perform the action. For examples, a user may have long GECOS or home directory paths; using sudo instead of root to execute the command may also lengthen it.

·        If you have both pre v5.0 Centrify DirectControl Administrator console and Deployment Manager installed, and then un-install the DirectControl Administrator console, the welcome page of the Deployment Manager is no longer accessible. This does not happen if the Centrify DirectControl Administrator console is v5.0 0 and above or you are using Centrify DirectManage Access Manager.

·        We recommend that you DO NOT launch multiple instances of Deployment Manager. If you run multiple instances at the same time you may experience the following problems:

-   The UI between the consoles is not synchronized.

-   There will be a chance of database conflicts. For example, analyzing computers would have a greater chance of failing as it may not be able to update the database.

·        History records contain non-printing characters 

There may be some non-printing characters displayed in the history records after running analysis; these are usually control characters captured while capturing the history and may be ignored. 

·        Special user accounts on AIX 

UIDs imported for special user accounts on AIX will be displayed as negative numbers. The UIDs are correct, it is just the display that is incorrect, and this may be ignored. 

·        System.AccessViolationException shown

Occasionally Deployment Manager will show an error dialog box reporting a System.AccessViolationException due to an attempt to read or write protected memory due to a problem with SQL CE. You should restart Deployment Manager if you encounter this. 

·        Can discover a computer but cannot deploy software if SSH service is not functioning.

Deployment Manager relies on the SSH service on a discovered computer for information gathering and software deployment. If the SSH service is running but not functioning correctly, Deployment Manager cannot retrieve additional information nor deploy software to it. 

·        Access violations occur when run under heavy load

This is a known issue with Microsoft SQLCE. You can find more information about this, including a patch to fix it, at:

·        Deployment Manager will report that there is no software on the local system even though it successfully downloaded to a VMware Shared Folder. VMware Shared Folders do not trigger file system notifications so Deployment Manager is not notified.

·        MMC crash after switching from UNIX name filter to History Node (Ref: 23122/CS-37045)

This is how it may happen:

-   “Users” node is selected and some characters are typed into “UNIX Name” filter

-   Then select “History” node as soon as possible after deleting the characters in previous filter

·        Deployment Manager does not work on computers by using accounts that require multi-factor authentication when login or execute commands (Ref: CS-38698)

·        You cannot deploy the Suite 2016 Mac agent using the Deployment Manager in Suite 2015.1 or older. This is due to system file changes introduced in Mac 10.11 OS, and old Deployment Managers prior to the Mac 10.11 release cannot handle this change. The new Deployment Manager in Suite 2016 will handle the upgrade correctly. (Ref: CS-39320)

For the most up to date list of known issues, please login to the Customer Support Portal at and refer to Knowledge Base articles for any known issues with the release.

5.    Additional Information and Support


In addition to the documentation provided with this package, you can find the answers to common questions and information about any general or platform-specific known limitations as well as tips and suggestions from the Centrify Knowledge Base.

You can also contact Centrify Support directly with your questions through the Centrify Web site, by email, or by telephone. To contact Centrify Support or to get help with installing or using this software, send email to or call 1-669-444-5200, option 2. For information about purchasing or evaluating Centrify products, send email to