<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - GPO upgrade error"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=143460#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - GPO upgrade error"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=143460">bug 143460</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>So are you trying to upgrade an older LibreOffice installation *also deployed
using GPO*? If so, you need to describe *in detail*, how you upgrade:
* What GPO feature are you using for deployment: e.g., that could be a startup
script, or software installation policy;
* Are you re-using the same GPO, or are you creating a new GPO for the new MSI;
* What did you do with tour older deployment: remove with uninstall? simply
remove?
* If you delete old policy, does it have a "delete from user systems when out
of scope" (or a similar) property?
* Which is the new LO version, which was the older version, and was there an
even older version also deployed using GPO?
Basically, the problem is most likely that you do not remove the older
deployment policy from user systems - and the *GPO* restores the registry key
after LO installer has removed it. I suspect that actual sequence is this:
1. You install LO version e.g. 5.0 using GPO.
2. You deactivate 5.0 without uninstalling from user systems, and deploy 6.0;
this works fine, with LO installer detecting LO 5.0, uninstalling it, and
installing 6.0.
3. At some point, user systems get rebooted, and get old policy re-activated
from cache, getting additional registry key from older GPO for LO 5.0
re-applied.
4. You deactivate deployment for 6.0, and deploy 7.0 - and that fails, because
user systems now have registry settings as if there are *two* simultaneously
installed LO versions: 5.0 and 6.0, which confuses installer for 7.0.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>