That is an interesting question Franz. I'm sorry I don't have an answer for you but I am having a great many issues with my DSfW and looking at possible solutions. 

I have an issue where certain applications will not run if a user logs onto their workstation using a DSfW domain account but the issue does not exist if the domain controller is a Windows server.

I'm not yet ready to abandon DSfW completely but I was wondering if I could introduce a Windows Server into the mix and make it a domain controller thereby eliminating issues I have when accessing my DSfW servers.

I was told a while ago that this is not possible. I have not ran into many issues with DSFW for what wanted it for. Has worked very reliably for sure. Still on OES 2018 SP2 for the only because they are running so solid. Considering trying to take one to 2023 but honestly a little concerned with that as well as not sure where they are going with it. The biggest thing being asked is for the Azure support which don't even know if that will ever come now.

Well, my problem is that the functionality is about OK, but the stability is bad :-( . Our network is quite heterogeneous and since samba-4.13 a starting winbindd tends to crash the rpcd on DSfW. Additionally ndsd leaks memory and has to be restarted about once a week. Both problems have been reported, but no solution since over a year. The leaking memory SR even has been closed after the leak was mitigated a bit.

Well, my problem is that the functionality is about OK, but the stability is bad :-( . Our network is quite heterogeneous and since samba-4.13 a starting winbindd tends to crash the rpcd on DSfW. Additionally ndsd leaks memory and has to be restarted about once a week. Both problems have been reported, but no solution since over a year. The leaking memory SR even has been closed after the leak was mitigated a bit.

Franz Sirl said:

The leaking memory SR even has been closed after the leak was mitigated a bit.

I have had many similar experiences. Micro Focus technical support has been helpful but as soon as a defect is created for the developers to investigate things seem to fall apart. I've has a dozen cases opened and one by one they get closed without the defect getting resolved.

I have seen rpcd crashing very frequently on OES 2018 SP1.

Workaround is to set to following in /usr/lib/systemd/system/rpcd.service:

Restart=on-failure
RestartSec=5s

Then run: systemctl daemon-reload

I have seen "only" two rpcd crashes on OES2023 in 42 days thus far.

OES2023 is running stable for us otherwise.