Prepare:

1. Download the latest MCe installer

• You will need to visit the download page to download the installer/upgrader: https://files.maintenanceconnection.ca/
• You will be asked for the Name, and the Download Code, so enter your name for the name field and then enter the download code "MCeLatest1", then hit the button "Download Now" when the button turns blue to start downloading.

Enter in your info

Starting to communicate with the server

Confirmation of code and prep for download

Your browser might ask where to download it to

Or it might just decide where to put it. This is very browser, browser version and in some cases browser configuration dependent.

Then your browser will show, in whatever specific way it does it, the download progress

2. OPTIONAL: Turn IIS off for MCe pool.

Remember: MCe runs offline, so most users won't even notice!

There could be some minor temporary problems for users that refresh usually fix.

3. Backup the entity database

While we almost never need the backup, but it is good to be safe.

4. Backup the reg database

While we almost never need the backup, but it is good to be safe.

If you roll back - try just rolling IIS back first, leave the database updated.

There are almost never any problems running 'old' MCe on 'new' database structure.

To back up an IIS configuration using the Windows Command Prompt (CMD), use AppCmd.

1. Open Command Prompt as Administrator

Then go to the IIS AppCmd folder:

cd %windir%\system32\inetsrv

2. Create an IIS backup

appcmd add backup "IIS_Backup"

This creates a backup of your IIS configuration.

The backup will normally be stored under:

C:\Windows\System32\inetsrv\backup\IIS_Backup

Check available IIS backups

appcmd list backup

Restore an IIS backup

appcmd restore backup "IIS_Backup"

Example with a dated backup name

appcmd add backup "IIS_Backup_20260905" 

You could be using LoginHub with an Identity Provider and giving features like SSO (SSO is optional but almost everyone uses SSO if they use an Identity provider)

You could be using LoginHub without an identity provider (this is rare currently but we expect that may change in the future.

So go to where you login, likely with https:://example.com/mc_web and if you get a LoginHub screen, you are running LoginHub

2. Run the MCe install/upgrader

Pressing the 'install' button here actually is EXTRACTING the installer.

3. Install button to start the extraction process

Once you confirmed that you are on the correct directory, hit the "Install" button to start.

4. Progress displayed or errors

You will see progress bar of the installation until you see a welcome page with the "Next" and "Cancel" button for the next process. See picture below

If you get an IIS not detected dialog box ... you probably forgot to run as administrator.

5. Next then Confirm connection settings

Simply hit "Next" to proceed

Confirm connection settings

You will then be asked to confirm the connection settings

Make sure they are correct and the status bar is showing green. If you are unsure, hit the "Retry" button to check the connectivity. See screenshot below

Double check that the SQL Server name is the correct one

6. Next to proceed

If everything is OK then hit the "Next" button to proceed to the next step.

The LoginHub and Reliability settings.

If you are using LoginHub you MUST check the MC LoginHub, if you are not you must NOT select it!

If you are running Windows 2022 or higher you MUST select the Reliability Service

7. LoginHub? (identity provider and SSL)

You checked earlier... If you have LoginHub on your server for the authentication then tick the checkbox for MC LoginHub

8. If you are using Windows 2022 or higher, select the Reliability server

Make double sure the setting for the Reliability Service for the advanced email settings is correct.

9. Next Check IIS Setup settings

You will then be redirected to the IIS setup for your MCe. Normally you don't need to do anything on this page, you just need to make sure the "Server Access URL" is correct and then you may proceed by hitting the "Next button.

11. Now you are ready to install

The next page, this is important and "Install or Upgrade" button must be clicked to do the upgrade. See screenshot below, you MUST click the button that is highlighted in a red rectangle below.

12. Progress, please be patient

Once you clicked on the "Install or Upgrade" button a progress bar will show as a proof of an upgrade happening. See screenshot below.

13. Verify then complete

Once they all show as green or checked icon, then hit Next to proceed and you are done.

SQL

• Some on-prem systems don't give our SQL user account enough privileges to do the table structure upgrades.
  • If so ... you probably know who you are! If that is the case you have a couple options,
  • Option 1: Temporarily give the user you have defined for MCe higher permissions
  • Option 2: run the upgrade scripts manually (they run slower in SSMS than in our code... except when our code doesn't have permission and they don't run!)

It will give you a quick message (toast) when done

Do a quick test to log in:

If you get the following 2, likely you don't have LoginHub but you clicked on the LoginHub option above.

Some on-prem systems don't give our SQL user account enough privileges to do the table structure upgrades.

• If so ... you probably know who you are! If that is the case you have a couple options,
• Option 1: Temporarily give the user you have defined for MCe higher permissions
• Option 2: run the upgrade scripts manually (they run slower in SSMS than in our code... except when our code doesn't have permission and they don't run!)

  Option 1

  Run it remotely. For instructions on this MCe Upgrade - Triggering MCe database Upgrade remotelyIt also has instructions for creating SQL scripts that you run in a tool like Microsoft's SSMS

  Option 2

  If you are still on the Web/App server, you can do it this way:Load a modern browser that is up to date, you should likely use Chrome. Do NOT use IE. There are problems reported with Edge.Run against the HostnameDo NOT run on 127.0.0.1 !! This can cause problems, and they aren't always obvious at first. The extent of the problems depends on timing, but there will be problems so don't do this.

  Running from the IIS server, Double click on one of the MCe logos

  a

  Click on Advanced Tools

  

if you get:

you aren't running it on the server, or the app can't tell that you are on the server. Don't run with a URL that makes it looks like it is not running from the server, and you may not have your hosts file set up correctly.

Fixing a broken Hosts file

Quickest Method (NotePad++ or NotePad.)

1. Open Notepad(++) or your tool as Administrator:

• Press the Windows key, type "Notepad".
• Right-click on Notepad and select "Run as administrator".

2. Open the File:

• In Notepad, go to File > Open.
• Paste the following path into the address bar at the top and press Enter: C:\Windows\System32\drivers\etc.
• Change the file filter in the bottom-right corner from "Text Documents (.txt)" to **"All Files (.*)"**.
• Select the file named hosts (it has no extension) and click Open.

3. You need to point the sub domain to 127.0.0.1 so it pulls the sub domain as local domain.

So let's say your users connect to MCe by typing: https://cmms.example.com/mce you would use

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
 
# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost
 
 
127.0.0.1			cmms.example.com

Similar instructions for your favorite text editing tool like VSC, or at least the tools available on the server.