SwissChecklist

Checklist: (obsolete) Update DNN Platform or Evoq Content to latest Version (Software Version Upgrade)

Update DNN Platform or Evoq Content to latest Version (Software Version Upgrade)
  • Notes

    Show Details Show Substeps Show Substeps Show Substeps
  • Preparations

    Show Details Show Substeps Show Substeps Show Substeps
  • It's recommended to test the Upgrade on a Copy of the whole DNN Application

    Show Details Show Substeps Show Substeps Show Substeps
    • Errors may occur that require research.
    • Existing DNN Skins may require updates (css conflicts, modified portal.css, etc.)
    • Maybe Localization Changes
    • Maybe URL Schema changes
    • Extensions/Modules may be updated and require new License or special upgrade process!
  • Coordinate Date & Time for the Upgrade

    Show Details Show Substeps Show Substeps Show Substeps
  • Ensure all Software Requirements for the new Version are accomplish

    Show Details Show Substeps Show Substeps Show Substeps
    see www.dnnsoftware.com/platform/start/install

    new DNN Software may require:
    • New .NET Framework (CLR Runtime)
    • New SQL Server Version
  • If necessary, ensure you or someone else has Administrator Permission to IIS

    Show Details Show Substeps Show Substeps Show Substeps
  • Create Backup of all Files

    Show Details Show Substeps Show Substeps Show Substeps
  • Create Backup of the SQL Database

    Show Details Show Substeps Show Substeps Show Substeps
  • Ensure you or someone else is available to do a Restore of DB & Files (for worst case)

    Show Details Show Substeps Show Substeps Show Substeps
  • Download the correct Upgrade Package (Edition & Version)

    Show Details Show Substeps Show Substeps Show Substeps
    • See /Host/Dashboard.aspx for Details
    • Ensure you download the correct DotNetNuke Product (DNN Platform, Evoq Content or Enterprise edition)!
  • If the Website is Monitored by a Monitoring Software (PRTG, Pingdom, etc.), pause that monitoring

    Show Details Show Substeps Show Substeps Show Substeps
  • Empty Recycle Bin on all Portals

    Show Details Show Substeps Show Substeps Show Substeps
    Because of bugs with Duplicate Tab names
  • Run Upgrade

    Show Details Show Substeps Show Substeps Show Substeps
  • Again, verify you have a current Backup of the Database and all Files

    Show Details Show Substeps Show Substeps Show Substeps
  • Stop the IIS Application

    Show Details Show Substeps Show Substeps Show Substeps
  • In a Web Farm: Stop the IIS Application on all Web Servers & disable all WebServers

    Show Details Show Substeps Show Substeps Show Substeps
    Known Issues:
  • If necessary, change/modify the IIS Application Pool

    Show Details Show Substeps Show Substeps Show Substeps
    • .NET Framework (CLR Runtime): .NET Framework v4.0
    • Managed pipeline mode: Integrated (for DNN 7 and newer)
  • Extract the Upgrade Package to the Web Folder

    Show Details Show Substeps Show Substeps Show Substeps
    Overwrite everything
  • Start the IIS Application again

    Show Details Show Substeps Show Substeps Show Substeps
    In a Web Farm, only start the IIS Application on one Web Server!
  • Open Website in a browser

    Show Details Show Substeps Show Substeps Show Substeps
  • Login as host

    Show Details Show Substeps Show Substeps Show Substeps
    If the Login fails, open the following pages to force the upgrace:
    • /Install/Install.aspx?mode=upgrade
    • /Install/Install.aspx?mode=installresources
  • click "Upgrade"

    Show Details Show Substeps Show Substeps Show Substeps
  • Wait until Upgrade shows 100% completed

    Show Details Show Substeps Show Substeps Show Substeps
  • Ensure Upgrade Log is empty

    Show Details Show Substeps Show Substeps Show Substeps
    • Check it in the Browser
    • Also see Folder ~/Providers/DataProviders/SqlDataProvider/ for Logfiles just created (like 07.01.02.log.resources). All should be empty (2 bytes files)
  • In a Web Farm: start all affected IIS Applications again & enable WebServers again

    Show Details Show Substeps Show Substeps Show Substeps
  • Post Upgrade

    Show Details Show Substeps Show Substeps Show Substeps
  • Ensure Website loads again

    Show Details Show Substeps Show Substeps Show Substeps
  • If the Website is Monitored by a Monitoring Software (PRTG, Pingdom, etc.), resume that monitoring

    Show Details Show Substeps Show Substeps Show Substeps
  • Optional Steps

    Show Details Show Substeps Show Substeps Show Substeps
  • Upgrade Language Packs

    Show Details Show Substeps Show Substeps Show Substeps
  • Upgrade additional Extensions/Modules

    Show Details Show Substeps Show Substeps Show Substeps
  • Do special modifications required by 3rd party Extensions

    Show Details Show Substeps Show Substeps Show Substeps
  • Fix issues in the Skin

    Show Details Show Substeps Show Substeps Show Substeps
  • Update/Fix Localization issues

    Show Details Show Substeps Show Substeps Show Substeps
  • Configure a "404 error page" (DNN 7.1 and newer)

    Show Details Show Substeps Show Substeps Show Substeps
  • Update Hyperlinks because of changed URL Schema

    Show Details Show Substeps Show Substeps Show Substeps
  • If you made changes to DNN Core stuff, ensure they're still there

    Show Details Show Substeps Show Substeps Show Substeps
    Maybe you've modified:
    • HTML Editor (RadEditorProvider)
    • core images
    • favicon
    • jQuery/jQuery UI Version
  • Do Hardening

    Show Details Show Substeps Show Substeps Show Substeps
    • Remove optional Install-Packages
    • Hide/Remove some Modules
    • ...
  • Final Steps

    Show Details Show Substeps Show Substeps Show Substeps
  • Test new DNN Version

    Show Details Show Substeps Show Substeps Show Substeps
  • Inform People

    Show Details Show Substeps Show Substeps Show Substeps
  • New Step

    Show Details Show Substeps Show Substeps Show Substeps
Use this Checklist

Preview/Print

Use

Change

Sort