Coyote User Cases
A company hires a contractor to build some web pages. The contractor is given a Coyote server, and the Coyote client is installed in the web server directory he is building. Pages are automatically replicated from the developer's hard drive directly to the web server without the contractor needing FTP access. After the contractor has finished, the Coyote server is useless to the contractor without the matching Coyote client.
An insurance company maintains a web server in the DMZ, and wishes to replicate insurance claims from a directory on the web server to another server used for internal use without opening up FTP ports, or NetBIOS. The Coyote server runs on the web server in the claims directory, and the Coyote client replicates all the claims to an internal server for staff use.
A medical professional maintains his EMR (electronic medical records) on his laptop, which he uses for all this consultations, both at his surgery, and when he visits the hospital. Back in the office, as soon as he connects up to his network, both the Coyote server and client reconnect automatically, and his new data is backed up to the surgery servers. No effort is required to ensure that his important data is always kept backed up.
A technician needs to recover files off a windows pc where the operating system has crashed. He boots with a Bart PE cdrom which has the Coyote server installed. He then configures the Coyote server to run in the root of the directories he wants to recover data from. There is no need to configure workgroups, or to join a domain, to get access to the files.
