Managed Host Enrollment
Enrollment turns a real host into a Managed Host by installing and binding the DRLink Agent to the Server.
Server commands
After enrollment:
Identity boundary
Managed Host identity is tied to the enrolled Agent/machine identity, not merely to a display label, hostname, or observed NAT/public IP.
Enrollment credentials are bootstrap credentials. They are not the same as the persistent Agent management identity or Relay Engine transport credential.
Next step
For additional services after enrollment, create them on the owning Agent Host.
Automatic setup and additional services
Services selected through Zero-Touch SSH only, RDP only or Choose Remote Services automatically receive the required Service Object, Remote Service and public endpoint reservation during enrollment. Do not create the same service manually again. Inspect actual names with show remote-services on the Agent.
A blank username in SSH only affects connection hints; it is not management-only enrollment. To enroll without publishing services, run set enrollment bulk, choose count 1 and leave the SSH username blank. Choose Remote Services requires at least one service. OS accounts, sshd/RDP, external firewalls and Access Policy rules remain separate.
Only when adding a new destination/port to an existing Agent, inspect/prepare the Server Object definitions and use set remote-service <NAME> on the owning Agent.Last modified on October 29, 2026
