This message was deleted.

if the client wants to use cloud hosted VDA's the only way to achieve that is with Citrix Cloud

If cloud hosted VDA means cloud hosted only by Citrix, then true. However, thats not true if you are open to other companies hosting your VDAs. I can have a vpn or express route to Azure and have my VDAs cloud hosted by Azure and DCs, netscaler, ect on prem or in citrix cloud, or any cloud or colo for that matter

how would you provision VDA in that scenario?

Will that work if you dont have Citrix cloud?

oops, wrong picture hold on.

and be able to provision machines there using Citrix tools?

There is no difference in having a citrix VDA sitting on a 1, physical server on prem, 2 inside of Vmware ESX on prem, 3 an machine that you created or migrated to Azure, AWS, ect. As far as citrix support and license you should be good also. https://support.citrix.com/article/CTX270373/public-cloud-support-with-current-releases-and-long-term-service-releases

I really hope your right, however that is not my understanding. I've asked that question a couple different places, including my Citrix SE and their conclusion is that VDAs, no matter how they are provisioned, are not supported in Azure/AWS/GCP past 1912. I would really like to be proven wrong here as this directly affects a client of mine.

Review at the above article. My read has always been that you just need to make sure they have hybrid rights on there on premise subscription if we are talking about a license issues.

„Hybrid Rights are term-based subscription licenses that are provided in addition to the cloud service subscription when customer transitions or trades up from a perpetual license to a cloud service subscription. Customers leveraging the Citrix Virtual Apps and Desktops 1912 Long Term Service Release (LTSR) for public cloud workloads (VDAs), can now leverage a Hybrid Rights subscription to continue utilizing public clouds with the Citrix Virtual Apps and Desktops 2203 release.“ In most cloud trade up you get Hybrid rights. For OnPrem you have to extend your perpetual licenses with hybrid rights which is way more expensive than doing Cloud TradeUp. For sure as Citrix wants their customers to use Citrix cloud with public workload together…

that's how i understand it. Although i thought for some reason that obtaining hybrid rights without a cloud sub would be a little cheaper than cloud...thats kinda redic. Citrix needs to remove their stance in general on Cloud VDAs needing anything other than a normal license.

You got that right, As above, Citrix wont know shouldnt care where my VDA is. This is just a cash grab.

i'm willing to fight the good fight with you @stormlight

Does anyone know what is a “cloud service subscription” roughly cost per user these days. Im sure there are probally 15 sku

We are switching to cloud specifically because of the cloud VDA support. I am totally with you on the cash grab. I dont think that there are any ways around it if you want to contniue using Citrix's hosting integration for provisioning

yeah, i get it if you are using hosting connections/provisioning. If you have normal licensing, just remove cloud entries from hosting connection options.

The logic for Cloud only for public Cloud workloads is a fair one - their focus on development would have to be on two core streams, cloud is a LOT more agile than on prem CVAD so that has been the focus. They did backtrack with 2203 hybrid use rights, the idea is that is for enterprise or very large sectors that cannot move to Citrix Cloud - so its not a cheap option, and its not really designed for smaller environments. So in summary • Citrix Cloud is required for public cloud workloads regardless of provisioning type AFTER 1912 LTSR • Citrix 2203 on prem allows for integration with Azure again IF you have hybrid rights • Citrix Cloud is more feature advanced than on-prem these days, so if you can go, go :)

if your not doing any cloud integration, it shouldn't matter and doens't req more dev cycles.

the product doesn't differentiate between customers and their workload requirements - they have to cater for every scenario from a dev perspective - so it takes a LOT more cycles to manage two platforms - right or wrong on that decision, that is the logic

but they have to support their on prem product anyway...

that's 2203 Hybrid Logic right there - i would imagine we will see this stance change at some point given changes being made everywhere else, but that is a completely unbacked opinion based comment 🙂

rebellions are built on hope

They support their product on VMware ESX on prem, Xen on prem, I assume HyperV on prem and a myriad of physical machines. Whats the reason to charge more If I were to build a virtual machine VDA in azure and vpn to it from my on prem Citrix DC. I dont see the extra cost for dev then sticking that same VDA on any of the above examples at a colo that I manage of my choice. I have no idea but i assume VMs in azure are running on hyper v so there shouldn’t be more dev cycles

@James Kindon would you be able to recommend any person to contact regarding a possible decision change? Some of this is a little technical and doesn't sit well when explained to people who don't fully understand.

there is a lot more to it than where your workload runs - I agree with you it shouldn't matter if you weren't using provisioning - but I see the efforts that go into cloud provisioning and it is massive /shrugs

Ah, I see the disconnect here. My client doesnt care about provisioning. They build and manage a number of VDAs manully

same for my client, and i built them some aws automation to powerup/down things during off hours to save on some costs.

yep, that is the scenario that I 100% agree should be unlocked

is it locked though? if you have IP connectivity and dont need power management you can using any device as VDA physical or virtual.

no you cannot. if a workload is on Azure, or AWS, or GCP, it will not register to on* CVAD components without 2203 hybrid use rights after 1912

That is crazy. That sounds like all the bullshit devs use to code in apps to prevent you from running the app on terminal server\citrix many years ago. Now Citrix is doing it on their own product.

There is a much bigger set of considerations here

It should all just be freeware.

shareware.net!

Not to be argumentative because i just want to understand. Please give me example if you have one. Im talking no provisioning and just a basic register of a VDA that is sitting on azure back to your on prem Ctrix DC. Is the software that Azure injects into the VDA (like VMware tools) that drastic that it warrants additional dev time to justify the cost?

I would think a non-provisioned VDA would register, you would just get the ole "sorry not supported" if you call in with an issue. I believe the way they are managing it right now is by not exposing the host connections for cloud providers in the on-prem version, but if you tell it "this is a physical machine with no hosting" how could it know otherwise? Perhaps they bake something into the VDA that reports that it's in a cloud?

I thought they were going to start doing checks for the installer too.

@stormlight outside of provisioning i am not 100% sure on the dev impact to be fair.... @langsbr they will be physically rejected - there is an event log that calls out the specifics of why (can't remember it offhand) @Steve Noel yep, checks on install and checks post install incase you lie 🙂

Isn't it the "is this VDA hosted in cloud" option during the VDA install that screws it? Basically, they ask you to dob yourself in?

99% sure it will check regardless - it was erroring out before that install option existed I believe

Ah ok. Never understood why that option existed TBF

I could well be wrong - but I’m 99% sure

I'll take your word for it at 99