Hi Team,

I am planning to upgrade PRTG Network Monitor in our organization and would like to have some information on step by step instructions for upgrading to new version.

Current Version: 16.3.24 New Version: 18.3.43 https://www.paessler.com/support/updatesI also have few questions – - How do I make sure I have all pre-requisites set before upgrading to newer version. - I have gone through few KB articles before reaching you ref https://www.paessler.com/support/updates https://www.paessler.com/manuals/prtg/detailed_system_requirements https://helpdesk.paessler.com/en/support/solutions/articles/760000635119193-i-run-prtg-on-vmware-how-can-i-obtain-best-performance https://www.paessler.com/manuals/prtg/auto_update https://www.paessler.com/support/faqs#e3797-10 - I have another question is I have cloned the PRTG server to another VM and would like to test before I do the prod one and have server with same name with (-test) does it work and do I need to change the name and will PRTG will take different name for test.

Thanks, Krishna

Article Comments

Adding on to my above questions - - Can we change the hostname using a test server to upgrade and deploy on production server? - Do we need to change the host name of the test server we cloned from the prod server and does host name change will make any further licensing issues during the auto-update since the prod server PRTG hosted on is different? - Is it okay to run an auto-update on test server using the same hostname and does it work and do we need to take any precautions or recommendations?


Sep, 2018 - Permalink

Hello Krishna,

I think you already read all important information to update here. Please note, that you need active maintenance to update successfully.

If you want to try the update with your configuration an a testing server, please follow these steps:

  1. Copy and install the "C:\Program Files (x86)\PRTG Network Monitor\PRTG Installer Archive\PRTG Installer (Currently Installed Version).exe" on the testing Server (with a trial key)
  2. Pause the PRTG Services on the testing server
  3. Copy the "C:\ProgramData\Paessler\PRTG Network Monitor\PRTG Configuration.dat" file to the same directory on the testing server
  4. Start the Services and check if everything runs fine
  5. Update the server and check again

Please let us know if there are further questions.

Kind regards,
Birk Guttmann, Tech Support Team


Sep, 2018 - Permalink

Thankyou Birk. I have converted the P2V and I have checked the required path and correct as suggested.

I have received thousands of false alerts to my email however I did not see them in prod PRTG monitor and it stopped until I have to disconnected the nic from test VM

Any suggestion of causing such issues before I should be proceeding with upgrades as I believe I should be checking all the pre-requisites before make any changes in the environment.

Thanks again.

Krishna


Sep, 2018 - Permalink

Adding to my prev note - I am looking into the logs following the https://helpdesk.paessler.com/en/support/solutions/articles/7600006351163-how-and-where-does-prtg-store-its-data


Sep, 2018 - Permalink

Hello Krishna,

To shorten your process here a little, I would recommend to run the update on your productive system. There are only few deprecated sensors in this version jump. If something doesn't go smoothly, you are able to downgrade easily.

The process to downgrade is the following:

  1. Run the old PRTG installation (C:\Program Files (x86)\PRTG Network Monitor\PRTG Installer Archive)
  2. Replace/rename the "PRTG Configuration.old" to "PRTG Configuration.dat", so the configuration before the update gets active

    I think this process is much faster and less troublesome then setting up a new server to test the update. Please lt me know if you still want to use a test server here.

Kind regards,
Birk Guttmann, Tech Support Team


Sep, 2018 - Permalink