Have new cloud instances register with your console the first time they boot, by adding the HyperView install command to the deployment. Nothing needs doing on the instance afterwards.
Before you start
An installation key set up the way you want new instances filed: folder, owner and settings. These instances register unattended, so the key is your only chance to get that right. See Installation keys.
Use a key created for this deployment rather than a shared one, so you can replace it without affecting anything else.
NOTE: The command contains your installation key. Pasting it into a deployment puts it everywhere that deployment goes: templates, the repository they live in, CI logs, and the provider console. Anyone with the command can register systems into your account. If a template ends up somewhere it shouldn't, deactivate the key and create a new one.
Step 1 - Get the instructions for your provider
Go to Installation.
Choose your installation key and the Target OS of the image you're deploying.
Under Option 2: Install automatically when deploying to a cloud provider, click your provider: Microsoft Azure, Amazon AWS, Google Cloud, Alibaba Cloud, Oracle Cloud, IBM Cloud, Tencent Cloud, OVHcloud, Hostinger or DigitalOcean.
The instructions open with the script already filled in for your key and OS. For example, Google Cloud:
The steps for your provider. Here, the gcloud CLI or the Cloud Console.
The startup script to add to the instance.
The copy button.
For providers with a CLI, a complete command that creates the instance with the script already attached.
Step 2 - Add the script to the instance
Copy the script.
In your provider's instance-creation flow, paste it into the first-boot field (user data, custom data or startup script, depending on the provider). The instructions name the exact field.
Launch the instance.
Step 3 - Check it registered
Go to Systems. The instance appears with a green dot shortly after it boots.
Check it's in the folder, and has the owner, that your key sets.
In Admin > Installation Keys, the key's Installs count has gone up.
Installing at first boot vs in a golden image
Install at first boot whenever you can. Each instance installs and registers on its own and appears as its own system.
If you install the HyperView Server into a golden image instead, every instance launched from it starts with the same identity, so the console sees them as clashing and they register again. What happens then depends on Default Installation Key under Admin > Account Settings > General Settings. Read A system didn't register, or registered twice before using a golden image.
Troubleshooting
Nothing appeared. The script may not have run. Check the instance's boot log or cloud-init log.
The script ran but failed. The network may not have been up yet, or the script didn't run with administrator or root rights.
The instance is in the wrong folder. Fix the key, then move the system with Assign to folder. Changing the key doesn't move systems that have already registered.