Sentinel Migration

The protection system for using our programs has been fundamentally modernized, simplified and improved for use in complex IT infrastructures. As part of this migration, we are replacing all existing «Hardlock» protection keys with new «Sentinel» protection keys. The associated instructions describe the requirements and the procedure.

The new protection system is characterized by the following qualities:

• Performance
• Driverless use¹
• Future-oriented

The Sentinel protection system is significantly more powerful. The connections between the programs and the protection key are extremely stable. Even in complex networks with diverse virtualization, licensing interruptions are an absolute rarity.

The CUBUS programs can be used without installing a driver¹. For the vast majority of users, the installation and maintenance of the programs is massively simplified.

With the migration to Sentinel, we are also taking the first step towards a wide range of licensing options. Although only licensing with physical protection keys is available at the moment, the future-oriented technology, inprinciple, also allows more modern approaches.

Notes concerning the migration

• Once a Sentinel key has been delivered, the old system (type «Hardlock») can continue to be used in parallel for a short period of time (approx. 1 month) while the new system (type «Sentinel») is being set up. If you are using a local protection plug or already have other Sentinels in use, the migration will take but a few minutes.
• Please note that only programs that receive active support (generation 9 & 8) are supported by the new protection system. If you are still running older program generations that use the hardlock, they will no longer work after the migration. However, you have the option of importing old projects into new program generations. If you do not convert them yourself by the end of the replacement period, we can support you in converting individual projects at a later date.
• This migration is absolutely essential, particularly because Thales, the manufacturer of the old system, no longer maintains the driver and Microsoft stipulates that Windows drivers whose signature is no longer valid must not be installed.

¹ Driver installation may be necessary for use with network licenses.