Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


To deploy a virtual appliance, you must first create a join token and issue it to the corresponding on-prem host when you set up your machine. You can use the same join token to deploy multiple virtual appliances. You can also create as many join tokens as you need and use them for different purposes. For  For example, you can create one join token for to provision a set of remote devices , and and assign them to your Cloud Services Portal account. You can create another one join token for an admin who will manage need to join on-prem hosts only for a short period of time. You When the admin finishes the task, you can revoke the join token when the admin no longer manages the and they will not be able to provision any new hosts. You can also revoke a token if a join token has been compromised for any reason . An appliance cannot be connected to prevent its use to provision new on-prem hosts. A host cannot establish a new connection to the cloud if you use a revoked token; however, it keeps an existing connection. Note that join tokens are valid until you revoke them through the Cloud Services Portal.


  1. From the Cloud Services Portal, click Manage -> On-Prem Hosts.  
  2. Click the Join Tokens tab, and then click Create Token.
  3. On the Create Token page, complete the following:
    • Name: Enter a name for the new token.
    • Description: Enter some information about this token,
    • TAGS: Click Add to associate keys with the on-prem host and specify the following:
      • KEY: Enter a meaningful name for the key, such as a location or a department.  

      • VALUE: Enter a value for the key. Select the respective check box and click Remove to delete the associated key. For information about tags, see Using Managing Tags.

  4. Click Save & Close.
  5. The join token string appears in the Copy Token? dialog box. Click Copy to copy the token. You should copy the token string and save it in a place where you can find it later. You need this token string when you configure your virtual on-prem hosts.