Issue 47899 - Unable to build a deployable .msi package for multiple users on single pc.
Summary: Unable to build a deployable .msi package for multiple users on single pc.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-21 18:50 UTC by joyh
Modified: 2005-04-21 20:48 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description joyh 2005-04-21 18:50:36 UTC
I need to build a "package" to deploy through group policy.  I have OpenOffice 
1.1.4 installed on a server. To install I ran the command 
x:\instdir\setup.exe -net. I assigned read and execute rights and shared the 
folder. To install on a workstation, I chose a workstation installation and 
followed the prompts. 

I use WINinstall LE 2003 to discover and create packages. As the workstation 
installation proceeds I use the discover process to create a snapshot of 
installation changes to my xp machine. I am currently not able to have more 
than 1 user "see" the application on one machine after deploying the 
installation package through group policy. The messages received include "this 
application is in use by pcxxxx" and "unable to see the installation package". 

Are there currently any .msi packages available or do you have any suggestion 
for creating a usable package? I have an environment where multiple users use 
multiple workstations.

Thanks.
Comment 1 Olaf Felka 2005-04-21 20:47:41 UTC
I don't know if there are any of these msi packages but I don't believe so. For 
mor information please ask the related mailinglists (see http://www.openoffice.
org/mail_list.html or use users@openoffice.org).
Comment 2 Olaf Felka 2005-04-21 20:48:34 UTC
Not a bug but a support request.