IDC Upgrade - Anyone done this themselves yet?

ECM
1

Has anyone upgraded their IDC instance yet? How did it go?

2

to any version in particular? We got our Dev box up to 9.3.xxx and didn’t see any trouble.

1 Like
3

9.34

4

9.33.8310 is where we’re at. I was going to do the next update this weekend, but I don’t see a 9.4 out there, only 9.33.11210.

5

I have done a few recently and they were not an issue. They and ECM have been getting better at the upgrade process.

6

Do they have the guides out there?

7

Do they have the guides out there?

8

For 9.3xx release - yes the guides are there but oddly they are Word Docs.

1 Like
9

On Epicweb?

10

Found it I believe, thank you.

1 Like
11

yep - was just on there an hour or so ago to make sure I had the latest release & docs

12

So if it’s just an upgrade does the.msi know that? It seems like the install guide assumes you’re installing it for the first time?

1 Like
13

been a few months but I’m pretty sure it’s just like ECM now. Just run the installer and it takes care of everything. I do have some notes about making sure you have the folders/paths recorded somewhere so you can confirm them when running the installation/updates.

1 Like
14

Wow… sounds so easy. I wish EVERYTHING could install just like that.

2 Likes
15

Okay, thank you Mike.

We are on a pretty old version so it’s probably been a while since you’ve had to deal with it.

We are on version 9.11.9290…

Do you recall any huge “gotchyas” from long ago when you first started to upgrade?

1 Like
16

I don’t recall anything particular, but I think one upgrade reset all of our email/file capture agents and I had to recreate the connections - but I think that was more than likely to convert to M365 (from Exchange on-prem).

Good luck! Happy to help if I can!

1 Like
17

Right!! I was very surprised when I realized it. I might have been spoiled with the Windows self-healing install from years back, but I never expected it from a ‘product’ installation. And now ECM does it too - it makes patching very quick and easy.

2 Likes
18

I found my notes!!

You have to do it in the right order:
Server install
Web Client
Automated Clients
Input Services

This is what my cheat sheet looks like:

Server Install
Dest Folder = C:\Program Files (x86)\Epicor IDC (server and other have subfolders)
SQL server = .ashworth.com
database =
image directory = \
License Key = ****************************
install as service = true
encrypt and all others = false
Port# 12345 is default

Web CLient
Dest Folder = C:\Program Files (x86)\Epicor IDC
Port = 80
App server refers to IDC Server service = so localhost is OK
127.0.0.1 / 12345
DB Connection string can be left blank

Automated Clients - take the defaults

Input Services - For File/Folder input

Reset the Windows account the services run under. We use a domain
account of our own, and the install resets it to the Windows account.

Set the HTTPS Bindings and Certificate again.
Reset IIS

2 Likes
19

If you have the install guide it says do them in the order Mike said in a longer way.

I did my dev and production tonight and both took about 30 minutes with no issues. They now read the configs and in some screens do not even let you change it.

One odd thing for me was the IDC Input Service got set to manual start on both machines.

1 Like
20

One thing to be aware of is that the windows services associated with IDC will very likely reset back to Local System, so if you have been using a specific user account for these services, you’ll have to reconfigure those, too.

2 Likes