Open Directory Replication 10.8.5 problems with Kerio Connnect 8.3.0

I recently was hired to implement an Open Directory Master/Replica into a network that wanted to leverage Kerio Connect mail server. At first, all seemed fine. I created the directory, the replica, and installed the kerio extension on both servers as was instructed by the fine folks at Kerio. Now I’d just like to say that this is different than what I remember in the days of 10.6. Back then you only had to install the OD extension on the master, the replica would then copy the schema over so that it could import the extended schema data at that time.

The problem comes into play when you have a master with already provisioned users in Kerio and you want to add an OD replica. Since the replica does not copy over the extended LDAP schema it is unable to replicate any provisioned users. The result is that those users will not exist in the replica which is bad news if you have services relying on that replica. To resolve this problem use the following procedure on the replica you wish to build:

sudo slapconfig -createreplica <master IP> diradmin

Once complete install the Kerio extention.

slapconfig -stopldapserver
slapadd -v -F /etc/openldap/slapd.d -c -l /var/db/openldap/openldap-data/backup.ldif
slapconfig -startldapserver


#gowellandinpiece
#replication

How to Force Propagation on Apple Secondary DNS Server

As you all probably know that using Apple’s DNS server can be challenging at times. If you make changes on the primary you usually have to wait some time before those changes propagate to the secondaries. However with the following commands you can force this propagation without having to nuke files or folders in /var/named

1. On the secondary server, run this command. (use whatever zone you want to transfer in place of lan.example.com
rndc -p 54 retransfer lan.example.com IN com.apple.ServerAdmin.DNS.public

2. Reload configuration
rndc -p 54 reload

3. Forcing client cache flush
dscacheutil -flushcache

The reason I think this is better in my opinion is it gets rid of the potential “oops” of deleting critical files in /var/named.

How To RAID Mac Mini Server without Reinstalling

Replicate boot drive to spare drive.

While this post title specifically says Mac Mini Server, this procedure will work with any Macintosh that has more than one hard drive.

1. Open Disk Utility
   One drive should be labelled “Server HD” and the other “Macintosh HD2” Remember which one is on top and which one is on bottom.
2. Select the Hard Drive associated with Macintosh HD2, and then click Restore
3. Drag Server HD in to the source and Macintosh HD2 into the destination
4. Make it go

Build the spare drive into a RAID of one disk

1. Open Disk Utility
2. Select the Hard Drive associated with old “Macintosh HD2”, and then click RAID.
   If you unsure as to which is which you can select the drive and note the mount point at the bottom of the window. Choose the one that DOES NOT have the mount point of “/”
3. Set the following options
   RAID Set Name: Server HD RAID
   Format: Mac OS Extended (Case-Sensitive, Journaled)
   RAID Type: Mirrored RAID Set
4. Drag the spare Server HD from the list on the left into the box on the right.
5. Select Options and enable “Automatically rebuild RAID mirror sets” Click OK then Enable
6. Rename the newly built drive to Server RAID
7. Go to System Preferences->Startup Disk and select the newly built RAID.
8. Reboot

Integrate Other Drive into RAID

1. Once the system is booted verify the RAID drive is the boot volume
   To do this open Disk Utility again and select the Server RAID volume, make sure the mount point states “/”
2. While in Disk Utility select the RAID device, which is located above “Server RAID” and click on the RAID tab
3. Drag “Server HD” into the white box on the right to add it to the RAID
4. Click Rebuild, it will take some time. Once done perform one more reboot and you’re finished!