MCe upgrade
Steps to follow

MCe upgrades are relatively easy and usually take a small amount of time (minutes, not hours.)

1. Download the latest MCe installer

  • You will need to visit the download page of the installer --> Click Here
  • 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.
image.png

2. Turn IIS off for MCe pool.

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

3. Backup the entity database

4. Backup the reg database

5. OPTIONAL: IIS can be backed up as well

But only one setting - the directory of files it points to - needs to be changed if you want to roll back, so backing it up is not all that critical.

  • 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.
  • There ARE occasionally issues with old MCe when Accruent makes upgrades that are NOT backwards compatible, because of course the old MCe doesn't know to handle the data differently.
    • It's been since 2022 since they did that.
    • But in those cases, you would have ALSO recently upgraded MC - and got an MCe that is compatible with it, so reverting just MCe is unlikely a good choice in that situation.

6. If we are helping you do the upgrade, this is the point to call us in

or this is the point you should be at before a scheduled meeting.

7. Run the MCe install/upgrader

image.png

8. Install button to start

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

9. Progress displayed

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

image.png image.png

10. Next

Simply hit "Next" to proceed

11. 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

image.png

12. Next to proceed

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

The LoginHub and Reliability settings.

image.png

13. LoginHub? (identity provider and SSL)

If you think you have LoginHub on your server for the authentication then tick the checkbox for MC LoginHub and also for the Reliability Service for the advanced email settings then hit Next.

14. Double check then Next

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.

image.png

15. 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

image.png

16. 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.

image.png

17. Verify then complete

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

image.pngSQL

  • 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!)

18. If you elevated the permissions of the SQL user for MCe, you may want to dial them back now

19. Run the database upgrades.

Option 1

Run it remotely. For instructions on this MCe Upgrade - Triggering MCe database Upgrade remotely

It 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 Hostname

Do NOT run on 127.0.0.1 !! This can cause problems.

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

image.pnga

19 b) Click on Advanced Tools

image.png

if you get:

image.png

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:

Quickest Method (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
image.png

Similar instructions for Notepad++ or other similar tools.

19 c) Make sure you have 3 checkmarks for the the database updates

The first check mark is just whether it can connect.

The second two run the upgrade of the database. Just by 'coming here' they start to run. But you should check after and upgrade by clicking on the recheck buttons in order.

If you need the SQL to run in SSMS instead of here - click on the Upgrade SQL

image.png

When the upgrade is complete, go to the next step

20. Turn IIS pool back on

Appendix: Backup IIS configuration

You can run the following scrip inside a PowerShell on your app/web server to backup your IIS configuration

$backupName = "IIS_Config_Snapshot_$($(Get-Date).ToString("yyyyMMdd_HHmmss"))" & $env:SystemRoot\System32\inetsrv\appcmd.exe ADD backup "$MC2025UpgradePrep"

Record the name

If you need to rollback, replace the 20260323_141401 part with the name you saved above

# Restore the backup
$backupNameToRestore = "IIS_Config_Snapshot_20260323_141401" & $env:SystemRoot\System32\inetsrv\appcmd.exe RESTORE backup "$MC2025UpgradePrep"