Summary: | LO 7 apps do not start on Windows 2012 R2 Terminal Server multiuser environment | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Alka o.p.s. <admin> |
Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED INSUFFICIENTDATA | ||
Severity: | normal | CC: | buzea.bogdan, xiscofauli |
Priority: | medium | ||
Version: | 7.0.0.3 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 118000 | ||
Attachments: |
Error message shown to users trying to strat LO apps
Newly created users can't even start the app |
Description
Alka o.p.s.
2020-09-05 07:01:02 UTC
Created attachment 165171 [details]
Error message shown to users trying to strat LO apps
Created attachment 165172 [details]
Newly created users can't even start the app
I tested this on Win2012R2 server with RDS. I could run normally installed LO 7.1+ for 2 different users without an issue. RDS is the new name for Terminal Services (which you mention in Steps) but this bug is likely about Terminal Server (used with licenses). To add TS to Standard or Datacenter edition of Windows Server, if someone can do it: 1. Server Manager -- Add roles and features -- Role-based -- Server Roles -- Remote Desktop Services -- select RD Session Host and RD Licensing Role Services -- finish wizard. 2. Open gpedit.msc. Set the licensing mode to match the type of purchased RDS CALs you have, and Specify the FQDN of your RD Licensing server (localhost is fine in your case) Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing\ Use the specified Remote Desktop licensing servers Enabled Set the Remote Desktop licensing mode Enabled 3. Open RD Licensing Manager (licmgr.exe). Activate the server, then Install your purchased RDS CALs To install in TS mode: "Change User /Install". Note: Before reporting the bug, it's always advisable to test with LO master which is now 7.1+, from https://dev-builds.libreoffice.org/daily/master/current.html. But for this issue, I doubt version is important. Yes, I do confirm, I am running 2012 R2 server in TS mode for remote access for dozens of users. They use any other application without a problem (Office 2016, Firefox, Chrome, Adober Reader X, Java apps, IrfanView, FreeCommander). All apps are installed in TS mode (by running the install from the Control panel option "install apps for terminal server") I used and reported the latest version available at the moment when it was reported. My conclusion is that the App is somehow trying to write to a location which is not available for standard users in Terminal server, I woudl expect all changes to used files must be done solely in the user profile folder. But I did not have a chance to check which files are being accessed for writing, perhaps some filemon by sys internals can tell more, but as it is a production environment, I am a bit afraid to play with it and also I am not sure what everything LO is reading/writing to in a standard setup. If you ask me a specific thing to do I will certainly be happy to test and give you feedback. (In reply to Timur from comment #3) > I tested this on Win2012R2 server with RDS. > I could run normally installed LO 7.1+ for 2 different users without an > issue. > RDS is the new name for Terminal Services (which you mention in Steps) but > this bug is likely about Terminal Server (used with licenses). Thank you for reporting the bug. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Unfortunately the target server is no longer available, it was replaced by a whole new setup and there is no more LO installed any more. So I cant reproduce on the same setup I had when I was registering the bug. I am sorry. My conclusion was that the RDP setup is not supported with LO where some shared files when accessed by more than 1 user caused issue. However I cant prove this any more. So nobody has a setup to test this. Let's assume this can work, according to his page which confirmes using LO with TS. https://www.urz.uni-heidelberg.de/en/node/18/desktop-and-workstations/windows-terminal-server https://www.en.it.physik.uni-muenchen.de/dienste/betriebssysteme/windows/software/index.html |