Edge Agent Update

Good morning,

We are finishing up implementing Epicor Kinetic, and the one thing that is not sitting well with me is the tediousness of updating the Edge Agent. I currently have a GPO set up that maps all our Kinetic environments to the Edge agent, URLS, Executables, etc. Today, the new update now wants the sysconfig location, which is fine, but my current script checks to see if “Edge Agent Application Tray” is installed, but can’t see the version. Does anyone have a better way to deploy and update the Edge agent?

1 Like

I only saw this today after @Randy posted the below idea by @aosemwengie1

Automate deployment of the edge agent

There’s some discussion on there between @Olga and @Randy on this… don’t know if it would be of any use to you.

2 Likes

what is your script? Powershell?

Yes.

#Check for Edge Agent
$MyApp = Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*  | Select-Object DisplayName | where { $_.DisplayName -match "Epicor Edge Agent"}

#Evaluate if Edge Agent is installed
if ($MyApp -match "Epicor Edge Agent"){

   
}
else{
 cmd.exe /C ""\\lex\Software\edgeagent-kinetic-windows-x64-installer.exe" --mode unattended --unattendedmodeui none --installMode localInstall --allowedURL [THIRD URL] --allowedURL2 [PILOT URL] --allowedURL3 [LIVE URL] --clientExePath C:\Epicor\GOV\161047-THIRD\Client\Epicor.exe --clientExePath2 C:\Epicor\GOV\161047-PILOT\Client\Epicor.exe --clientExePath3 C:\Epicor\GOV\161047-LIVE\Client\Epicor.exe"
}

I had to set this script to run on the machine level, not user level, because it requires admin. I had tried this with a BAT file, but it didn’t work as well as doing it in Powershell. If I change the install executable does that update if it’s the wrong version? I also noticed today I had to map the path for the sysconfig file in the newest Edge Agent update.

Thanks for this. I am reading on there and I’m confused because 95% of our users are going to use the browser version, but you still need the Edge Agent to attach documents. Really frustrating for us

You can use something like this to get the version

$assembly = [System.Reflection.Assembly]::LoadFile("C:\\Program Files\\Epicor\\EdgeAgent\\edgeapp\\EdgeApp.dll")

# Get the version
$version = $assembly.GetName().Version

# Output the version
Write-Output $version
2 Likes

What type of attachments do you use?
If you are not in the cloud and do not require to use client side file attachments, then server side attachments do not require edge agent. As well as SPO and ECM and others

1 Like

We are a Saas client. We have some custom attachment types that we utilize to determine if we can do business with a Customer or Vendor.

Have you considered ECM? We were in the same boat but also needed AP Automation, etc so we switched form using a file server to ECM. We still need edge agent but on fewer machines now.

well, if those are file attachments there is no way you copy files automatically to some folder just in browser, so edge agent is required for that.

What is ECM? We have the Kinetic Azure FileShare, so we map that drive and that’s what our company has been using to save attachments for Kinetic.

2 Likes

Epicor product stands for Enterprise Content Management. It used to be called DocStar previously.

I’m with you though, I hope Epicor will make an improved deployment/upgrade tool for Edge Agent.

So we are not using that, we are in the Gov Cloud, so I’m not sure if that is a reason we don’t have that. Just trying to deal with what we have. Thanks for your guys’ help

2 Likes

I was able to update my script, I just removed the condition and wrapped the cmd script in powershell, but I get an issue where it says the required port is in use. Is there a way I can break out of a powershell script because the Edge agent updated, but I had to open task manager and close the Kinetic Tray program (which I think is actually the script that never closes out). I just tried doing a .bat file, where I put all my options in a separate text file, but I get errors that it thinks the options are wrong, even though they work when I keep them in line.

1 Like

installer kills the tray app. you can just run the installer

That’s the weird part, the installer kills the tray app, but then who kills the installer? On my test PC, it showed the edge agent had updated, but when I try to run the Edge Agent it says the required port is in use. I went and looked to see what was using it, and it was something in Task Manager called KineticTray. I end this task, and Edge Agent opens fine now. I had seen this before when I was doing the initial deploy of the Edge Agent and the installer script just stayed open until we closed it.

It doesn’t seem the installer every FINISHES, at least as a powershell

at the end of install, tray app is started again

1 Like

try to run it yourself, without script. Just copy all in the command line and run. it should install everything and finish. Tray app is started after that too