Upgrade to 11.2

I was reading the guide for out test upgrade to Kinetic, and the workstation requirements say it should be Windows 11. In short, is this required as we are still on Windows 10 with no plan on going to Win 11.

We’re testing (AKA 2022.2.8) now on Win10 computers and have no issues. That said, doesn’t mean we just haven’t ran into something yet. Odd as Win10 is still under active support from Microsoft so weird that Epicor would require Win11.

1 Like

Generally speaking the specs listed in the notes are the ‘supported’ configuration. Any deviation from that means that Support may consider you ‘unsupported’ for a given issue. That’s all the legal stuff of course.

In practice you will probably be fine, and as long as you have one Win 11 station to work on with the Support group in testing stuff, just in case, I’d say you can get by.

They (Epicor) should officially support Windows 10 while it’s supported. Especially since most will be upgrading to get rid of the fat client, but the Web interface isn’t quite there yet.


We are currently running 11.2 and our entire enterprise is running Windows 10. It’s no problem. I’m not sure why the guide calls out Windows 11 specifically. From my experience, running Windows 11 in the Enterprise is not common yet.

Windows 10 Enterprise’s end of standard support is 24 October 2025.

One will no longer be able to purchase Windows 10 directly from Microsoft at the end of this month. While Windows 10 is not going away, Microsoft is moving on. The cadence of technology marches on… We will be on Windows 11 this year with about 15% already upgraded.


Can we have 10.2.700 and 11.2.200 installed on the same app server? we are getting an issue with the admin console.
we have Dev instance trying to upgrade to 11.2.200 and our pilot instance we want to keep at 10.2.700 for now.


You should be able to have multiple but never did a jump that large on a single server. The Admin Console will need to be the newer of the two.

we have the updated Admin consol. downloaded the extensions for 10.2.700 and when we try to connect pilot we get a certificate error…

This is what i am getting when trying to register the existing server.

Looks like the SSL cert isn’t installed or maybe expired. It’s been a long time since I setup a server as we’re cloud now and before that it was taken over by our infrastructure team.

yeah it was an SSL issue. we put in an Epicare ticket and they helped sort it out.

1 Like