I've got a pair of PVS farms that are pointing to ...
# citrix-provisioning
j
I've got a pair of PVS farms that are pointing to the same license server that is being used for CVAD, but there aren't any PVS licenses showing in the Licensing Manager......am I losing the plot or does PVS consume CVA licenses rather than specific PVS ones?
j
I haven't touched PVS licensing in ages but I noticed this in passing on a client site a few weeks back...
image.png
The use Citrix Cloud for DaaS/WEM but have a stand along PVS lic/SKU, cheers
j
Yeah that's what I was expecting, but I only see this
Hence why I'm asking if I've missed some change.....PVS seems to be working fine regardless
j
Quite possibly. Do you have access to their Citrix portal/account to see what's in there?
j
Sadly not
j
It could be that the Premium SKU includes PVS. I struggle to keep track of all the licensing changes Gaaaaa
c
Advanced / premium included a entitlement for PVS
👍 1
j
Think you might be on the money there......
🙃 1
That would explain it, thanks!
Clear as mud on the Citrix licensing page 🙂
c
if you right click a target device / properties and look at the status tab u will see the licensing status
👍 1
j
Yep the premium and advanced should cover it. Also target devices would be throwing warnings if there was an issue.
👍 1
s
Depends on the PVS version -- as of the latest LTSR CUs and CRs, PVS started consuming PVS licenses BUT we also changed the backend so that those of you with PVS entitlements would get license files that have both CVA AND PVS licenses -- you "just" need to return and reallocate your licenses to get the updated license files.
Until 2402, the lack of a PVS license would not cause any problems on the targets but as of 2402 (and 2203-CU5) we are now requiring a PVS license (this was all documented in release notes starting with the 2302 release).
j
On a related note.....do PVS licenses when assigned via the Premium SKU count towards the total license utilization on the license server?
s
Well, as of 2402-CU1, 2311 onwards, we have backed out the checking out of PVS licenses per target and reverted to the old behaviour of using the presence of a suitable CVAD license to consider PVS targets licensed (with no checkout). More on this later...