Apache OpenOffice (AOO) Bugzilla – Issue 13110
Need method for dealing with mandatory profiles
Last modified: 2013-02-07 22:37:02 UTC
No apparent way of installing OOo for all users as opposed to individual ones. Within a locked down environment (many users, any machine), the use of mandatory, non-roaming profiles is usual - this makes the process of each user installing their part of OOo impossible or at best implausible (the local profile is temporary, and they can't write to the network profile). Applies to NT4 as well as later versions. Any and all suggestions welcome - this is preventing rollout across a number of school sites (~5000+ users).
Hi Bettina, please have a look.
Set to "NEW"
OpenOffice.org Issue Tracker - Feedback Request. The Issue you raised has the status 'New' pending further action, but has not been updated within the last 4 years. Please consider re-testing with one of the latest versions of OOo, as the problem(s) may have already been addressed. Either use the recent stable version: http://download.openoffice.org/index.html or consider trying the new OOo 3 BETA (still in testing): http://download.openoffice.org/3.0beta/ Please report back the outcome so this Issue may be Closed or Progressed as necessary - otherwise it may be Resolved as Invalid in the future. You may also wish to search for (and note) any duplicates of this Issue that may have advanced further by checking the Issue Tracker: http://www.openoffice.org/issues/query.cgi Many thanks, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
Please consider re-testing with one of the latest versions of OOo and providing an update / further information. Cheers. Lowering Issue priority... From: http://qa.openoffice.org/scdocs/ddIssues_EnterModify.html#priority P2 - Marks severe problems which affect a significant number of customers. Issues with this priority must be fixed before the target release ... and should be dealt with as soon as possible. Not fixing them for the target release is not acceptable.
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".