--- title: "Get a New Device Registration Code" slug: "get-a-new-device-registration-code" updated: 2026-08-04T12:11:25Z published: 2026-08-04T12:11:25Z canonical: "support.controlup.com/get-a-new-device-registration-code" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.controlup.com/llms.txt > Use this file to discover all available pages before exploring further. # Get a New Device Registration Code Your tenant's device registration codes are used when installing the ControlUp for Desktops Agent or Agent Manager to enroll a new device. This article describes how to create and manage your registration codes. New codes are generated using a stronger and more secure algorithm. If your tenant was created after July 21, 2026, you already have a new code by default and don't need to switch codes. If your tenant was created on or before July 21, 2026, you're still using a legacy code and need to switch. To improve your security, all legacy codes will **automatically expire on August 31, 2026**. Before that date, you must create a new code and [update your deployment resources to use it](/v1/docs/get-a-new-device-registration-code#updates-required-when-you-create-a-new-code). If you don't create a new code, you won't be able to register new devices to ControlUp. You can confirm which type of code you have by checking its length: new codes are 64 characters, legacy codes are 40 characters. ## Current devices stay registered Changing your registration codes **does not affect** devices that are already registered in your tenant. Registration codes are used only when a device first registers with your tenant. ## Updates required when you create a new code When you create a new code, you must update all your **deployment resources** to use the new code. Your old code remains active until it expires or you delete it, giving you time to implement these changes: 1. Replace any old Device Registration Codes with the new one in all your deployment resources as listed below. 2. Check whether you deploy the Agent through the **Agent Manager** or **direct Agent installation**. If you aren’t sure which method you use, [read below to learn more](/v1/docs/get-a-new-device-registration-code#understanding-agent-manager-vs-direct-agent-installation). - If you use the **Agent Manager**, replace any Agent Manager installation files with the latest version that supports the new codes (2.17.8.394 for Windows and 2.18.2.3268 for macOS). Download the latest version from the [**Downloads page**](/v1/docs/controlup-for-desktops-agent-installation-overview)**.** - If you use **direct Agent installation**, you don’t need to update your Agent version. The current Agent versions already support the new codes. Make sure you update your code and Agent Manager files (if used) in every applicable area such as: - **Installation scripts** - **Deployment commands** - **Golden images** - **Virtual machine templates** - **MDM profiles** (for example Intune for Windows and Jamf for macOS) - **Thin client configurations** - **ChromeOS extension settings** (See [ChromeOS Deployment](/v1/docs/chromeos-deployment) for details.) **Best practice:** You should not keep multiple codes active for a long period of time. You should fully switch to the new code as soon as possible and then delete the old code when you are finished. ## How to create a new code > [!NOTE] > Permission required > > To create and delete codes, you must have the **Manage device registration code** permission located under **Device Permissions > Configuration > Agent Registration**. This permission is included in the default **Admin** role. Viewing the Agent Registration page to see your existing codes requires the permission **Show Agent Download Page**. 1. Go to **Devices** > **Configuration** > **Agent Registration**. You see all Device Registration Codes created for this tenant. ![Access Agent Registration Settings](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AccessAgentRegistrationSettings(2).png) 2. Click **Create new**. 3. Optionally enter a **Description** for the new Device Registration Code, for example a code you are using for testing. 4. Select whether you want to designate an **Expires after** duration or **Never expires**. If you select **Expires after**, you must select a **Duration**. After you create the new code, it appears in the table. 5. Update each of your [deployment resources listed above](/v1/docs/get-a-new-device-registration-code#updates-required-when-you-create-a-new-code) with the new code. 6. After you have fully implemented the new code, **Delete** your old code. Note: deleting a code can’t be undone. **Note:** The installation commands on the **Downloads** page are prepopulated with your tenant name and registration code. They are automatically updated to include your most recently created code. ## How to re-register an existing device using a new code Switching your existing devices to use the new code **is not required**. Currently enrolled devices continue to work even after you generate a new code. However, if for some reason you need to delete and re-register a device, perform the following steps to re-register using the new code. 1. Uninstall the Agent and the Agent Manager (if used). You can use our uninstall scripts for [Windows](/v1/docs/edge-dx-agent-distribution-and-installation-for-windows#scripted-agent-uninstall) and [macOS](/v1/docs/edge-dx-agent-distribution-and-installation-for-macos#uninstall-the-agent-with-a-script). 2. If you use the Agent Manager (available for Windows and macOS), download the latest version from the [**Downloads** page](/v1/docs/controlup-for-desktops-agent-installation-overview). Only the latest versions support the new stronger codes. 3. Reinstall the Agent Manager or Agent using the new code. Note that for macOS, you must first unmount any existing installers before you install the new Agent Manager. ## Understanding Agent Manager vs. direct Agent installation **Windows and macOS:** Windows and macOS support both deployment options (Agent Manager and direct Agent installation). When you deploy the Agent Manager, it automatically installs the Agent and keeps the Agent updated according to your [version control settings](/v1/docs/agent-version-control). The Agent Manager file is `agentmanagersetup.msi` for Windows or `ControlUp Agent Manager.dmg` for macOS. If you use ControlUp’s built-in version control, it means you have the Agent Manager installed. This is the most common deployment method for Windows and macOS. Some customers choose not to use the Agent Manager and instead deploy the Agent directly and control versioning using separate deployment software. If you use this method, you install the Agent directly using a `sipagentx.xx.x.xxxx.msi` or `ControlUp Agent vx.xx.x.xxxx.dmg` file. **All other operating systems:** Direct Agent installation is the only available deployment option.