Anybody else have Problems with CSP CVAD on Premi...
# citrix-vad
c
Anybody else have Problems with CSP CVAD on Premise Licenses?
We had a Call Last Night with Citrix Support. Workaround —> Downgrade License Server to Build 49000
f
Yes same here.
Upon start it removes certain license files
c
Hopefully they won't have the leap year problem again like last year
j
‼️ Anyone on Citrix License Server 11.17.2.0 build 51000. You will have a problem because license files are automatically removed at midnight (March 1st). This already a known issue at Citrix. ‼️ Workaround when you experience this problem: Revert back to version 11.17.2.0 build 49000 and reinstall license files
orange alert 1
Message edited because it’s not only at restart. Thanks @Christian Jöns, @Fabrice Pfeiffer, @ultrat0s
j
Our org is on 11.17.2.0 build 51000, licenses installed and did not see them deleted. I wonder if the trigger has something to do with when the licenses were "cut"/allocated.
m
Anybody having done a license server rollback and WEM not working afterwards? Just got a call about this, still investigating. Update: only the management part doesn't work, so "meh, we'll wait"
j
"were associated with a discontinued licensing offering" or "There were some cases where partners on the new CSP 2.0 annual license" ...
c
I don't think it was just a few cases
💯 1
c
It only affecting CSP licenses ? I Need to upgrade my license server so debating to go 51000 vs 49000 we got regular DAAS premium licenses so non CSP
j
@Marcus Niemann. Thanks for the link. …The legacy CSP MRR license files contained ‘UB=1’ identifier, while the new licenses contain the ‘MSP2’ attribute…. What Citrix should have mentioned in the article is that the new license file still may contain the ‘UB=1’ identifier and the ‘MSP2’ attribute must be present. Redownload the license file doesn’t change anything and only the ‘UB=1’ identifier is present. But reallocating the license does change the content and shows the ‘MSP2’ attribute. Works on my end.
✅ 1
d
What a mess!!! 🤢 We had a customer last weekend with this issue. Users were no longer able to work.