Working in Num Sum, however, was a bit slow; same with Google Spreadsheets.
Importing a presentation is easy, and it even took a basic one I whipped together in OpenOffice.
Two solutions, Neverfail for Exchange and SteelEye LifeKeeper, bring true fail-over to an entire Exchange server. Setting up LifeKeeper is straightforward.
Spreadsheets can handle formulas, but they choked on the electronic form sheet like everyone else. For example, past versions of Jtest generated tests at the class level.
Importing from my own library of spreadsheets was no problem, including formula support.
I tried to enlist him for this piece, but he threw a stapler at my head, so I stopped asking.
You will need to create service accounts, as with the other solutions, but the documentation steps you through the process. It means more time spent on e-mail maintenance than I ever had to do using a desktop client. It takes snapshots of server performance and performs trend analysis to identify areas that may become problems in the future.
Working in Num Sum, however, was a bit slow; same with Google Spreadsheets. Spreadsheets can handle formulas, but they choked on the electronic form sheet like everyone else. Your preferences may vary. The time necessary for this process will depend on the amount of e-mail stored in the inbox. If the primary server experiences a hardware or software failure, the secondary server assumes its IP address and hostname and resumes operation.
I observed the Outlook client experience when the primary server failed, as well as the time required to fail over to the secondary server.
It also seemed slower than Zoho. That meant nonstandard margins, different style headings, and loads of tables. If Outlook has it, I want it in my Web client.
It also seemed slower than Zoho.
Spreadsheets can handle formulas, but they choked on the electronic form sheet like everyone else.
Because the replication is based on transactions, no corruption of the Exchange database is passed on to the backup. It takes snapshots of server performance and performs trend analysis to identify areas that may become problems in the future.
Surprisingly, Zoho handled the tables just fine, but lost out on the margins and styles a bit.
It also seemed slower than Zoho. Locally installed applications are simply more reliable and feature-rich. Both of these are highly capable browser-based e-mail clients, but they are primarily designed to run with their own e-mail servers. Importing a presentation is easy, and it even took a basic one I whipped together in OpenOffice. Collaboration is fair, including a shared area to which you can invite team members, as well as discussion boards you can setup.
The interval between failure of the primary server and starting the secondary server is short, about two minutes in my testing. A low-bandwidth module is available that enables compression and encryption over a WAN link, as well as asynchronous replication. That was no trouble because the office had guest Internet access and a steady Wi-Fi connection. If the primary server experiences a hardware or software failure, the secondary server assumes its IP address and hostname and resumes operation. It takes snapshots of server performance and performs trend analysis to identify areas that may become problems in the future. After all, whenever Google waves its hands in this direction, the pundits swoon. Zoho displayed a few dozen cells of one-letter gobbledygook and also claimed success.
Then it also had the wiki, blogging, and other collaboration tools that make the Web the bane of SharePoint.