LDMS 2016.3

Ivanti Landesk Management Suite 2016.3 is probably the most buggy it’s ever been. Ivanti Landesk has taken the crown when it comes to shipping a product so full of bugs that it’s hardly usable.

Here is a list of what I’ve encountered so far. Note that I haven’t dove deep into any of the features yet. I’m just trying to get AV and inventory stabilized.

  1. Kaspersky/Jabber/Win10 issue is back!
  2. Corrupt antivirus definitions on new agent installs.
  3. Security menu doesn’t work, so I can’t fix corrupt av definitions.
  4. Console extender renames items sometimes. Have to restart console.
  5. Console extender no drag n’drop. (bug or missing feature?)
  6. Legacy RC 2016.3 can’t remote control an older agent (2016.0).
  7. No software deployment run on older agents (2016.0).
  8. Can’t provisioning into VMWare Workstation. (I’ve tried editing the .vmx)
  9. LDAV.exe crashes when trying /updatefrominternet. (bummer, that’s the fix for #2)
  10. Uninstalling a partially installed agent fails and b0rks future agent installs. (I had to rebuild a server over this.)
  11. Coworker can’t install console until we install 9.6 console, upgrade to SP2 then upgrade to 2016.
  12. Restarting servers because of “Legacy API shutdown”. (Even though the agent is set to never reboot a server.)
  13. (UPDATE) Previous PXE agent service (2016.0) disappears off the PXE server w/o installing the new agent.
  14. (UPDATE) 2016.3 installer doesn’t detect x64 properly and tries to install Remote Console on Win7 SP1 x86. (These kinds of bugs really annoy me, because this is just sloppy workmanship.)

The first three are the most important. If I could get those fixed, the rest could me annoyances.

UPDATE 2017-03-10: Service Update 3 fixed #2 and #3.


Kaspersky and Jabber

I’ve run into a nasty bug in the latest Kaspersky Antivirus. It seems to kill any Jabber calls. After a couple minutes, Jabber won’t be able to make any calls. It just dead air.

I have commented on a couple forum posts but I haven’t found any definitive fix other than uninstalling Kaspersky.

I’m using KES10 ( with SP1 MR2 on Win8.1 (x64) and Win10 (x64). And I’ve tried several versions of Jabber:

  • 10.6.5
  • 10.6.7
  • 11.5.1
  • 11.5.2

It’s really annoying. At least, Win7 x86 doesn’t seem to be affected by this bug.

Update 2016-03-14: It looks like it’s related to the Kaspersky Network filter driver klwfp.sys. After disabling system protection, renaming that driver, and rebooting, Jabber works after the two minute mark.

Update 2016-04-08: Kaspersky contacted me today. I am currently testing out a new driver for them and it seems to be working. I’ll need to do more testing on Monday, but so far so good. (knock on wood)

Update 2016-04-12: The fix worked and I learned that once you get used to hands-free calling with Jabber it’s very difficult to go back to a regular phone.

Cisco Jabber lag?

I noticed that my Cisco Jabber became very laggy when typing and sending chat messages. A little google-fu found this page from Cisco. Apparently Microsoft’s KB3038314 is the cause of it. I uninstalled the KB and Jabber is back to it’s snappy self. I’m running the latest version of Jabber (10.6.3) and I hope that Cisco can get around this in the next version.

Update: It looks like the lag is fixed in v10.6.4 build 63238.