Like many companies we use network home directories for our desktop Mac users. This works fine for most properly written applications even somewhat misbehaving ones like Microsoft Office. The less said about Adobe the better.
Unfortunately if you try setting up OmniPresence to a folder within the users network home directory which of course means on a network file server then OmniPresence rejects this because it is not on a local disk.
One of the reasons to use network home directories is to ensure files by being stored on a server are backed up, and another other is to prevent potentially confidential files being left on desktop computers.
As far as I can see this should be perfectly possible for OmniGroup to achieve along the following lines.
- User logs in to computer as a network login
- Login triggers standard user (not system) launch agent for OmniPresence
- Launch agent runs OmniPresence (this assumes user has set OmniPresence to auto start)
- OmniPresence syncs between OmniGroup server or webdav server to folder and should support both local and network paths
- Obviously if the path is not found an error should be given.
I cannot change the entire company from network home directories just for the benefit of one misbehaving program. A potential workaround but highly undesirable might be to use something like ChronoSync to do a bi-directional sync between the webdav folder and the users network home directory, i.e. to effectively use ChronoSync to replace OmniPresence. This effectively would add a 50% cost overhead to OmniOutliner Pro.