This message was deleted.
# _general
s
This message was deleted.
r
Hmm, I only run across things that license by user or by machine. Example is like SecureCRT licenses per users, which is stored in the user profile.
r
yeah i've only seen user/machine type models so I'm a bit perplexed by the concept
r
So for VDI think of it like a one to one mapping. Each user has a VDI machine or a pool of VDI machines. When you get into the user licensing part, typically it can be control by some admin portal the will say this username has the license. For Machine based licensing, It will license the whole machine as a whole no matter who logs in. Published apps are Remote Desktop Session Host in the grand scheme of thing. User licensing, can get tricky at time because its a share resource. But there are so many way to achieve this.
Example like Adobe Cloud, or office 365. We have a tool called Red gate that is per machine but they only purchased 1 licensing for a machine. Being I installed it on my master image, which will spawn to 6 machines, I needed to tell it what machine to activate on. In this case I use Citrix applciation Tags to force the user to this one machine
r
I'm thinking of the case with a user on VDI who has access to lots of published apps, do they consume a session for each app? I don't really get why you would do it per session vs per concurrent user/named user which is what seems the normal
and if you add a Citrix Delivery Controller (CDC) as all sessions on the Delivery Controller also take up a session... do they need a license? I'm confused!
r
The Delivery Controller only acts for the Brokering of apps and desktops. It contacts the licensing server, but doesnt play a huge role in consuming the license. Sounds as if they log into a Citrix VDI machine and then have what is called a double hop setup (Which the VDI has workspace install) then it will open published apps from within the Citrix VDI image?