Florian Kroiss (Customer) asked a question.
Dear Progress Community, we got an OpenEdge shared network installation on a server. In the past users started the installation from the server. Now we should deploy the "openedge shared network installation" using a software Deployment system.
We'd to deploy the OpenEdge Shared Network Installation without a connection to the OpenEdge server. We tried to copy the installation sources from the server and launched it locally, but after installation all the shortcuts and registrations are pointing to the install directory where it was installed from (which is the software deployment system's cache directory).
Is there a way to modify the "Network Installation Directory", which might solve the issue here?
If this is not the right way to deploy OpenEdge on the clients, what's the recommended way to deploy the app using a software deployment system? We came across the creation of an installation bundle, which could be created on the server and then deployed on the clients. Or we try to get the "Windows Installer package for client networking" which might be the preferred way.
We would really appreciate any help here.
Thank you all so much,
All the best,
Florian
I would advise to move away from the shared network installations.
It adds a layer of dependencies and potential points of failure for no real pratical gain. The times where it saved significant disk space on the client machines are a thing of the distant past, and any potential ease of use/management would also be provided by your Software Deployment tools.
The rest of how you package things would depend on what other depencencies etc. you have, probably starting with the Client Networking .msi installer is a good starting point.