2.4 Domain Services for Windows (DSfW)

2.4.1 CIS Pattern Conflict in DSfW Name-Mapped/Non-Name-Mapped Servers

CIS pattern cannot be installed on Name-Mapped and Non-Name-Mapped DSfW servers.

2.4.2 Workaround for DSFW Name-Mapped Tree

On a Name-Mapped deployment, CIS is installed on the eDirectory server and DSfW is installed on a partitioned container. Dashboard is not able to fetch DSfW server details since CIS and DSfW are in different domains.

Workaround: DSfW domain DNS is added as a primary DNS in the eDirectory server where CIS is installed. With this change CIS resolves DSfW domain and started fetching DSFW server details.

2.4.3 Mixed Mode Configuration is not Supported

Beginning with OES 2018 SP1, the DSfW domain controllers having OES 2018 SP1 or later and those having earlier OES versions cannot coexist in a forest. This is because of the functional incompatibility between the updated Kerberos version in OES 2018 SP1 and the Kerberos version in OES 2018 and earlier. All the DSfW servers in a forest must be on the same OES version and on the same patch level.

2.4.4 DSfW Interoperability Issues

IMPORTANT:The following list is provided for your convenience. Do not consider the list as complete. Be sure to consult the documentation for your other Micro Focus products for information on interoperability issues with DSfW.

ZENworks Endpoint Security Management 3.5

On an OES 2018 server with DSfW installed, the Endpoint Security Management utility fails on all DSfW server ports.

Micro Focus has no current plans to change this.