Updating a collector manually

this describes how to manually upgrade a collector, see collector updates for a more automated approach the steps to upgrade the collector are the same as the steps to installing a collector docid\ iv4 sd56tdxcqkrkcj4kv generating a token will invalidate the current token after 24 hours, so the collector will still be able to send data between the generating of the new token and the upgrade there is no need to generate a new token to upgrade a collector if you still have the old token saved somewhere when upgrading from a version of the collector that does not have advanced settings available in the historian, the settings should be updating a collector manually /#recovering environment variables before upgrade the environment is overwritten during the upgrade process, so this should be done before upgrading the collector the variable names will change from upper snake case in the environment to uppercamelcase in the historian read the release notes of all collector versions between the previously installed version and the upgraded version to find any (breaking) changes in functionality and/or settings of the collector and/or its measurements recovering environment variables before upgrade linux you can find the environment variables in the environment file this can be found here /etc/systemd/system/environments/factry collector xxxxxxxx xxxx xxxx xxxx xxxxxxxxxxxx (replace the x’s with the collector id which you can find in the historian) windows open regedit navigate to computer\hkey local machine\system\currentcontrolset\services select factry collector xxxxxxxx xxxx xxxx xxxx xxxxxxxxxxxx (replace the x’s with the collector id which you can find in the historian) right click environment and select modify… take note of the values of all the environment variables, except for api token, service name and working directory configuration after installation the collector will register itself on the historian server and the collector settings will be ready to be filled in switching to a new collector service to switch a collector instance in the historian webpage to a new collector service, one needs to generate a new api token first next, use this token to install a new collector service finally, delete the previously existing collector service to cleanup the inactive collector service using a new server one is able to switch from an existing collector service, to a new collector service on a different server in this case make sure that the necessary tcp ports from the historian server are reachable by the new collector server