As far as I know, there's no way to export an OBi Expert configuration. Like you, I feel this is a significant deficiency if OBi Expert is to be used for unattended remote configuration. A remote login capability in the OBi would be a much better approach for remote configuration and would totally avoid this business of trying to maintain a mirror of the OBi's configuration on someone else's web site which you have no control over.
In general, be it a local or unattended remote installation, if one gets to relying completely on OBiTALK / OBi Expert for configuration and the OBiTALK web server goes down, you're hung out to dry. If you revert to configuring the OBi directly, you've got to remember to disable auto-provisioning to avoid having your changes wiped out when the server is restored. Then if you want to return to using OBiTALK / OBi Expert for configuration, you've got to first get the server caught up manually with any changes you've made in its absence before you can re-enable auto-provisioning.
For the first time user, OBiTALK is a great way to get up and running quickly. It can also serve as a tool to learn what goes into actually configuring an OBi by observing the parameters it generates for a particular scenario that it's capable of handling. If your needs are reasonably simple and OBiTALK configures everything you need, then you're done.
But for things that are beyond what OBiTALK can handle, the picture changes. Except for the isolated case of unattended remote configuration (needed due to the lack of remote login capability), I just don't see what configuring through OBi Expert accomplishes over making changes locally. If you possess the knowledge necessary to use OBi Expert, then you don't need it (or OBiTALK) and it only adds to the complexity. But all this is just one person's opinion.
