Issue 14886 - Office fails on Citrix with non-default program directory
Summary: Office fails on Citrix with non-default program directory
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Windows 2000
: P4 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: joerg.skottke
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-26 08:58 UTC by joerg.skottke
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2003-05-26 08:58:08 UTC
The office can not be executed when the default installation directory for a
workstation installation is redirected to a non-default location.

More precisely:
The office has been installed to a Citrix Metaframe XP server with the /net-option.

During a Citrix session the user executes soffice.exe and thereby triggers the
Workstation-installation. During setup, the installation destination is changed
from C:\Program Files\StarOffice6.1 to H:\$homedir\Windows\Application
Data\StarOffice6.1. The installation completes successfully.

On the next start of the Citrix connection to soffice.exe the office should
start. Instead the errormessage is displayed, that the installation cannot be
found in C:\Program Files\StarOffice6.1 and the user is asked if he wants to
repair the office.

We need a better handling of the sversion.ini - it should be impossible to
redirect this file from Application Data.

Note: There exists another issue with the same content. I just was unable to
locate it. As soon as i find it, i will try to handle it in a useful manner ;)
Comment 1 joerg.skottke 2003-05-27 10:29:28 UTC
set target
Comment 2 hennes.rohling 2003-06-19 11:10:22 UTC
I know that there was an identical task already fixed by DV. Please
verify an close this one.
Comment 3 hennes.rohling 2003-06-19 11:11:55 UTC
Sh***, why can I reassign the issue after setting it to reolsved
invalid ???
Comment 4 hennes.rohling 2003-06-19 11:12:34 UTC
Again, verify and close.
Comment 5 joerg.skottke 2003-06-26 10:46:35 UTC
closing.
Comment 6 joerg.skottke 2003-07-24 11:23:37 UTC
.