KB Article #190044

Existing Installation Not Detected During Server Upgrade

When upgrading a server (whether it is a modelling, production, or domain server), you might encounter a situation where the upgrade process does not detect the existing installation and only offers the option to perform a new installation.

This typically happens when the user running the upgrade does not have access to the metadata created during the initial installation, which is necessary for the system to recognize the existing environment.

Solution

To ensure the upgrade process correctly detects the current installation, you need to copy the hidden .Automator directory from the home directory of the user who performed the original installation to the home directory of the user performing the upgrade.

cp -r /first_install_user/.Automator /update_user/.Automator

⚠️ Important:
After copying, make sure the .Automator directory has the appropriate ownership and permissions so that the update user can fully access it during the upgrade process.

Once completed, the installer should correctly detect the existing server instance and proceed with the upgrade instead of initiating a fresh installation.