Sage 100

I realize this is not a recommended or supported configuration and that Sage 100 servers should have as many ports as needed open for registration and if all else fails login as the domain admin and remove all firewalls ( Note: This is highly not recommended and I'm being sarcastic to the type of support response I would expect from the publisher).

Does anyone have a different/updated list of the sites and ports that are needed to renew the Sage 100 license? I have a high-security medical practice that cannot open random ports for a once yearly renewal.

I did find this in the KB however there's really no indication of how to test that the remote access.

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924150078858&page=1&position=0&q=license%20server

Also is there any type of error trapping / error messages or any way to know that the access to the Sage licensing server was blocked and/or what site was blocked?

In this case the customer IT had a proxy server which they disabled on the server, opened firewall to AMAZONAWS and then re-ran the activation. This worked.

We used this Sage KB which wasn't hugely helpful but gave some guidance: 

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924150078858&page=1&position=0&q=license%20server

This is all good information you share @Wayne Schulz.  We have had two clients with an issue like this already this month.  Both are on OLD versions, and in their cases, it was their IT doing "start of new year cleanup" and disabling TLS1.0/1.1.  In both cases the "enabled it again" and the annual registry completed.  Thanks for sharing.  

• TLS 1.2 is required to connect with Sage License Server. Verify Sage 100 version is not retired as retired versions used older TLS 1.0 & 1.1 which cannot connect to the Sage 100 License Server.