Well I’m hoping to get the final configuration of the Live database done today and possibly add the Demonstration database. It took 112 minutes to convert E9 to E10 and the only failures we encountered were for external BAQs that looked at SQL views. The schema change from dbo to erp, etc., means that the queries cant find the fields they are looking for so they’ll have to be recreated unless I can find some clever way to convert them.

First off, add an Epicor Server. Right-click the Server Management node, select Add Epicor Server, enter the name of the server I’ve installed the application on and click the Ping Server button. Success, server located.

Next up, add an Epicor Application Server. Another right-click, this time on the Epicor Server I’ve just added and select Add Application Server. In the dialog there are 4 tabs.

On the Application Server Settings I’ve changed the Application Name to ERP10 and the Net TCP Binding Configuration filed to UserNameWindowsChannel. I’ve created a Custom Directory in the ERP10 directory and added that location.

Once the connection is established I need to go back and Regenerate DataModel as I’ve migrated data. This is done with a right-click on the database under Database Server Management. This took 5 minutes to complete.

With my Application Server setup complete I next need to apply my license file. This is an Epicor 10 specific license so you’ll need to ask Epicor for one. License applied and Companies assigned that’s the basic installation complete (I hope) so on to the Post Installation tasks.

Post Installation Tasks…

The first time you log into Epicor 10 you’ll be informed that some mandatory conversions need to be run. In my system they took around 20 minutes to complete. I have issues with some BAQs and related BPMs where they are updatable. I’ll revisit these when my configuration is complete and work through them to get them to work. You can view the issues by double-clicking the conversion that had errors.

Setting up the Task Agent proved pretty straight-forward. My System Task Agent user is “print” so I set that and “manager” to Allow Session Impersonation and used that as the Username and Password when I created my Task Agent.

I then went on to deploy my Assembly Dashboards without any issues and validated my customisations. I’d suggest if you don’t need them and have them then I’d delete all Personalisations as they may fail validation. Its probably a good idea to start with fresh screens as layouts may have changed since your users personalised them in Epicor 9. I used the Personalisation Purge procedure from System Management – Purge/Cleanup Routines.

Well, I’m off for a well-deserved break now, I’ve left the installation at this point as it’s as good a place as any, catch you in a couple of weeks…

Time for the good bit: installing E10. It may be worth noting that I’m updating this blog in real-time now to make sure anything that comes up doesn’t get forgotten.

To say we are doing an upgrade here wouldn’t be 100% correct. The process is more like a clean install with a database migration. We want to be able to run E9 and E10 on the same server as it’s important to us that we can show the performance difference between the two versions when we’ve finished the install. Without provisioning new virtual servers we don’t have the luxury of being able to install E10 on an identical box and we don’t want any factors to be different when we perform the testing.

I should also mention that our servers are buried in a bomb shelter-like datacentre somewhere in the South of England and we don’t have the ability to stick the media in the drive to run the install. Fortunately, the E10 disk is just a disk with an executable on it so I copied the 1.6gb file across the network and double-clicked.

It’s a bit alarming to see that the first thing it does is uninstall the Administration Console and at this point I’m not sure if I’ll have any control over my E9 installation. Does it remember the settings and just add more in for E10? Time will tell.

At Insights this year a guy from Holland said he upgraded in 15 minutes. Considering what its taken to get to where we are then his system must have been perfectly configured to get it done that quickly. The actual install of the software on our “throttled-back” servers took exactly 20 minutes and that only takes me to 10.0.700. There is already a 700.1 patch on general release and I’d heard that 700.2 was due out yesterday. Unfortunately 700.2 hasn’t appeared on EpicWeb yet so I’m going to patch to 700.1 and revisit it later.

I’ve unchecked the “Launch the Epicor Administration Console” box at the end of my install as I’m applying the 700.1 patch before I go any further in configuring the software.

Our bandwidth allowed us to download the 800mb+ file in around 8 minutes then a further 3 or 4 to copy it to the server. The patch install took around 10 minutes to complete and this time I’ve left the “Launch the Epicor Administration Console” checkbox checked. After a minute or two pause the console opens.

A right-click on Database Server Management and Add Epicor Database Server allows me to add the server that my SQL instance for Epicor is installed on. I’ve verified the connection, clicked OK and the servername appears in the tree view pane.

I’ve finally hit my first problem and it’s not an Epicor one. As I’m keeping E9 and E10 running on the same box I don’t have enough space to migrate my E9 db into the E10 one. Time to talk to the IT Guys…

Not bad, 35 minutes and I have an extra 40gb to play with. Who said the wheels of industry turn slowly?

I’m adding my new database as Epicor10 (for the Live database) as the current Epicor 9 naming convention is Epicor905, EpicorPilot905, etc., and we are sticking with that format. After entering the Deployment Server path and clicking OK a WIP box appears stating “Adding a new database takes time. Please be patient.” The Create Database on Server dialog displays. Clicking the Start button kicks off the procedure which took around 17 minutes. Don’t forget that you’ll need to change the Configuration before you click start if you want the database and log files in a non-standard location and I’d advise making the initial database size somewhere near the current Epicor 9 database size. This means the database doesn’t have to grow while you are migrating it which can slow the process considerably. Creating the default 1gb E10 database took 9 minutes, creating a 20gb one took 17 so its worth creating an equivalent sized one up front as it doesn’t add much time.

Migrating the Current Database…

At this point I’d usually be taking a backup of my newly-created empty E10 database so I can restore it if the migration fails. As I’ve set my db size to 20gb I don’t have the capacity to so I’ll skip that part knowing I can drop and recreate my empty database if I want to.

I’ve right-clicked on my new db in the Epicor Administration Console and selected Migrate Epicor Database, then set the source to my E9 db and verified the other settings from the other tabs, than finally hit the Start button. Time to sit back and relax…