My company is in the process of migrating to the Kinetic cloud. However, we have some classic customizations in our on-prem installation that we need to keep so our users don’t freak out about the new UI. Our users are not tech savvy.
One example is Order Tracker. Our cloud pilot environment has all the customizations that our on-prem install has. This means that when I try to launch Order Tracker in the cloud, it fails to open.
My understanding is that Epicor Edge Agent allows our cloud instance to communicate with our on-prem application server.
I have installed and setup Edge Agent. I can print from cloud to a physical printer in the office.
However, when I try launch Order Tracker from the cloud (with customizations) it is not launching the Epicor classic Order Tracker.
Error Message for Order Tracker. What does “classic windows user interface” refer to?
That is the client that gets installed on every user’s computer, just like before - whether you’re coming from Kinetic on-prem or E10 or earlier.
Is that something you plan on installing? without it, you will not have access to your classic customizations.
The Edge Agent needs to be configured to find it - I’m very shady on how to configure it properly … we are browser-only, so only a few of us even have the client on our machines for functions and DMT, etc
But essentially, as part of the process of installing Edge Agent, I had to point it to the EXE file for the Kinetic client - and you’d need a separate config file for opening the client connected to your cloud environment, since it has a distinct server address.
I believe in the SaaS cloud, you can still get the Smart Client downloaded and installed. All you need to know is your Epicor Site ID (Epicor Account number, not the site inside of Epicor).
Google Search Epicor Download, and where you download it from will come up.
If you want to access it from the browser, then you need Edge Agent configured and installed.
However, the smart client is going away altogether in 2026.1 - so you need to migrate any customizations to the Kinetic UX before you upgrade to that version; regardless as to what your users do or don’t like.
Even though we’re on-prem, I’ve already eliminated all smart client access at our company, despite the groaning and moaning, simply because it’s going to happen regardless, and I wanted them all to finally transition and be done with it once and for all, and not have to maintain two different types of customizations any longer.
What trips me up is that I have Edge Agent installed. Epicor Cloud can print documents to our local printer from the cloud. The Cloud instance can see Edge Agent and can print.
I will take a look at the Edge Agent Configuration applet in our instance and try from that angle.
What version of Kinetic are you going to in the cloud? In the 2024.2 version of Kinetic, the corelating version of Edge Agent requires you to configure a path to the smart client so that it knows where to pull the .dll from.
It’s separate from the app server urls that it uses for print communication.
Image from the 2024.2 upgrade guide:
I took the screenshot from my Kinetic 2024.2 upgrade guide that I used earlier in the year when we upgraded. You can get the corelating upgrade guide for your version of Kinetic from EpicWeb; as I know there were additional upgrades to Edge Agent for the 2025 versions (like Edge Agent being updatable, as opposed to having to be uninstalled and a new version installed with each Kinetic Upgrade).
This is not a thing… They are two completely separate environments. The Edge Agent can launch the SaaS environment classic client if installed on the desktop but it will never touch your on-prem environment…
But as others have said, if you are currently migrating to SaaS Cloud, you should not even be touching classic at this point, you have no time to waste, you must convert all your customizations to the browser by May 2026. If you’re not going to make that timeline you should really be staying on prem until you’re 100% browser.
