Bug 98337 - Deployment doesn't work with 5.1.0.3 (working with 5.0.x)
Summary: Deployment doesn't work with 5.1.0.3 (working with 5.0.x)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-02 08:36 UTC by mkuhn
Modified: 2017-03-21 12:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mkuhn 2016-03-02 08:36:35 UTC

    
Comment 1 mkuhn 2016-03-02 08:38:40 UTC
Have a simple MSI deployment process, working perfectly with 5.0.x version, but doesn't work with 5.1.0.3:
Software will be installed without a problem, but if I try to open it, the software hangs. Window can be closed, but can't opened all the time (same issue after reboot)
Comment 2 Buovjaga 2016-03-10 10:08:15 UTC
Please tell us the deployment process in detail.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 3 mkuhn 2016-03-11 07:48:36 UTC
Hi Buovjaga,

Deployed with the following command:
\\fileserver\ir$\000024\LibreOffice_5.1.0_Win_x64.msi ADDLOCAL=ALL CREATEDESKTOPLINKE=0 REGISTER_ALL_SMO_TYPES=1 REMOVE=gm_o_Onlineupdate RebootYesNo=No

For deployment itself ManageEngine DesktopCentral is used, but I think its just a remote command like psexec used...
Comment 4 Buovjaga 2016-03-11 08:18:00 UTC
5.1.1 was released yesterday. Does deployment work with it? There were many Windows-problems in 5.1.0.
Comment 5 Timur 2016-09-20 08:47:43 UTC
Please test with the current 5.1.5. 
Please create and attach verbose install log with msiexec option /L*v install.log

You didn't specify how large deployment is, but in mass production Still is advised, not Fresh. It means version x.y.last, so only 5.1.6 should be deployed.
BTW, please be aware of: Bug 94090 and Bug 97982.
Comment 6 Timur 2017-03-21 12:43:04 UTC
It's been 12 months since no response from reporter. 
This is very important for all deployers and maybe the same cause as other mentioned bugs. We had issues with deployment on Windows that use similar method. 
But, without response, we don't know whether this was reproduced with 5.1.6 or 5.2.6 and without cooperation this can't be solved, if possible at all. 
So, I close as Insufficient Data. I still kindly ask you to note here your further experience. 
If this is still a problem, please set back to New.