Sage 100

 View Only

  • 1.  Clarification on keys auto updating when client changes Perpetual to Subscription

    Posted 03-18-2019 12:12
    Edited by Madeline Stefanou 03-18-2019 12:45
    ​The RKLe Management Team requested clarification from Linda Cade regarding auto-updating license keys. I believe the "Refresh Button" mentioned means the "Update Button" on the LM --> System Configuration --> Registration Tab.  Let me share what we were told:

    We received the following clarification from Linda Cade.

       

    Starting with the 2018 release, the product keys entered in during installation will not be updated until the user presses the Refresh button in the Registration dialog.  This means the customer can install 2018 with the old product keys and not choose to upgrade to cloud until they're ready.  The fix is also in the latest 2017 PU so if the customer is already on 2017, make sure they're on the latest PU and they won't be automatically updated to the cloud key when they purchase it (assuming they don't press the Refresh button)."

     

    Prior to the 2017 release, we didn't connect to the registration server, (we didn't institute that function until we started monitoring payroll subscriptions if memory serves) so if customers are on even older versions they should be okay as well.

     

    Hopefully that puts your customers in a position where they can move to subscription and not have to be concerned about their keys "breaking" something before they are ready.

     

    RKLe Summary:

    Version 2016 and earlier – no issue, license keys are not auto-installed

    Version 2017 – must have the latest PU installed or this will be an issue

    Version 2018 & 2019 – no issue, can run with perpetual keys, new keys will only be updated if the customer presses the refresh button

     

    RKLe Open Questions:

    Version 2017 – similar to 2018/2019 – is there a refresh button that must be avoid?
    Version 2017 – how can we avoid the license being auto updated for those on v2017 PU4 compatible with Sage 100cloud Manufacturing?
    A:  from LC:      By the end of March, JobOps will be compatible with 2017 PU5, but in the meantime, yes, they should have the new key in hand before they migrate.

    Version 2018/2019 – if the client loads the old perpetual keys, will the system be licensed and unlocked for use without pressing the refresh button?

    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------
    ​


  • 2.  RE: Clarification on keys auto updating when client changes Perpetual to Subscription

    Posted 03-18-2019 12:59
    First, congratulations on getting a response from Sage product management. I think that should qualify for an award at MOTM 9 in 2020.
    Second, while I can't find the article in the Sage KB, I remember that the following versions were receiving auto-update of keys. 
    2015.5+
    2016.2+
    2017.0+


    As near as I can interpret, Linda appears to be saying that you can use the old product keys to install 100c and nothing will happen until you hit the "Update" button at which time the customer will receive their latest keys and the old keys are (presumably) then disabled.

    Problem is: 
    • If you are going form standard to advanced/premium - you will need new keys to "pass go and collect $200"  (ie - the new Sage 100 won't install the proper version
    • Even if you are staying on the same flavor you may need/want to install additional 100c modules included in the bundle which the customer previously didn't own (ie Visual Integrator is one I run into quite a bit).

    This change seems like it works ok if the customer is moving from the same flavor and modules to the same flavor and modules.
    As soon as they need to add a module or change to advance or premium then it seems like they'd need new keys (does that invalidate the old ones?)

    Or am I misreading/misinterpreting something?

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 3.  RE: Clarification on keys auto updating when client changes Perpetual to Subscription

    Posted 03-18-2019 14:01

    I don't think installing with old keys would work, because the problem is, they have one current set of keys and that's it, right?

    So if you were already installed, you're golden, but installing new, you'd have to get past the licensing server.

     

    Rhonda McNamara

    Customer Success Manager

    Sage and QuickBooks support and integration

    Stewart Technologies, Inc.

    785 Elkridge Landing Rd.

    Suite 150

    Linthicum, MD 21090

    410-309-9550 x108

     

    Click here to upload files to me.

     



    ------Original Message------

    First, congratulations on getting a response from Sage product management. I think that should qualify for an award at MOTM 9 in 2020.
    Second, while I can't find the article in the Sage KB, I remember that the following versions were receiving auto-update of keys. 
    2015.5+
    2016.2+
    2017.0+


    As near as I can interpret, Linda appears to be saying that you can use the old product keys to install 100c and nothing will happen until you hit the "Update" button at which time the customer will receive their latest keys and the old keys are (presumably) then disabled.

    Problem is: 
    • If you are going form standard to advanced/premium - you will need new keys to "pass go and collect $200"  (ie - the new Sage 100 won't install the proper version
    • Even if you are staying on the same flavor you may need/want to install additional 100c modules included in the bundle which the customer previously didn't own (ie Visual Integrator is one I run into quite a bit).

    This change seems like it works ok if the customer is moving from the same flavor and modules to the same flavor and modules.
    As soon as they need to add a module or change to advance or premium then it seems like they'd need new keys (does that invalidate the old ones?)

    Or am I misreading/misinterpreting something?

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------


  • 4.  RE: Clarification on keys auto updating when client changes Perpetual to Subscription

    Posted 03-18-2019 14:13
    "...if memory serves..."
    Now there is something that instills confidence of an official, tested, and technically reliable response.
    Seriously, how did they NOT come up with a list of Use Cases (i.e. upgrade from 100 Standard to 100C Premium) and go through the logical considerations pertaining to their licensing controls?!?
    Wait... I know how.  It's Sage.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: Clarification on keys auto updating when client changes Perpetual to Subscription

    Posted 03-18-2019 14:54
    I seem to have gotten lucky and sidestepped this issue. I tentatively chalked it up to my upgrades not having their older perpetual versions capable of phoning home to verify keys. Most of my platform swaps have been from perpetual to 100c.

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------

    Original Message


Related Content