Actually the 5.0.38 ones are not outdated if you are still converting files from older versions before 2014, but I assume you are not.

I've never needed to add them all and I have had a few installations that don't work with the default install. In those cases, I confirm the two you mentioned are there and if not, I add them. Then I add one at a time until it works. I start with Sage50Accounting.exe, then add a couple of ports (even accounting offices and bookkeeping firms don't really need the full range to be available), etc.

Whenever I have problems connecting to a file on a server, I move that file to the local workstation machine or test with the sample file to make sure locally the program is operating. If it is not operating locally, then the problem is usually on the workstation. If works on the workstation, then I go to the server and start working at that end.

Based on some quick discussions with a couple of IT people, they have told me that some of their colleagues, when setting up systems, will lock it down quite a lot to prevent virus and malware problems, etc. Whether this is correct cause of these problems or not, the fact remains that Sage has provided some help that will allow people to get through if they have to.

I wonder if like the 5.0.38 ones, that most of them are carryovers, and that Sage has just kept them all in the article over time instead of breaking down specific requirements by version (more back then, less now)?

And perhaps what you saw with needing to add some extra things beyond what the installer did was due to a deficiency in that year's installer? Or perhaps the need arises with very specific functions in Sage which aren't commonly used?

Maybe Sage can clear some of this up.