So I just had support tell me that you can not run 2 different versions on the same app server. This is not what I was told before going to E10 and other agree with me.
So for all your Epicor Expert Guru’s…
Can I run 10.2.300.5 on my E10 Training and then run 10.2.300.8 on my E10 Test Environment?
We’ve got two sets of app servers for two different groups of companies which we’re looking at upgrading to 10.2.
The first app server has three environments on 10.0 and one we’ve upgraded to 10.2 and the second has two on 10.1 and one on 10.2 so it certainly is possible.
Disclaimer - I’m not a guru.
However, I have been advising anyone who asks to try to avoid running different versions on the same server because we had gremlins while doing so. Many knowledgeable people say it shouldn’t be a problem, and I’m sure they’re right, especially in a technical sense. If you know what you’re doing then as far as I know there’s no reason why different versions shouldn’t co-exist quite happily.
But for those of us who simply need to keep a company running, there is a risk that something you do that ISN’T quite right may affect things, and Support may well be of limited help once they hear you have two versions running on the same server.
We have now moved all our non-Live environments to a different server environment and have been very glad we did. After all, you do need to play with a new version before throwing it at everybody, and doing it somewhere safe is a weight off everybody’s minds.
I run about 13 versions on a single App Server… E9, 10.1.400.x, 10.1.500.x, 10.2.100.x, 10.2.300.2, 10.2.300.7 – no problems besides sometimes the Admin Consols dont play nice between major versions. I also run several versions of Task Agent, SSRS… all on a single PC.
Answer: FALSE
You can run multiple versions just fine. Just make sure everything is separated properly
@josecgomez how would you separate the client deployments for the different versions? Say I want a client deployment path for Live that’s at one version but want a separate client deployment for Test that may be at a later version then live. Thank you sir!
I assume you do this when configuring the Appserver and maybe just add ‘Live’ to the end of the Deployment Directory field?
We have seperate clients per Environment, so when you install Epicor on 1 PC and you need DEV, TRN, TST - you will get 3 Clients, each one having a Epicor.sysconfig file; this allows us to be flexible during upgrades (not sharing the same client files) and again, isolation/replication/consistency.
You can run multiple versions no problem. Really just the client deployment is more management than server side. I made it so we have 1 whole client directory per environment with one sys config file per environment. Yeah, more space used by all the client directories, but more segregation and less headaches with client dll versions. If anyone is interested in powershell client deployment scrips and version checks let me know 
happy to share!
can you create separate deployments for the clients though? To isolate the different versions for each Environment/Appserver? I’m talking about having 2 Epicor environments/appservers with different versions on one server. So say I want to upgrade my Test environment to 10.2.200.23 and do testing but leave my Live at the 10.2.200.0 level. So when i upgrade my Test appserver, it will then only update the test clients because it has a separate deployment. Maybe I’m thinking of this wrong, I’ve never tried running two different version appservers on the same server itself.
Ex. of two separate deployments
Live Environment Client Deployment - \\ERP10.2.200.0Deployment\Live
Test Environment Client Deployment - \\ERP10.2.200.0Deployment\Test
This is exactly how Epicor SaaS works. The Live, Pilot, and Education clients are in three separate folders under the Epicor folder. We’ll be upgrading to .300 next weekend so our Pilot is at .300 and our Live is at .200 as we speak.
We run 4 different versions on the same server with multiple task agents.
We had to because CSF demanded a version change.
I wrote a batch file to install the clients to keep things separate.
Regards,
Chris Wineinger
I assume “App Server” here refers to the box (or VM instance) and not the Application Serving program on that box.
So it is possible to install 10.2.300.x on a box that is currently serving up 10.1.400.x?
I just install 10.2.300 like 10.1.400 isn’t there? And can they share the same SQL box? What about the SSRS? Wouldnt the SSRS DB’s conflict?
You can at least upgrade only one of your systems, say Test or Pilot to 10.2 while keeping the others at 10.1.400, and all running on the same server. We did. And I have no reason to doubt the experts in this thread and elsewhere who say there are no inherent problems in doing so.
Going right back to the question at the beginning, though, anyone doing that had better be confident in their Epicor admin ability. Firstly because if you do make a mistake then you could affect the Live environment in ways you didn’t expect, and secondly because when Epicor Support find you have multiple versions running concurrently they may be less than helpful in sorting out any problems you have. And if there’s one time you want Support on your side it’s when you’re trying to smooth the way to a fresh version.
1 OS, 1 SQL, 1 SSRS, Many Versions, Many Databases.
I just name them
Same for SSRS I put them all in their own sub folders in the config and it creates sep dbs
I also set the Agents Directories to something like:
3 Versions of Task Agents running under Services. The only trouble I have sometime is If I want to Administer an older Version - I just have to install for the time being that older versions Admin Console, because the Snap-In doesn’t always play nice.