Hi Christopher,
You do not need to run setup assistant, that will automatically kick off during the CIC installer/upgrade. This is where TLS1.0/1.1 is required to be enabled on database and CIC servers, which you can disable after the upgrade, but the upgrade of the CIC will fail if you don't enabled TLS1.0/1.1.
Each server will have 2 installers that need to be ran, a Release installer and a patch installer. On the CIC these installers can take hours to run, so you are looking at 2 to 4 hours to just upgrade the CIC server. I also make sure i have a SNAP of all our Virtual servers incase i need to back out of the upgrade.
At a high level this is the process I follow, you may not have some of these servers in your environment.
- Media Server
- Video Server
- Fail over to backup CIC server
- Upgrade primary CIC server
- Upgrade 2 Session Managers
- Upgrade 1 CCS server
- Failover to primary CIC server
- Test system
- Upgrade remaining Session Managers
- Upgrade remaining CCS server
- Failover and test again.
- Fail back over to Primary CIC server ( Upgrade completed)
let me know if you need anything else.
Thank you
------------------------------
Scott Williams
Missouri Higher Education Loan Authority
------------------------------
Original Message:
Sent: 09-29-2020 08:39
From: Christopher Becker
Subject: Upgrade 2016 env from 2018 R2 to Latest version (2020 r3)
Scott - if you do not mind providing additional insight, I know i have to upgrade my media server first, because if I upgrade the CIC first, it will cause an issue (or so I have been told by a co-worker.) I want to know when you did your upgrade, did you upgrade the media server, reconnect, and verify then upgrade the CIC or did you upgrade the Media, then the CIC, run setup assistant and verify?
I am starting to write our my plan and want to try and account for all the steps.
I appreciate any feedback as i am still quite new to this and hope to become an active contributing member of the community
------------------------------
Christopher Becker
State of Michigan - Oakland County - WRC
Original Message:
Sent: 09-23-2020 15:27
From: Scott Williams
Subject: Upgrade 2016 env from 2018 R2 to Latest version (2020 r3)
I am not sure why they are pointing you to Migrator unless they are thinking you are turning up new servers with 2020 R3, then migrate the configuration off the 2018R2 servers to 2020 R3 servers.
If the Servers are not changing, you do not need to run migrator. You will just run the installer on the servers your 2018 R2 is on to upgrade.
------------------------------
Scott Williams
Missouri Higher Education Loan Authority
Original Message:
Sent: 09-23-2020 13:56
From: Christopher Becker
Subject: Upgrade 2016 env from 2018 R2 to Latest version (2020 r3)
Thanks for the response - I opened a case as well, and while I was told earlier I could do the steps as above, I was just referred to the Migrator documentation. I was thinking I would not need to go through the entire migrator process as well. To me, using the migrator is about the same as a fresh install. So i have feedback from one tech, no mention of migrator, and now I am to use the migrator. Am i to assume they just expect me to use the migrator and will this be needed come R2021?
------------------------------
Christopher Becker
State of Michigan - Oakland County - WRC
Original Message:
Sent: 09-23-2020 10:33
From: Scott Williams
Subject: Upgrade 2016 env from 2018 R2 to Latest version (2020 r3)
Hi Christopher,
I just recently upgraded to 2020 R2, and while i was already on a 2019 Release I don't recall seeing any documentation or notice about needing to be on 2019 Rx prior to upgrading to 2020.
The only issue i ran into when upgrading was Setup Assistant error out when trying to update the Database Schema, i found out that TLS1.0/1.1 is required for that process to run. So if have your system running on TLS1.2 you will want to make sure you enable TLS1.0/1.1 on both the database and CIC server before the upgrade.
Thank you
------------------------------
Scott Williams
Missouri Higher Education Loan Authority
Original Message:
Sent: 09-23-2020 09:29
From: Christopher Becker
Subject: Upgrade 2016 env from 2018 R2 to Latest version (2020 r3)
We just finished a massive migration project to move our on prem implementation of CIC 2018 r2 to new hardware/database. All hardware is now Win 2016, with SQL Server 2016 as back end database. We are a unique set up where we really only use Interactive Attendant and custom web services to take payments over the phone (no voice, only keypad prompts.)
I am looking at migrating the existing system from the current CiC 2018 r2 to a fairly recent version. I would like the most current, but I am fact finding now to see if there is any reason i would not go to 2020 r3.
From what i have assessed, this should be as 'simple' as downloading the new version, running the install, running setup assistant and validating. I expect to be able to do this on my QA environment in a days time.
Hoping to have this ready to soon, just seeking any info or somethings i am not considering or if anyone has had issues. I am assuming the large jump (2018 to 2020) is not a problem and i should not have to upgrade to 2019, then 2020, as i have had to do with other 3rd party software in the pass.
Any and all info is greatly appreciated. I hope after this venture to become a more active community member as well.
#ArchitectureandDesign #imlementation
------------------------------
Christopher Becker
State of Michigan - Oakland County - IT
------------------------------