Utilising statically configured binding with an "Open Directory" template
in Directory Access populates the full preference file including the
references to read-only and writable replicas.
<?xml version="1.0"
encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD
PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist
version="1.0">
<dict>
<key>LDAP PlugIn
Version</key>
<string>DSLDAPv3PlugIn Version
1.5</string>
</dict>
</plist>
The above is an expected behaviour with DHCP deployment of the
preferences - so that your computers can roam to other locations and receive
their configurations dynamically without any pre-existing configurations
clouding the way they behave.
A suggestion to facilitate failover could be to use a DNS hostname A
records for each of your OD servers (replica and master). Then send that
hostname to your DHCP-configured clients. For example:
Instead of using: server01.mydomain.com
Use:
ldap.mydomain.com
Which resolves to server01.mydomain.com as well as
replica01.mydomain.com.
Because the Password server is multi-master, and the Kerberos KDC
password changes are performed only through the OD Master's Kerberos KDC, you
should still be able to change passwords etc as you used to (as long as the OD
Master is running!)
