Appsense licensing model

AppSense AM uses a kernel filter driver that intercepts all file execution requests. The launch can then be allowed or denied based around various configurable rules. This includes a restriction by device name or IP address, allowing a compliant control to be applied for the Microsoft per-device licensing rules.

Take, for example, a company with Microsoft Visio installed on a XenApp 6. This application is only used by 70 users but as the servers with the app installed can be accessed from any thin client machine, the company must purchase licenses for Visio — more than will actually be using the application, making a mockery of the cost-savings associated with their XenApp and thin client infrastructure.

However, AppSense AM controls access to visio. If additional clients require access to Visio, their details can be added to the device rule when more licenses have been purchased. Another additional feature is the capability to run Application Manager in passive mode, allowing details on application usage to be monitored and giving the company an idea of how many licenses they may need to purchase.

Talk to the people behind the technology. Our team are a safe pair of hands for your business. We are certified experts with leading vendors, but more than that, we have a proven record of results. About us. How we help you. The time can be metered to a certain point, after which the license is no longer valid and the application cannot be accessed.

The user can then be prompted to purchase another use-time license, or to switch to another type of license that has no time restraints. Alternatively, the user can be notified ahead of time that the license should be renewed soon. Another term you may have heard about is consumption-based licensing, where the user pays for the actual usage of the software. However, in practice the consumption-based license is just one way to implement the metered licensing model.

An aggregate use time license is used to limit the overall time an application is used for. The main idea of the aggregate use time license model is that it counts the accumulated time taken to accomplish a task and refers to the total hours consumed by one sector or group of workers.

It is also a subset of the metered licensing model, time again being what is metered. Providing an aggregate use time license is very appealing for enterprise customers as it allows them to better control spending on complex projects. With an aggregate use time license the software may still sit redundant while work streams are coordinated, however, the key difference is that software is not consuming budget. With an aggregate use time licence, an organisation can purchase a total number of licensed hours and this time allocation can be consumed by any number of users.

This is why the aggregate use time license type is a literally a money-saver. Learn more about the aggregate use time license here. The feature license model is used to limit the use of a specific feature of an application.

In feature based licensing you, the software vendor, can control which features of your software the end user can and cannot use. The feature license can also be used to limit the number of times a specific feature of an application is used. A feature license model is in effect a subset of the metered license. It is one of the most commonly used variants of the metered license and if your current licensing provider or your in-house built licensing system cannot support feature-based licensing, it is highly recommended to try out a complete licensing solution such as 10Duke Entitlements.

As the name suggests, a fixed duration license is simply a license to a piece of software for a defined period of time. A trial license is like a fixed duration license, but with the main difference that you are allowing access for a user to allow them to test your application with the hope that they will ultimately purchase a license.

Users expect to be able to try out a software application before they buy it. The trial period is normally defined in advance. The trial license also allows you to control what features or aspects of your application can be accessed during the trial period.

Learn more about supporting trial users here. A project-based license is designed to support collaboration between multiple people who work for different companies. In the project-based licensing model, the customer purchases a main license from the licensor and then grants entitlements to access the licensed application on to project team members. These team members can then access the application under the main license, even if they are part of a different company or organisation.

Rather, it is a license provided to a distinct group of people, but as it is very popular we have included in this list. The academic licensing model is typically used by companies providing educational or engineering applications to schools and universities.

It provides access to an application for that specific group of users and the license typically has different commercial terms lower cost, free to use, throttled access to some features, etc.

Academic licenses are much like trial users in that they are either provided for free or a reduced rate in order to encourage usage of an application amount students users or, even better, the usage of an application by academic researchers and teaching staff who both use it themselves and use it as a teaching tool for their students. The basis idea here is that if a student become familiar with a software application while at university, they are more likely to use that same application once they join the professional workforce.

This is particularly the case with more complex applications, such as CAD, CAE, simulation or special effects applications. Learn more about supporting academic users Learn more about supporting academic users. Multiple authorised employees can use the license on several different machines, but Product X will only run on one machine at a time. This license again combines aspects of other licenses to create flexibility for the software publisher.

The agreement includes a minimum and maximum license duration an employee is allowed to take at a time, but total use time for all employees will not exceed days. With the offline use license, a user can check-out a license for a defined period of time and is not required online access.

This license is ideal for use in the mining or construction sectors where a user of an application may be in a remote area where connection to the Internet is not possible. The time for which a license can be checked out is entirely configurable by the vendor — it can be 1 day, days or whatever the vendor prefers. An anchored license is one in which a license is provided to a customer, but it is anchored to a specific device.

The application can only be used on that specific device. Different to an anchored license, with a device license there is no human actor involved. A license is granted for use of the application on a defined number of devices. Learn more about Learn more about device licensing here. A support and maintenance license is typically used as an add-on to the perpetual license. It is normally used to provide software updates and fixes to a licensed software product purchased under a perpetual license.

A specific set of users can access a product based on a defined whitelist. This is ideal for product testing with select users. If you are looking for the best license model to help monetize your software and increase your revenue, there are many options available and a good license management solution should provide you with the model that best suits your application rather than the other way around!

When deciding on a license model, the best way to approach it is by following these three simple steps:. General Information Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. Website: Go to site Description: AppSense Application Manager is an Information Technology IT solution that provides users the ability to define per-user application entitlements, comply with licensing requirements, and enforce corporate security policy based on contextual factors such as location, device name, Internet Protocol IP address, firewall settings, or even time of day.

Users must ensure sensitive data is properly protected in compliance with all VA regulations. Section Information: This technology has not been assessed by the Section Office. The Implementer of this technology has the responsibility to ensure the version deployed is compliant. Section compliance may be reviewed by the Section Office and appropriate remedial action required if necessary.

For additional information or assistance regarding Section , please contact the Section Office at Section va.

These decisions are based upon the best information available as of the most current date. Any major. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry. Use of this technology is strictly controlled and not available for use within the general population. For example, a technology approved with a decision for 7. Anything - 7. However, a 7. Anything , but would not cover any version of 7.