Apache OpenOffice (AOO) Bugzilla – Issue 92509
moresome Persons loged in with single MS TS account and running OO.
Last modified: 2013-01-29 21:45:51 UTC
Hallo, we wants to use OO. the big problem: We have 600 Persons everyone uses the same windows-terminal-server-account to connect with thinclients to the server and to work here. Most applications are designet to work with only this single Windows account we cant redesign the Usermanagment to give everyone a Account. If one Person is going to open a Officefile this file ist not allways opening in this Persons RDP-Display it opens on someones other RDP-Display. It will be fine if OO Projekt is build in a feature that the OO binary is working in only one RDP-Session independet from used TS account. Sincerely Enver
jsc -> hro: maybe you have an idea if can address this problem. Although it sounds really strange and i have no idea if this would be a legal deployment. But we could come in the same situation if a user has two RDP sessions and opens a document.
This is still an issue in the current open office version. The Terminalserver community would be happy if someone could work on a fix.
I also have this issue. I usually use multiple sessions on my terminalserver. It is impossible to predict on which session openoffice will open (if it opens). I think this is a problem almost every company has when using openoffice with terminalserver or other remotedesktop solutions. I think under windows you have to start openoffice by checking WTSGetActiveConsoleSessionId.
"I think this is a problem almost every company has when using openoffice with terminalserver or other remotedesktop solutions." That is indeed correct. Therefore I would not call Open Office enterprise ready... How can we adress this to the open office project management, that they can put pressure on the development?
Well I do not know how to make the developer aware of the importants of this bug. I just know, that yesterday our company decided not to switch to ooo and instead upgrade to the newest ms office version within the next two months. Everything was fine during evaluation of ooo until we got the problem with our terminal sessions. Even nobody really likes the new ms office (nasty ribbons take much space), we have no choice since we can not avoid using terminal server.
Hi stumbled over this bug by chance. currently I'm not working on OOo and it seems the bug was forgotten because status and component are wrong. This is a known issue, because OOo does not use the TS session id to distinguish between running instances (just the user account name + user data directory). If there's the possibility to run a script for each new created session the behaviour can be workarounded by using OOos -env command line parameter. Changing component, status, version, owner.
Changing platform
Well there are some more things which are wrong in this issue. 1. OS is not only Windows 2003. You can reproduce this issue with any Windows version. (Tested with XP, 2000, and 2003) You just have create multiple sessions for the same user on the machine using remote desktop. 2. In my opinion this is no feature request but a SEVERE bug which prevents companies using ooo. In our case every fix will be already to late, since MS-Office deployment will start in 3 weeks. 3. Since this is a bug that makes using ooo impossible for many companies priority should be at least P2 (in my opinion even P1)!
This is a very nasty bug, especially if OO should be used by a company: Imagine what happens when a senitive document opens in a wrong session? I would stronly suggest to increase the priority to P2 (or better to P1).
The bug does not only affect Windows installations. In our company, we have a Linux terminal server, which is being accessed via Nomachine NX from a handful of clients. When we started using the installation in earnest, we soon found out that OpenOffice documents keep opening on the screen of the user who started the first session, which makes the planned installation completely worthless! The only workaround seems to be to install virtual machines on the server and run each new terminal session in a different virtual machine, which makes everything ridiculously complicated. Am I missing something here, or does this mean that there is no possibility for running OpenOffice on a terminal server installation? I cannot believe that this is true ...