jlu_tmg100_c
Active participant

Re: Upgrading 2018 R1 to 2019 R2

From memory, I think IIS needs to be on for part of the upgrade.
To block users from accessing the application, consider putting a firewall rule in place blocking all http/https, except for the FNMS instructure servers.

j
adrian_ritz1
Consultant

Re: Upgrading 2018 R1 to 2019 R2

Hi @jlu_tmg100_c ,

To stop users accessing application, you simply stop the IIS, this of course if you don't have any other web application running on the same server. Using firewall rules to block communication is to much hustle. 

0 Kudos
FrankvH
Intrepid explorer

Re: Upgrading 2018 R1 to 2019 R2

Hello,

Yesterday we executed these steps in our productive environement we went from  2018R1 to 2019R2. Only problems we have seen where around:

  • Rights on DB level in principal you need DBO rights
  • And our DB logfile run full. We set the DB to simple mode and enlarged the logfile

The good thing is you can rerun the script if something goes wrong.

Afterwards everything went well it just takes time.

Regards

Frank

jlu_tmg100_c
Active participant

Re: Upgrading 2018 R1 to 2019 R2

@adrian_ritz1, hi. But if the upgrade requires changing or setting something in IIS, then the web server needs to be on, therefore you can't do that.
Firewall rules inside in the Windows Server control panel are fairly easy (certainly don't mean putting in firewall rules on routers).

j
0 Kudos
adrian_ritz1
Consultant

Re: Upgrading 2018 R1 to 2019 R2

Hi @jlu_tmg100_c ,

 

You are right but the change to IIS if take place is done by powershell script, and this is the last task to be run.

1. Update database

2. Update application running setup.exe

3. Running powershell script

The powershell script is smart enough to check if IIS is running, and if it's not running he will start it, also he will start all services that are stopped during migration.

I personally prefer to not mess with OS around as in our environment the OS is managed by other teams. 

0 Kudos