Scott Gardiner

Hi @Phillip Helmling - Thank you for coming back to me. A couple of your fantastic Omnissa team members pulled me into a call the other day and explained to me a bit about what the future will look like and how this problem will be solved! The future looks great, and the fact that they came back to me in person highlights why I love working with Omnissa.

Hi, Not sure if anyone else has come across this and has a solution. We package up some Windows apps, in this case Nessus Tenable agent for Vuln scanning, the version that is uploaded is 10.4.1.20157. The application then autoupdates but we don't see that in WS1, all we see is the version number related to the package that was uploaded. This makes application version reporting impossible, to the point where we need yet another agent installed on the device so that we can gather accurate version number reporting, as you can see below, Lansweeper reports the correct version number. I know that Omnissa have plans to implement Vulnerability remediation tools into Workspace ONE but I don't understand how they can do that if the solution doesn't accurately report back software that is actually installed. Unless i'm doing something wrong?

Thanks for this, we'll upgrade and see if that works. Apologies for the delay in responding, for some reason i'm not getting notifications.

Hiya - Yeah we tried that too, was hoping it would be that simple.

Hi - Yes we tried that one, was one of the first things we came across, but it didn't work for us.

Hi - A buggy version of the intelligent hub seems to have been released at some point. When we enrolled devices with this version they ended up in a state where the Intelligent Hub UI is missing, so when the user opens up the hub on Windows they can't see the all important application catalogue. We worked with support and a version of the hub was released that fixed the issue for new enrollments. The problem now is that we have a bunch of old enrollments out there where there is no UI view. We have no idea how many, we don't really know when the issue started, and even if we did have this information there isn't an easy way to re-enrol as the devices are spread out across the world. If we did know who was affected we'd at least know the scale of what we need to fix. Support don't seem to have any ideas at the moment other than asking us to re-enrol. Has anyone else come across this? And if so what are you doing to fix it? Its making our lives very difficult because we're trying to encourage users to self serve apps from the catalogue and when we send them there they don't have a catalog.