Issue 16978 - File extension associations are installed incorrectly
Summary: File extension associations are installed incorrectly
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Windows 2000
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-16 18:21 UTC by gregmiller
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Setup Guide (1.41 MB, txt/pdf)
2003-07-17 08:37 UTC, Olaf Felka 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description gregmiller 2003-07-16 18:21:04 UTC 
After installing OOo 1.1RC on Win2K SP4, the file extension associations are
correctly installed under the Administrator account (the account where the
installation took place).  After logging off, and logging in under a user
account, none of the OOo file extension associations are present.  I did some
digging, and found that the installer seems to be assigning file extension
associations into the HKEY_CURRENT_USER tree.  I would think that proper
behavior would be to install the file extension associations to a location that
is used by all accounts (like HKEY_LOCAL_MACHINE?).
Comment 1 Olaf Felka 2003-07-17 08:36:01 UTC 
OOo isn't designed to work like that. You have to install OOo for
every local user.
Comment 2 Olaf Felka 2003-07-17 08:37:01 UTC 
Created attachment 7790 [details]
Setup Guide
Comment 3 gregmiller 2003-07-17 19:14:30 UTC 
In other words, READ THE ****ING MANUAL!!!  OK, after rolling out OOo
to over 1000 Windows PC's, I finally know how to properly install it!

The way I have always installed OOo is to log in as Administrator, and
just run the setup routine.  When the setup is finished, I copy the
sversion.ini file to each user's directory.  This seems to have worked
OK in the past, but 1.1RC puts the file associations in a different
place in the Registry.  Was this a bug with previous versions of OOo?
 Also, is there any way to lock the workstation installation so that
the individual users can not modify the installation or uninstall OOo
from their account?  When upgrading to a new version of OOo, I always
uninstall the previous version first.  How does this work with the
Server/Workstation installation method?  Do you have to uninstall from
each account, and then uninstall the Server, or does uninstalling the
Server remove everything from all accounts?  If I install the Server
OOo to a file server and then install the Workstation OOo to each
workstation in my company, can I upgrade OOo by simply replacing the
Server version or do I need to upgrade each individual Workstation
version as well?

Thanks!!!
Comment 4 Olaf Felka 2003-07-18 09:08:38 UTC 
- For 1.1 we put the reggitry settings to the user part of the registry.
- I don't know how to block a workstation installation of a user.
Please ask the community.
- We have integrated a update feature 1.0.x -> 1.1. Easiest way is to
have a workstation of 1.0.x as administrator, start setup -net of 1.1.
Setup is detecting by sversion.ini were the -net installation is and
updates this installation. When the user logges in and starts OOo
1.0.x he starts a setup that will update his workstation to 1.1.
- in the case that you replace e.g 1.0.2 with 1.0.3: To do it save you
should remove all workstations first, and then replace the -net
installation. Please ask the communuity about their experiences. Maybe
they could help you further.
- for OOo 2.0 we are going to change the installation behaviour of OOo
Comment 5 Olaf Felka 2003-07-23 12:39:31 UTC 
.