MC Upgrade - Part 1 Prerequisites
On-Prem Server

1. What this document is for

This document explains all prerequisite checks that must be completed before running MC Upgrade.

Use this document to reduce upgrade risk and prevent avoidable deployment failures.

This is the first document to use in the upgrade sequence. Do not open the installer until this document is complete.

2. When to use this document

Use this document:

  • Before the maintenance window starts.
  • Before opening DPInstaller.exe.
  • Any time an upgrade fails and you need to re-validate environment readiness.

3. Access and environment prerequisites

Confirm the following first:

  1. You have local Administrator rights on the target server.
  2. You can sign in interactively to the target server.
  3. You can access the installer bundle location.
  4. The server has enough free disk space for package extraction, deployment, and logs.

If any item above is missing, stop and resolve access before continuing.

4. System requirements (mandatory pre-check)

Verify all of the following are installed/configured before upgrade.

If any mandatory item is missing, the upgrade should be treated as blocked and must not proceed.

4.1 App/Web Server requirements

  • PowerShell 5+ / Windows Management Framework
  • NTFSSecurity PowerShell module
  • .NET Core 8.0 Hosting Bundle
  • Web-Server Windows Feature (IIS)
  • Self-signed (or trusted) certificate covering all required DNS names, selected in IIS bindings

4.2 All server requirements

  • TLS 1.2 enabled
  • NuGet package provider (recommended, not strictly required)
  • SQLServer PowerShell module
  • PSIni PowerShell module
  • .NET Framework 4.8 Runtime
  • .NET Core 8.0 Runtime for desktop apps (x64/x86 as required by your installer runtime usage)
  • MSOLEDBSQL version 18 driver

4.3 Database server requirements

  • SQL Server 2019 or 2022
  • Database compatibility level equivalent to SQL Server 2016 minimum or newer
  • Connectivity from app/web server to SQL instance is validated

4.4 Authentication/connectivity requirements

  • If using Windows authentication, the account running installer has required SQL access.
  • If using SQL authentication, credentials are valid and tested.
  • SQL provider path resolves to MSOLEDBSQL.

5. Backup and rollback prerequisites

Before any upgrade action:

  1. Take a VM snapshot or server backup.
  2. Confirm SQL backups exist for key MC databases.
  3. Document rollback owner and rollback trigger criteria.
  4. Confirm maintenance window start/end times.

Minimum rollback plan should answer:

  • Who approves rollback?
  • How long restore takes?
  • Which systems/users are impacted?

6. Installer package readiness

Validate package contents in the local working folder:

  • DPInstaller.exe
  • DPInstaller.project.json
  • Package folders required by your installer build

Also confirm:

  • Files were extracted fully (no partial copy).
  • No SmartScreen/quarantine block remains on executable files.
  • Endpoint security is not actively deleting package files.

7. SQL and database prerequisites

Before running upgrade:

  1. Confirm target SQL instance is reachable from the application server.
  2. Confirm serverInstance value is correct.
  3. Confirm regDbName (typically mcRegistrationSA).
  4. Confirm which auth mode will be used:
    • SQL authentication (dbUsername / dbPassword), or
    • Integrated security (integratedSecurityUsername / integratedSecurityPassword).

Important:

  • Confirm the registration database name is the intended environment value.
  • Do not proceed with temporary, placeholder, or guessed database names.

If SQL connectivity/authentication fails during this check, resolve now instead of inside deployment.

8. Configuration inputs you must decide in advance

Prepare and verify these values before opening the installer UI:

  • websiteHostName
  • installDirectory (default C:\MCApps unless approved change)
  • loggingPath
  • imageServerPath
  • dataProtectionKeyStorageLocation
  • enableHttps (normally true)
  • proxyDisabled
  • smtp
  • suppressMroCustomFileCopy (normally false unless change is planned)

Store approved values in your change ticket or run sheet.

9. Additional requirements and upgrade considerations

Confirm the following before execution:

  • Database compatibility mode is SQL Server 2016 minimum (or higher).
  • SQL provider is set to MSOLEDBSQL.
  • Valid hostname is configured and bound in IIS.
  • Client internet connectivity requirements are understood for internet-dependent features.

10. Pre-flight checks on server services and network

Before deployment, validate:

  • DNS/host binding decisions are finalized for websiteHostName.
  • Required firewall paths between app server and SQL are open.
  • IIS and dependent Windows features are not manually locked down in a way that blocks upgrade.
  • Service accounts used for file and network access are valid and not expired.

11. Prerequisite completion checklist

Proceed to Part 2 only when all items are true:

  • Admin access confirmed.
  • Backup/snapshot and SQL backups confirmed.
  • Installer bundle validated.
  • Mandatory system requirements verified on each server role.
  • SQL connectivity and auth path confirmed.
  • SQL provider validated as MSOLEDBSQL.
  • SQL compatibility level validated.
  • Required variable values prepared.
  • Network/DNS/service account checks completed.
  • Certificate and IIS binding checks completed.
  • Maintenance window and rollback plan documented.

Once all items are complete, continue with MC Upgrade - Part 2 Execute Upgrade.