MC Upgrade - Part 2 Execute Upgrade
On-Prem Server

1. What this document is for

This document explains how to run the MC Upgrade installer during the maintenance window.

It covers launch, variable gathering, variable review, and deployment execution.

This document is for a full MC upgrade run on an existing on-prem environment. It is not a SaaS migration-only database upgrade pass.

2. When to use this document

Use this document after Part 1 is complete and when you are ready to execute the actual upgrade.

Use it:

  • During the approved maintenance window.
  • After backups and rollback planning are complete.
  • Before handing the environment to validation testers.

3. Step 1 - Launch installer

  1. Sign in to the target server with an administrator account.
  2. Open the prepared installer folder.
  3. Right-click DPInstaller.exe and select Run as Administrator.
  4. Wait for the installer interface to fully load.

4. Step 2 - Run Gather Variables From System

  1. Open the Variables page.
  2. Click Gather Variables From System.
  3. Wait until gather steps complete.
  4. Confirm gather steps show successful completion.

Expected behavior:

  • Existing environment values are auto-populated where detectable.
  • Hidden internal variables are derived from visible values.
  • Installer values should reflect the current server/application state.

If values look wrong after gather:

  • Stop and review before clicking Deploy Now.
  • Do not assume the gathered values are correct just because gather succeeded.

If gather fails:

  • Record the step that failed.
  • Capture error output.
  • Stop and resolve before deploy.

5. Step 3 - Validate all required inputs

Review all visible inputs before deployment.

Always required:

  • serverInstance
  • regDbName
  • enableIntegratedSecurity
  • enableHttps
  • websiteHostName
  • installDirectory
  • loggingPath
  • imageServerPath
  • dataProtectionKeyStorageLocation
  • smtp
  • proxyDisabled

Conditional required values:

  • If enableIntegratedSecurity = false:
    • dbUsername
    • dbPassword
  • If enableIntegratedSecurity = true:
    • integratedSecurityUsername
    • integratedSecurityPassword

Upgrade-specific value:

  • suppressMroCustomFileCopy (normally false unless your run plan says otherwise).

Also review these commonly sensitive values carefully:

  • websiteHostName
  • installDirectory
  • loggingPath
  • imageServerPath
  • dataProtectionKeyStorageLocation

Hard-stop gate before deployment:

  • Confirm Part 1 mandatory system requirements are fully met.
  • Confirm SQL provider target is MSOLEDBSQL.
  • Confirm compatibility level baseline is SQL Server 2016 minimum or newer.
  • If any of the above is not true, stop and remediate before deploy.

6. Step 4 - Review the Steps page

After variables are confirmed, open the Steps page.

For a normal full MC upgrade run:

  • Leave the required upgrade steps selected according to the packaged installer workflow.
  • Do not uncheck steps unless you have a specific, documented reason approved for that environment.

Important:

  • This on-prem guide is for the full packaged upgrade path.
  • Unlike the SaaS migration database-only procedure, this is not normally limited to only Reg Db Upgrade and Entity Db Upgrade.

7. Step 5 - Execute deployment

  1. Confirm enableHttps is set as intended (normally true).
  2. Click Deploy Now.
  3. Monitor step progression from start to finish.
  4. Do not close installer UI while deployment is active.

Typical major stages include:

  • Prerequisite validation
  • Windows feature configuration
  • MC web/service package deployments
  • Database upgrades
  • Finalization scripts

8. Step 6 - Handle deployment outcomes

If deployment succeeds:

  • Confirm final summary shows no failed blocking steps.
  • Continue to Part 3 for validation.

If deployment fails:

  1. Record failed step name.
  2. Save full error message and timestamp.
  3. Capture relevant logs.
  4. Do not rerun immediately until failure cause is understood.

9. Execution checklist

  • Installer launched as Administrator.
  • Gather Variables From System completed.
  • Required values validated.
  • Steps page reviewed and left in intended state.
  • Deploy Now completed.
  • Final summary reviewed.
  • Failure evidence captured if any step failed.

After completing this checklist, continue to MC Upgrade - Part 3 Post-Upgrade Validation and Troubleshooting.