On 05/30/2007 03:28 PM, Pueblo Native wrote: > > The software is free, but there might be a few other reasons to want a > client-server model, particularly if you have several hundred computers > to work with. I know I wouldn't want to be the IT guy stuck upgrading > each and every one of those computers.
I know I wouldn't want to be the IT guy that has to manage many remote OOo users that are on a central server and are accessing via a web client. LES COLEMAN wrote: > VPN, load the Microsoft replacement (OpenOffice) on the host server, > thus requiring a single version of the software, and then access via > web-browsers (IE or Firefox) using either public or private lines. > Nothing would actually be installed at the workstation end. I've implemented OOo on a central server to lan connected workstations & that works fairly well. And I design, install, and manage multiple VPN networks for my customers - including remote terminal services to a central inventory management system. However I would *never* attempt to implement OOo across a VPN via HTTP, or even via a VPN terminal service - unless of course I had a huge budget & owned some very large data pipes. It's just too data intensive of an application, and if you think folks complain now about OOo, just try it via a slow VPN or network connection. Question for Les: do you implement MS Office in this way now? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
