Difference between revisions of "Documentation/Administration Guide/How to deploy OpenOffice.org though a network"
From Apache OpenOffice Wiki
| Line 5: | Line 5: | ||
|NextPage=Documentation/Administration Guide/Solaris | |NextPage=Documentation/Administration Guide/Solaris | ||
}} | }} | ||
| − | {{DISPLAYTITLE: | + | {{DISPLAYTITLE:Deploy OpenOffice.org using installation package managers}} |
The OpenOffice.org installer can use the most popular installation packages for each platform (Solaris pkg, Linux RPM and DEB, and Windows MSI), and network administrators can use the command line interface to deploy {{OOo}} through the network. | The OpenOffice.org installer can use the most popular installation packages for each platform (Solaris pkg, Linux RPM and DEB, and Windows MSI), and network administrators can use the command line interface to deploy {{OOo}} through the network. | ||
{{PDL1}} | {{PDL1}} | ||
Revision as of 07:55, 22 July 2008
- Deploy Apache OpenOffice using package managers
- Apache OpenOffice Basic Macros and Libraries
- Apache OpenOffice Extension Manager
- Adding Template Files to an Apache OpenOffice Installation
- Adding AutoText Files to an Apache OpenOffice Network Installation
- Deactivating the Apache OpenOffice Registration Wizard
- Accessing Email Clients
- Customizing the User Interface
- Restricting Functionality in Apache OpenOffice
- Accessing Apache OpenOffice User Profiles on an LDAP Server
The OpenOffice.org installer can use the most popular installation packages for each platform (Solaris pkg, Linux RPM and DEB, and Windows MSI), and network administrators can use the command line interface to deploy Apache OpenOffice through the network.
| Content on this page is licensed under the Public Documentation License (PDL). |
