Mis-identified VMWare vCloud Suite - 6 and 5

Discussion created by intellectualt on Jul 19, 2017
Latest reply on Oct 5, 2017 by julia.collingburn2

We've discovered that Snow appears to be misidentifying some of our installs of VMware vCloud Suite 6 as vCloud Suite 5.

A few months ago all of our Suite 5 installations were upgraded to vCloud 6 and, naturally, we are confused as to why Snow is still see version 5.

Wondered if this similar users have encountered this problem on version 7 of Snow?

How have you overcome this?

Currently makes our non-compliance percentage higher than it should be.

Outcomes

Mark.Walther Jul 19, 2017 11:50 AM
Might be fixed in SLM 8, that's what we are running and see correct vCloud 6 installations.

Any chance you can upgrade?
Like • Show 0 Likes0
Actions
julia.collingburn2 Oct 5, 2017 6:11 AM
This isn't an SLM7/SLM8 issue, correct recognition of an application or suite is down to the associated rules and in the case of suites, whether all the mandatory trigger applications are installed.
The trigger applications for both VMware vCloud Suite 5 and VMware vCloud Suite 7 are the same, the differentiator between the 2 versions in this case is the registry setting:
Like • Show 0 Likes0
Actions