Updating a collector manually

this page describes how to manually update a collector for a more automated approach, see docid\ g3adod9upom4alslqulwr important upgrade notes manually updating a collector follows the same steps as docid\ iv4 sd56tdxcqkrkcj4kv generating a new api token will invalidate the current token after 24 hours during this period, the collector will continue to send data if you still have the existing token available, you do not need to generate a new token to upgrade the collector when upgrading from a collector version that does not support advanced settings in the historian, you must first docid\ leqkpxddjqenepmncv45c before upgrading during the upgrade process, the environment is overwritten before upgrading, always review the release notes of all collector versions between your current version and the target version for any breaking changes recovering environment variables before upgrade linux environment variables are stored in the environment file /etc/systemd/system/environments/factry collector xxxxxxxx xxxx xxxx xxxx xxxxxxxxxxxx replace the x values with the collector id (available in the historian) windows open registry editor navigate to computer\hkey local machine\system\currentcontrolset\services select factry collector xxxxxxxx xxxx xxxx xxxx xxxxxxxxxxxx right click environment and select modify… note all environment variables except api token service name working directory configuration after installation, the collector automatically registers itself with the historian the collector configuration will then be available in the historian ui switching to a new collector service to switch a collector instance in the historian to a new collector service generate a new api token install a new collector service using this token remove the old (inactive) collector service from the system using a new server you can move a collector to a different server ensure that all required tcp ports from the historian server are reachable from the new collector host expected outcome after a successful upgrade the collector runs the new version the collector reconnects to factry historian the collector appears online and resumes sending data existing measurements and configuration remain available troubleshooting collector does not come online after upgrade possible causes incorrect api url configured in the historian network connectivity issues between the collector host and the historian verify the api url under configuration > general > api > url , confirm network access, and check that required settings were restored before upgrading