How to: Add Devices to your ZPE Cloud company using Customer Code and Enrollment key

ZPE Cloud is a powerful tool for managing your Nodegrid devices, and one of the recommended methods to add devices to your company in ZPE Cloud is to use the Customer Code and Enrollment key. Customer Code is a unique 5-digit identifier assigned to each company and Enrollment Key is a key initially randomly generated that can be changed by authorized company users in ZPE Cloud, together they represent the company's enrollment credentials. Here's how to add devices to your company in ZPE Cloud using customer code and enrollment key:

Here's how you can do it in GUI:

1. Log in to ZPE Cloud as an admin, and go to the Settings > Enrollment tab.

2. Under the Settings > Enrollment tab, make sure Enable Device Enrollment is checked and click Save, then copy Customer Code and Enrollment key to use in next steps.

3. Log in to Device's GUI as an admin, and go to the System > Toolkit tab.
   

4. Under the System > Toolkit tab, click to Cloud Enrollment.

5. You'll see a form is opened to provide the Customer Code, Enrollment Key. Enter the Customer Code, Enrollment Key and URL and click Save. URL is only required when enrolling device out of zpecloud.com.
   

6. You'll see a confirmation message that the device has been transferred into your company in ZPE Cloud.
   

7. Go back to ZPE Cloud, the device will now appear in the Devices > Available tab. If device was already loaded into the ZPE Cloud company and under Devices > Enrolled tab, it will appear in the Devices > Enrolled tab and next steps are not required.
   

8. Select the device that you just added and click Enroll. This will enroll the device in ZPE Cloud.

9. Once you've enrolled the device, it will be listed in the Devices > Enrolled tab. You're all set to start using it!
   

Here's how you can do it in CLI:

1. Log in to ZPE Cloud as an admin, and go to the Settings > Enrollment tab.

2. Under the Settings > Enrollment tab, make sure Enable Device Enrollment is checked and click Save, then copy Customer Code and Enrollment key to use in next steps.

3. Log in to Device's CLI as an admin, and type the following commands, replacing <customer_code> by the Customer Code and <enrollment_key> by the Enrollment Key. URL is only required when enrolling device out of zpecloud.com:
   
   cd /system/toolkit
   cloud_enrollment
   set customer_code=<customer_code>
   set enrollment_key=<enrollment_key>
   set url=<url>
   commit

4. You'll see a confirmation message that the device has been transferred into your company in ZPE Cloud.
   

5. Go back to ZPE Cloud, the device will now appear in the Devices > Available tab. If device was already loaded into the ZPE Cloud company and under Devices > Enrolled tab, it will appear in the Devices > Enrolled tab and next steps are not required.
   

6. Select the device that you just added and click Enroll. This will enroll the device in ZPE Cloud.

7. Once you've enrolled the device, it will be listed in the Devices > Enrolled tab. You're all set to start using it!

Note: For the device to show Online in ZPE Cloud, make sure Enable ZPE Cloud is checked under Security::Services in Device's GUI. 

For Device's CLI type, set /settings/zpe_cloud/ enable_zpe_cloud=yes and commit

Please note that adding a device by Customer Code and Enrollment Key is one of the methods to add a device to ZPE Cloud, but there are other ways as well, described in the following article How to Add Devices to a Company in ZPE Cloud.

It's important to note that adding a device by Customer Code and Enrollment Key can only be done through Device via API, CLI, GUI or Shell (Shell strict restricted to ZPE only) and not through ZPE Cloud. If you have any questions or need assistance with this process, don't hesitate to reach out to our support team.

Here're screenshots to help in the visualization of the process:

Settings > Enrollment tab to copy Customer Code and Enrollment Key, that can be used in Step 1, 2 and 5.

System > Toolkit tab to click Cloud Enrollment, that can be used in Step 3 for Device's GUI.

Form to add a device by Customer Code and Enrollment Key under System > Toolkit tab, that can be used in Steps 3, 4 and 5 for Device's GUI.

We hope this guide was helpful in adding your Nodegrid device to your company in ZPE Cloud. If you have any questions or encounter any issues during the process, please refer to our knowledge base for more information. If you still need assistance, don't hesitate to contact our support team and we'll be happy to help you.

• Related Articles

• Guide: Add Devices to a Company in ZPE Cloud

  Overview There are different methods to associate Nodegrid appliances with a specific ZPE Cloud company: Claim ID, Transfer Key or Customer Code and Enrollment Key. These different methods provide flexibility to fit the different corporate ...

• How to: Add Devices to your ZPE Cloud company using Transfer Key

  ZPE Cloud is a powerful tool for managing your Nodegrid devices, and one of the methods to add a device to your company in ZPE Cloud is to use a unique 45-digit Transfer Key, which is a unique identifier assigned to a device or list of devices. ...

• How to: Add Devices to your ZPE Cloud company using Claim ID

  There are different ways to add a device to ZPE Cloud, but one of the recommended methods is to use its unique 8-digit Claim ID. Here's how you can do it: Locate the Claim ID for your Nodegrid device. You can find the Claim ID on a sticker located on ...

• How to: Create a ZPE Cloud account and add ZPE Cloud users 

  To create ZPE Cloud users, you must have a ZPE Cloud account. ZPE Cloud accounts are bonded to your company. Company is the denomination of your tenant in ZPE Cloud. The ZPE Cloud account manages the ZPE Cloud company. 1. Access zpecloud.com or ...

• How to: Create and apply configurations to your device using ZPE Cloud

  Overview ZPE Cloud profiles enable to perform operations to your Nodegrid devices, such as: configurations, custom scripts, backups, software upgrades, and cellular modem firmware upgrades. In this document, we are focusing on the configuration ...