UMC configuration on DSfW Domain Controllers (FRD, ADC, or CDC) fail in Name-Mapped and Non Name-mapped DSfW setup. UMC is unable to detect the existing UMC server in the same tree.
The Samba shares cannot be created in iManager because the NCP Server object fails to load during the process. However Samba shares can be created in the smb.conf file.
CIS pattern cannot be installed on Name-Mapped and Non-Name-Mapped DSfW servers.
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.
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.
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 OpenText products for information on interoperability issues with DSfW.
On an OES 2018 server with DSfW installed, the Endpoint Security Management utility fails on all DSfW server ports.
OpenText has no current plans to change this.