We just upgraded from On-prem 2023.2 to 2024.2. Part of the upgrade is deploying Epicor to 150 clients. During the client install, we have to copy a dll into the client folder, which pushes Epicor customer activity to our Ring Central clients.
I thought that creating a custom folder and choosing it in the App Server Configuration would push the dll to the clients during deployment, but it didn’t.
No the custom folder is for server side assemblies. I’d suggest you copy it into the relaseclient.zip folder or go about creating a deployment folder for the assembly and add in the the required information into the Customisation section of the config.sys.
let me elaborate.
On your App Server, in the Epicor Installation folder find the ER11<ERP version instance\ClientDeployment\Custom\Client folder
Create a new folder, in your instances perhaps name it RingCentral, then copy the assembly there.
Then you need to update the config.sys file related to the install. In the
ClientDeployment\Client\Config Folder update the related config.sys file.
In the customisation section put in
<customization name="RingCentralLib.dll" directoryName="RingCentral" version="11.3.200.6-101" deploymentType="xcopy" />
Screenshot example
If the clients don’t have any switches in their shortcut then the difference between the client config.sys in the clientdeployment folder vs the local clients config.sys will be enough to trigger an auto update.
However if you need to force this then you can use /update in the shortcut
C:\Epicor\ERP11\LocalClients\Kinetic2024_2_Demo\Epicor.exe <put /Update here> "/Config=Kinetic2024_2_Demo.sysconfig"
Just remember to remove it afterwards of it will attempt to auto update every time. /Update forces a full update rather than just what needs to be changed it you don’t have it in place.
All of this information is available in the Systems Administration Tech ref of the relative version you are on.
This is for On-Prem only.
I hope this helps and it’s not too convoluted.
Thanks, Hally! That helps clarify things. I’ll give it a try!
Actually just forget toally about the release client.zip hairbrained idea. If you use the deployment method it will work for new client installs as well.