The first build of GP Power Tools (Build 20) was released at the start of August 2015 and so we are now into the second year of its release.
This means that the early adopters of GP Power Tools are approaching their subscription expiry dates and some customers are now receiving warning messages about their subscription.
This article explains what the messages are for and how they behave.
The behaviour of the subscription expiry message was changed in Build 20 (Last Modified: 11-Sep-2015). Check the About GP Power Tools window to see if you are on an earlier build (look at both number and date).
If you are on a build before the changes were made, the administrator will get 60 days warning prior to expiry and users get 30 days warning prior to expiry. This original behaviour was based on the idea that the keys would be created with an additional 30 days, but this did not happen so the messages start 30 days earlier than desired. There is also no grace period after expiry.
If you are on a build after the changes were made, the administrator will get 30 days warning prior to expiry. Once expired, both administrators and users will be notified that they are in a 30 day grace period. The warnings can be dismissed for 1, 7 or 14 days. If your users dismiss the warnings for 14 days, they will only see the message twice.
To stop the messages showing:
- Administrators, please don’t ignore the messages for longer than 30 days.
- If your build is before Build 20 (Last Modified: 11-Sep-2015), please upgrade.
- Get your subscription renewed and update the registration key in the system.
If you are still using Build 20, please upgrade to Build 21 as it has many new features and lots of fixes. However, the quickest solution is to get the keys renewed and entered for your current build.
Note: If upgrading from Build 20 to Build 21 or later, GP Power Tools is broken down into modules and so uses 4 registration keys instead of 1.
So you might ask why are the messages there at all?
The reason is simple, GP Power Tools is sold with a subscription license rather than the more traditional Purchase and Annual Enhancement model. Unlike the traditional model, when the subscription expires, the code becomes disabled. It is important that Administrators are made aware of the impending subscription expiry, so they can renew to avoid any disruption of service.
Thanks for your support.
This article was originally posted on http://www.winthropdc.com/blog.