Applies to: All versions of Centrify DirectControl in a Solaris Zones environment
How to configure time synchronization when using Solaris Zones?
Ensure that the Solaris Global Zone is joined to the Active Directory Domain.
Option 1: Have DirectControl (adclient) manage the time synchronization:
In /etc/centrifydc/centrifydc.conf, leave the parameter at the default
- This will have adclient sync time with the Active Directory domain.
- Turn off ntpd on the Solaris Global Zone (as ntpd will override adclient).
Option 2: Have ntpd in the Solaris Global Zone to manage the time synchronization
In some cases, turning off ntpd may not be an option or not desired. In this case, set:
In /etc/centrifydc/centrifydc.conf and restart adclient using:
Now the Solaris Global Zone will use ntpd to synchronize its time.
However, it is important to note that if the "time authority" that ntpd is pointing to is off by more than 5 minutes with the Active Directory domain, Kerberos will not allow AD user authentication (this concern is only when the time authority is not the Active Directory domain; as is often the case in a Unix environment).
The time authority must be ensured to be within 5 minutes of the Active Directory domain clock.
In either case, time sync failure messages in the Solaris Child Zones may be noticed. This is normal and does not have to do with DirectControl, but with Solaris Zones if there are multiple virtual machines using one physical clock. To suppress these messages, simply turn off sntp in each Solaris Child Zone. Turning off sntp in each Child Zone has no negative functional effect.