Sage 100

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I think the answer is because the hotfix is PU1 for 2020? 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 to reach the Sage Licensing Server.

2023.x
2022.x
2021.x
2020.1 ( PU1 )
2019.4 ( PU4 )
2018.10 (PU10)

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I had a 2020.1 POSSIBLY still showing up on Sage's sh*t list but they were also on Win 2012 server.  I was going to track it down, but decided to throw on an upgrade last weekend instead, so can't say definitively.  (They had updated to 2019 server, too.)

I think the answer is because the hotfix is PU1 for 2020? 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 to reach the Sage Licensing Server.

2023.x
2022.x
2021.x
2020.1 ( PU1 )
2019.4 ( PU4 )
2018.10 (PU10)

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Interesting.  What is you install an upgraded compliant version on the server that has the live non-compliant version without actually doing a migration and conversion.  I wonder if the non-compliant version would go to read only.

I had a 2020.1 POSSIBLY still showing up on Sage's sh*t list but they were also on Win 2012 server.  I was going to track it down, but decided to throw on an upgrade last weekend instead, so can't say definitively.  (They had updated to 2019 server, too.)

I think the answer is because the hotfix is PU1 for 2020? 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 to reach the Sage Licensing Server.

2023.x
2022.x
2021.x
2020.1 ( PU1 )
2019.4 ( PU4 )
2018.10 (PU10)

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I've wondered about that - guessing it WOULD shut down.  Would show on Sage's list as pinging both, but the old one would die.  IMO

Interesting.  What is you install an upgraded compliant version on the server that has the live non-compliant version without actually doing a migration and conversion.  I wonder if the non-compliant version would go to read only.

I had a 2020.1 POSSIBLY still showing up on Sage's sh*t list but they were also on Win 2012 server.  I was going to track it down, but decided to throw on an upgrade last weekend instead, so can't say definitively.  (They had updated to 2019 server, too.)

I think the answer is because the hotfix is PU1 for 2020? 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 to reach the Sage Licensing Server.

2023.x
2022.x
2021.x
2020.1 ( PU1 )
2019.4 ( PU4 )
2018.10 (PU10)

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I think the answer is because the hotfix is PU1 for 2020? 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 to reach the Sage Licensing Server.

2023.x
2022.x
2021.x
2020.1 ( PU1 )
2019.4 ( PU4 )
2018.10 (PU10)

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

LM6028T

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Thank you @Kevin Moyes!  This whole TLS thing has been a confusing pile of information/misinformation/hidden fixes/younameit.

Here you go @Cooper Black  (that's the friend BTW) 

LM6028T

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

LM6028T

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

@Kevin Moyes did you apply the patch this weekend as planned?  One thing that you need to make sure of doing is to check the server and make sure that TLS 1.2 is turned on in the Internet Security settings. 

LM6028T

Does anyone know why Sage does not have a TLS hotfix for version 2020?  "asking for a friend" 

Yes, it was very gracious of them to include the fix for the older versions in exchange for the subscription fee they withdraw from the customers bank account every month.  (Sarcasm intended!) .

Sage is Sage.  At least they did develop the fixes for old versions and let 90Minds know.  (Probably to prevent brand damage if a ton of customers had extensive downtime after the TLS lockdown... instead of a nice gesture).

Yes... Great for Sage and not so great for the customer that has been loyally paying maintenance or subscription for the last 20 years.. 

Let's just tell the customer they have to upgrade, no matter the cost or inconvenience, and not tell them that the issue can be resolved with a patch that updates three files and takes five minutes to install.  That's just wonderful.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-18-2023 10:49
From: Kevin Moyes
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Simple: Sage wants everyone on current supported versions.  Releasing a patch for old versions is a precedent they don't want to set.  If something goes wrong with the patch, they still have to be able to say "not supported".

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


Original Message:
Sent: 09-17-2023 11:02
From: Doug Higgs
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I am very curious about Sage's reason for not publicizing the existence of the TLS patch.  Why would a company not want to publicize an essential customer service benefit?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 09-17-2023 10:03
From: Wayne Schulz
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

Added LM6028T to our file storage

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960

It is as clear as mud to me.  Is LM6028T "only" for v2020?  Are there other "hot fixes" for v2018 and v2019 if the client can't go to the suggested PU?  

Added LM6028T to our file storage

I believe this all ties back to the original concept of self-updating Sage 100 registration keys. I have these notes from a few years ago. Although the information says that the self-update keys started with 2016.2 the reason that 2015.5 is listed ( I think ) is that Sage probably updated the key checking logic in PU 5+ for 2015.

To be Safe I've been telling all customers that "Sage says that the next time our version checks for a license key if you are not on TLS 1.2 then your software will go into read-only". I make is clear that this is Sage's assertion and that it applies if their version checks for a license key ( which gets me out of doing a min-review of whether the customer has perpetual or subscription, etc). 

Also note that the following one-off patches are available though Sage is not publicizing their existence and instead is leaving it up to the VAR to decide whether they should be used or not.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2.  There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c, which auto-update keys: 

2015.5+

2016.2+

2017.0+

Note: Versions 5.20.3 (2015.3), 5.20.4 (2015.4), 5.30.1 (2016.1) will have the ability to update the payroll expiration date with the Update button by installing the Hot Fixes based on version KB 83158 ( https://goo.gl/NnlQbY ).

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 09-15-2023 15:07
From: Madeline Stefanou
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

Thank you.  That is the confirmation I was looking for.  

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


Original Message:
Sent: 09-15-2023 14:52
From: Eric Lunceford
Subject: TLS 1.2 related to v2016 and v2017 subscription clients

This page pulled from Wayne's pdf of the August All Hands shows subscription tracking started with 2016.2. 

It indicates Payroll started checking with 2015.5. 

If I understand correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960