do you ask mr google or mrs google? there are significant difference between!!! HAhaHA!!!

But the community can help or open a case by OT!

Hello Tamás,

I encountered the same issue.

Opened a case and got the next instructions from support.

mkdir -p /var/lib/chrony/var/opt/novell/xad/rpc
Restart w32tm_client (systemctl restart w32tm_client)

Ted

Hello Ted!

Thank you for the answer. I have got the same advice from the support, but it didn't help. The status of the w32tm_client.service is masked. And the service is inactive(dead) after restart.

Tamás

Hello Tamás,

I forgot to mention that before I followed mentioned instructions I chanded the next line of file /opt/novell/xad/sbin/start-w32tm_client
From
IS_NTP_CHROOT=$(sed -n 's/NTPD_RUN_CHROOTED="\(.*\)"/\1/p' /etc/sysconfig/ntp)
into
IS_NTP_CHROOT=$(sed -n 's/NTPD_RUN_CHROOTED="\(.*\)"/\1/p' /etc/sysconfig/chronyd)

Make sure chronyd.service is running

Ted

Hello Ted!

Thank you again!

It's getting stranger. I have no /opt/novell/xad/sbin/start-w32tm_client file in that folder. But I found a rcw32tm_client with that line you advised. I changed it as you mentioned. Chronyd was running. I restarted it, but the result is the same.

I tried systemctl start w32tm_client and xadcntrl reload.

After that:

xadcntrl status says: w32tm client service inactive

systemctl status w32tm_client says: Loaded: masked (Reason: Unit w32tm_client.service is masked.) Active: inactive (dead)

I also tried to unmask the w32tm_client.service but no success.

Thank you!

Tamás

Hello,

have you solved the problem of loading w32tm_client.service, xad-krb5kdc.service and xad-kpasswdd.service after upgrading from OES 2018 SP3? I have the same problem.

Hello Jiri!

I suggest you to open a case at OpenText. When we had this problem the support solved this issue with remote access. In our case, the services are running now, but the clients still can't sync time with the DSfW.