Manage ClickOnce-deployed clients when moving the FactoryLogix server to a new server

KB Article administrator on-premise only

Overview

When a FactoryLogix server is decommissioned and replaced with a new server, FactoryLogix client machines that were deployed via ClickOnce require attention. The ClickOnce-deployed applications will continue to function but will no longer receive updates because the original UNC path used for deployment becomes permanently inaccessible when the server name changes.

How ClickOnce update checking works

Every time a ClickOnce-installed client launches, it checks the exact UNC path originally used to deploy the application. If updated source files are present, ClickOnce downloads the new version. If the UNC path is inaccessible, the check is skipped and the client launches without updating. Because the server name is part of the UNC path, changing to a new server name creates a new UNC path and makes the original path permanently unreachable.

Resolution

For each affected user on each affected client machine:

1. Use the standard Windows uninstall utility to uninstall the existing ClickOnce installation for the affected user.

2. Navigate to the shared Client Installations folder on the new server and run the .application file to reinstall using the standard ClickOnce installation procedure.