Update incomplete when ocssystray is loaded into memory.

Bug #957366 reported by karnov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OCS Inventory: OcsPackager
Fix Released
Low
Didier Liroulet

Bug Description

Hello,
if ocssystray is loaded into memory to update the client is not complete.

Example: change 2.01 -> 2.0.4
modules are not available to day:
Framwork 2.1
Sytem 2.0.1
wmi 2.0.1

the command 'pskill ocssystray / a / v' might solve the problem

cordially

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi.

pskill is a command which cannot be included in a redistributable package :-(

So, we cannot use it into agent installer.

However, the problem comes from agent installer starting systray every time launched, even when installer is launched by service when agent upgraded through agent deployment itself. In this case, one instance of systray applet run under SYSTEM account and cannot be killed if setup not launched under SYSTEM account.

So, in 2.0.4.7 agent release, we stopped starting systray applet in installer. See

https://bugs.launchpad.net/ocsinventory-windows-agent/+bug/809417/+attachment/3273227/+files/OCSNG-Windows-Agent-2.0.4.7.zip

Regards

Changed in ocsinventory-windows-packager:
assignee: nobody → Didier Liroulet (dliroulet)
importance: Undecided → Low
status: New → Fix Committed
Changed in ocsinventory-windows-packager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.