Nope 
Has to be within the same version for the auto update to work.
Kelly
2 Likes
Yea that’s what I thought to. Thank you for all the replies. Looks like either create a script to do a deployment or use a software package installer tool.
Join the list of people who would like a “Local Deployment” option where some computer looks for changes at Epicor, downloads it, and then the local stations upgrade from there.
Mark W.
Brandon - This might help: 10.2 Client Deployment Options - #3 by myutzy - ERP 10 - Epicor User Help Forum
1 Like
Dear group: We are also starting the process of upgrading 10.0 to 10.2. Do you recommend upgrading to 10.1 first, or directly from 10.0 to 10.2? Also, do you recommend installing 10.2 on the production 10.0 server and running the upgrade or installing 10.2 on a new server?
Thank you in advance.
You can go from 10.0 right to 10.2.
If you have a ‘TEST’ server I would do the upgrade there first. You will need to do some work to any customizations and BPMs when moving from 10.0 to 10.2. Plus it is always best practice to do any upgrades on a TEST server first before your Production box.
Hi Team
We are looking at going from 10.1.400 to 10.2.300. We have 4 test dbs on one TEST application server and were wanting upgrade 1 or 2 of them to 10.2 for testing. Can we do this and have the 10.1.400 DBs still functional on the 10.2 application server. The manual say you can upgrade a db individually but doesn’t say what happens when you upgrade the Application server. Or should we just VM a copy of our Test server and upgrade them all?
Darren,
You can have different versions running on the same server, no problem. One important thing to remember is that you will need both versions of the task agent service running on the server at the same time in order to run the task agents for both versions. You will need to run the client installer on your client machines for the new environment version, the auto update function will not work with that upgrade.
Great, thanks Joshua
Much help!