Sense check - multiple app server instances at different patch levels - OK?

Strangely I have never actually done this. So before I plough on I thought I would check that there are no issues.
For an App server will multiple instances running on it I am sure it possible to upgrade just one instance to a higher patch level without effecting others. Am I right or not?


1 Like

It’s never caused me any issues doing this. I’ve done it short term to test patches. You just can’t run multiple releases on the same app server. Example: 10.2.400 and 10.2.500.

1 Like

So I am clear, you have one machine, but multiple environments (i.e. LIVE, TEST, PILOT).
If this is the case, yes, you can have multiple patch levels. You have have some difficulty switching between environments as it will re-download the client each time (and the cache will be out of sync possibly), but it should be fine.
I agree about the major versions being different. It just is a pain to manage more than one major version on the same machine.

That’s the most annoying part in my opinion. Re-downloading the client files each time you switch environments.

Do a second install of the client, just for the test environment.

1 Like

In our Epicor folder on our client machines, Epicor has each client in a separate folder (Live, Pilot, Education, etc.) They can all have separate versions and often do during upgrade testing. Calvin is right, no need to download the client each time.

Do you mean locally on the client machine? And point it to a different directory locally.

Yes. I have the client installed twice on my workstation.

The client for our Live environment is in C:\Epicor\ERP10.1Client

The client for UAT (User Acceptance Testing) is in C:\Epicor\ERP10.1Client\UAT

Make sure the shortcut for each has the “Target” and “Start In” set right.

1 Like

Never thought of install it that way. That’s a better way to do it. Thanks for sharing!

I kind of wish I had put them into

That way the two would have been in parallel, instead of the one being in a sub-directory of the other.

1 Like

I think that’s how I would do it as well. Would be easier managing paths that way IMO.

We are running different major versions on the same server.
I created our own installation script using the install folder and custom icons.
This way we can run 10.1.600.35, 10.2.300.11 and 10.2.400.14 all on the same server.

How do you manage shared directories on the App Server, like EpicorData?

Also, Could you share that/those script(s)?

1 Like

NO scripting needed. When a log file creates for MRP, it will create under Companies then the Site folder and the user under that.
Users are users and they each get their own user folder.
The client is appended with the appserver name so we can have multiples under the same Epicor folder.
Same for the Local Clients on the server.
For SSRS, Each company has its own SSRS directory.