Hello econnell,
You actually have feature parity (or the ability to add that parity) between Windows and OS X agents on this matter - but as you stated it is not well documented.
Immediate activation:
The OS X agent acts slightly different from the Windows agent during installation. The Windows agent installs and does not attempt to broker immediately unless you edit the installer and add a broker -r command to it. The OS X agent however already has the broker -r command added in. This means that if the OS X agent is in-band (can reach core and CSA) during installation it will (mixed results here) automatically broker.
Activation via policy:
In the case that this fails you may also create a sh script to execute the following command via policy on any device that is not brokered, but is in-band.
#!/bin/sh
/usr/LANDesk/common/brokerconfig -r
Activation while out-of-band:
The Windows agent supports using a .lng file for out-of-band brokering: Unattended configuration of client for the Cloud Services Appliance
The Windows agent may also be brokered using the ldgatewayassistant: LDGatewayAssistant [Windows Version] or LDGatewayAssistant – Windows Version
The OS X agent may be brokered using the ldgatewayassistant: LDGatewayAssistant [Macintosh Version] or LDGatewayAssistant – OSX Version
*Note: I have not released a new version of the ldgatewayassistant yet to support the new miniscan technology - so it may not function correctly with 9.6.1 Windows agents. The service will likely crash. The OS X version should still work though.
Hopefully this helps,
Peter