General Consultant Discussion

@Wayne Schulz I think it is perfectly fine to share these two links with those customers:

Sage City Community

View Document - Sage Knowledgebase

Late sentence in the first paragraph of the Sage City post reads, "If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode."  The second link I posted is the link in the "Supported Version" link above.

The first link completely backs up your statement of read-only, and I have not seen anything else public-facing that disputes the claim in that Sage City post.

The Sage pronouncement doesn't tie to the "don't tell anyone" document concerning versions ( even unsupported ) that can be TLS 1.2 ready with a PU. I'm not suggesting that we openly discuss one-off patches but merely the availability via PU, which the user should be entitled to.

@Wayne Schulz I think it is perfectly fine to share these two links with those customers:

Sage City Community

View Document - Sage Knowledgebase

Late sentence in the first paragraph of the Sage City post reads, "If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode."  The second link I posted is the link in the "Supported Version" link above.

The first link completely backs up your statement of read-only, and I have not seen anything else public-facing that disputes the claim in that Sage City post.

I think it is perfectly fine to offer these types of customers the hotfix / PU on a case-by-case basis.

------------------------------
Brian Kelly
Accounting Systems, Inc. (ASI)
------------------------------


Original Message:
Sent: 05-23-2023 08:16
From: Wayne Schulz
Subject: TLS 1.2 LIcensing Communications to Customers - What Are You Sending?

The Sage pronouncement doesn't tie to the "don't tell anyone" document concerning versions ( even unsupported ) that can be TLS 1.2 ready with a PU. I'm not suggesting that we openly discuss one-off patches but merely the availability via PU, which the user should be entitled to.

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


Original Message:
Sent: 05-23-2023 08:11
From: Brian Kelly
Subject: TLS 1.2 LIcensing Communications to Customers - What Are You Sending?

@Wayne Schulz I think it is perfectly fine to share these two links with those customers:

Sage City Community

View Document - Sage Knowledgebase

Late sentence in the first paragraph of the Sage City post reads, "If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode."  The second link I posted is the link in the "Supported Version" link above.

The first link completely backs up your statement of read-only, and I have not seen anything else public-facing that disputes the claim in that Sage City post.

------------------------------
Brian Kelly
Accounting Systems, Inc. (ASI)

More specifically, the issue here is:

1. Sage only says in their public-facing announcement that supported versions have access to TLS 1.2
2. However, In the graphic in the "don't share" they show that 2018 PU 7, 2019 PU 5, and 2020 PU3 are ok ( TLS 1.2 compatible ). If a customer were already on this PU they would not have to undergo an upgrade to a supported version just to meet TLS 1.2 compatibility for Sage License Server ( SLS ).

My concern is that I think we have some duty to provide the customer with the full solution and not just an upgrade to the latest release.

Granted, you can privately tell specific customers of the existence of a one-off patch.

However, I'm looking to notify all customers with a broader campaign telling them which versions are ok. And Sage does not appear to have any public-facing document which does that.

I think the message to customers is: 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 for purposes of reaching the Sage Licensing Server
2023.x
2022.x
2021.x
2020.3 ( PU3 )
2019.5 ( PU5 )
2018.7 (PU7)

If you are on any earlier version please contact us prior to August 1, 2023 to have a conversation about your options.

I think it is perfectly fine to offer these types of customers the hotfix / PU on a case-by-case basis.

The Sage pronouncement doesn't tie to the "don't tell anyone" document concerning versions ( even unsupported ) that can be TLS 1.2 ready with a PU. I'm not suggesting that we openly discuss one-off patches but merely the availability via PU, which the user should be entitled to.

@Wayne Schulz I think it is perfectly fine to share these two links with those customers:

Sage City Community

View Document - Sage Knowledgebase

Late sentence in the first paragraph of the Sage City post reads, "If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode."  The second link I posted is the link in the "Supported Version" link above.

The first link completely backs up your statement of read-only, and I have not seen anything else public-facing that disputes the claim in that Sage City post.

 2018 PU 7, 2019 PU 5, and 2020 PU3 are in the Sage 300 table.  But, everything else you wrote is probably fine. 

More specifically, the issue here is:

1. Sage only says in their public-facing announcement that supported versions have access to TLS 1.2
2. However, In the graphic in the "don't share" they show that 2018 PU 7, 2019 PU 5, and 2020 PU3 are ok ( TLS 1.2 compatible ). If a customer were already on this PU they would not have to undergo an upgrade to a supported version just to meet TLS 1.2 compatibility for Sage License Server ( SLS ).

My concern is that I think we have some duty to provide the customer with the full solution and not just an upgrade to the latest release.

Granted, you can privately tell specific customers of the existence of a one-off patch.

However, I'm looking to notify all customers with a broader campaign telling them which versions are ok. And Sage does not appear to have any public-facing document which does that.

I think the message to customers is: 

If you are on the following releases - or higher - then you are compatible with TLS 1.2 for purposes of reaching the Sage Licensing Server
2023.x
2022.x
2021.x
2020.3 ( PU3 )
2019.5 ( PU5 )
2018.7 (PU7)

If you are on any earlier version please contact us prior to August 1, 2023 to have a conversation about your options.

I think it is perfectly fine to offer these types of customers the hotfix / PU on a case-by-case basis.

The Sage pronouncement doesn't tie to the "don't tell anyone" document concerning versions ( even unsupported ) that can be TLS 1.2 ready with a PU. I'm not suggesting that we openly discuss one-off patches but merely the availability via PU, which the user should be entitled to.

@Wayne Schulz I think it is perfectly fine to share these two links with those customers:

Sage City Community

View Document - Sage Knowledgebase

Late sentence in the first paragraph of the Sage City post reads, "If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode."  The second link I posted is the link in the "Supported Version" link above.

The first link completely backs up your statement of read-only, and I have not seen anything else public-facing that disputes the claim in that Sage City post.