Currently we are using Epicor 10.2.700 and would like to update to Kinetic 202X at some point in the future. We are able to use Kinetic Home Page coming with Epicor 10.3.700. I want to know how much difference between Epicor 10.2.700 Kinetic Home Page and 202X Kinetic. It would be appreciated if anyone has the experience and let’s know know.
Thanks,
I’ll say the Home Page is not really that different, but rather the User Interface changes.
The biggest one I can mention is that Kinetic eliminates the need of a client install since you can access from any web browser. You get actually pro’s and con’s from this, you get better performance but security needs to be enforced, since users can just log in from any device.
I’m currently doing a Kinetic Migration analysis, maybe down the road I could share it.
Hi Juan,
Thank you so much for your sharing.
The .Net client won’t be phased out until Kinetic version 2024.1 according to slides shown at Insights this year. Not all commands have been converted to the Kinetic UI, even in 2022.1.
We, and other companies, are moving to Kinetic and slowly migrating users over to the new UI as it makes sense. You can run both. Unlike the move from V6 to V8, it’s not an all at once move. Get current, learn the new UI, and take a little time to make a deliberate plan to migrate to the new UI. The framework is still in development and will take time to settle down, but I wouldn’t wait to move to 2022.1. This will give you an opportunity to use Automation Studio and other capabilities that you won’t have in 10.x.
Just my humble opinion…
2 Likes
I just posted asking about this kind of security. Will Epicor be providing guidance as to how to best secure our data? Right now we trust that Epicor is keeping our data secure (as we are dedicated cloud tenancy.) What changes will we have to make once everyone has to use a browser?
Sorry I didn’t explained this properly. This is only in the case of on-premise solutions. Cloud is managed by Epicor and complies with Azure security protocols.
1 Like
Yes, by moving to the cloud, you have picked up some security over on-prem. However, security is a shared responsibility. Epicor does not prevent your users from over sharing, etc.
An EASY security improvement that all Epicor users can do (but especially cloud of any type) is move to Azure AD and enable MFA.
The security battle moves from poor credentials to protecting tokens. But at least you’ve moved the problem to where your users are and not to anyone on the planet!
2 Likes
Is it trivial to turn on MFA? Or is this a new module and purchase agreement?
Depends. Epicor Identity gives you MFA for free I believe. It’s only available to cloud customers.
If you’re using O365 (and have the P1 Azure AD plan), then you can use that as well. MFA will be mandatory in 365, so you may already have it.
1 Like
Forgot the answer this. Trivial to turn on. Not so trivial to train the users. 
I would recommend high-risk targets use the Microsoft Authenticator app using the matching numbers. SMS is the weakest of the MFA. Hardware key is the strongest - but not as convenient. The matching number MFA is stronger against Man in the Middle attacks than the one time codes.
Windows Hello for Business is seriously under-rated in my humble opinion.
We use Duo to secure access to RDP and ADFS. So users can’t log into windows without their key generating token. They already hate this as they have to enter their password, and then verify with Duo MFA either on their phone app or with a hardware token. Would setting up kinetic to use MFA just add another MFA step to piss off my users? I mean, don’t get me wrong, I love making their jobs harder and more time consuming. 