How to Change the Device Registration Code for ControlUp Windows Agents Without Reinstalling

The Windows Agent Manager for ControlUp stores the Device Registration Code (DEVREGCODE) in the system registry at the location HKEY_LOCAL_MACHINE\SOFTWARE\Avacee\SIP, specifically under the value named DeviceRegistrationCode. This registry entry is critical for device identification and communication with the ControlUp environment. When a machine with an outdated registration key falls out of the monitoring system and then comes back online, it can cause connectivity or recognition issues due to the persistent old registration information.

It is possible to change the Device Registration Code without performing a full reinstall of the Windows Agent. This can be done by editing the registry value directly at the specified path. After modifying the DeviceRegistrationCode, it is necessary to restart the ControlUp agent service for the change to take effect. However, simply changing the registry value is not sufficient if the device has previously registered with ControlUp, as cached identity data may cause the agent to continue using the old credentials.

To fully re-register the device within ControlUp, it is also required to delete specific cached files that store device tokens. These files are located in the directory C:\ProgramData\Avacee\sip_agent\cachefiles and include uid.txt and DeviceAccessToken.txt. Removing these files forces the agent to discard the old cached tokens and register anew using the updated Device Registration Code. This approach facilitates scripted remediation, making it practical to deploy changes via Group Policy Objects (GPO), Microsoft Intune, or similar device management tools. However, it is strongly advised to test such changes on a limited set of devices first to confirm that the process completes successfully and does not inadvertently disrupt device monitoring.

In summary, updating the Device Registration Code on a ControlUp-managed machine without reinstalling is achieved by directly editing the registry, restarting the agent service, and clearing cached device token files to force re-registration. This method is useful when older registration keys cause devices to lose or restore connectivity improperly in ControlUp environments.

Read the entire ‘How to Change the Device Registration Code for ControlUp Windows Agents Without Reinstalling’ thread below:

Heyo – Can anyone help me with where the Windows Agent Manager stores DEVREGCODE after install, and can it be changed without a reinstall? Running into issues when a machine with an old reg key falls out of ControlUp and goes back online later

HKEY_LOCAL_MACHINE\SOFTWARE\Avacee\SIP

If you have a system that can do it yes, i have done it with a few devices

Thinking about righting a remediation script to target it

Thank you Eugene. You were lightning fast with that!

As Eugene says, the code lives in HKLM\SOFTWARE\Avacee\SIP under DeviceRegistrationCode. You can edit it in place and restart the service, with no reinstall. If the device has already registered, also delete its cached device access token file, or it will keep using the old identity. This suits scripted changes through GPO, Intune or a similar tool, since the installer’s own parameters just write the same value.

Advised to remove these files to re-register the device:
`C:\ProgramData\Avacee\sip_agent\cachefiles\uid.txt`
`C:\ProgramData\Avacee\sip_agent\cachefiles\DeviceAccessToken.txt`

Thanks Joel and Abel. (Abel you responded to me in both places, sorry about the sprawl and thank you again.)

no worries, happy to help!

When we deployed the new reg code back in August, we didn’t consider this self-clean scenario causing issues later.

And always test on a limited set of devices first of course

Totally

Continue reading and comment on the thread ‘How to Change the Device Registration Code for ControlUp Windows Agents Without Reinstalling’.  Not a member? Join Here!