License enforcement still doesn’t work in App-V



So, I have always been recommending that people don’t rely too much – if at all – on accurateness of App-V’s built-in license enforcement features (for which you need App-V’s own full infrastructure to begin with), unless having very constrained environment like terminal servers or fixed workstations.

And I still seem to be right on having this opinion, based on actual customer experience of using said feature:

To be fair, it IS the same thing with pretty much all licensing systems  needing to support concept of concurrent/floated license usage (like App-V’s does): they all fail on non-networked computers simply because there is no telling who has the application running across all machines on moment X. Only way to do this would be some check-in, check-out type of system but there’s not really much concurrency or true demand-based allocation on that, right?

It’s too bad the feature is not represented in correct light in the App-V’s documentation, people seem to get impression that this is foolproof way to enforce licensing..


, , ,

About Kalle Saunamäki

As one of the first four Microsoft App-V MVP's, Kalle has been doing application virtualization since 2003 and virtualization in general from 2000, and is a recognized in-depth technological expert in Microsoft application virtualization community.

View all posts by Kalle Saunamäki


Subscribe to our RSS feed and social profiles to receive updates.

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: