Summary
When manually adding a session host to an existing Dynamic Host Pool, Nerdio currently requires the administrator to manually enter the host name. This field should be pre-populated using the pool’s existing auto-scale naming convention, as defined in the pool configuration.
Problem Statement
In Dynamic Host Pools, Nerdio already enforces a host naming standard via the auto-scale configuration (for example:dguksavdst-{??}).
However, when an administrator clicks “New Host” and manually adds a session host to the pool, the Host name field is empty and requires manual input.
This introduces several issues:
- The administrator must manually re-type or remember the naming convention.
- There is a higher risk of naming inconsistencies or errors.
- It creates unnecessary administrative overhead for a task Nerdio already has sufficient context to automate.
Given that the host is being added to an existing pool, it is highly likely—and effectively required—that the host name conforms to the pool’s established naming standard.
Expected / Desired Behaviour
When adding a new session host to a Dynamic Host Pool:
The Host name field should be automatically pre-populated using the pool’s configured auto-scale naming pattern. Ideally, Nerdio would at minimum, present the naming pattern as the default value (editable if required).
Example:
If the pool naming pattern is:
dguksavdst-{??}
Then the Host name field should default to something like:
dguksavdst-04
(or the next available number in sequence).
Benefits
- Reduces manual admin effort and friction.
- Prevents naming inconsistencies within host pools.
- Improves UX by reusing configuration Nerdio already has.
- Aligns manual host provisioning with auto-scale behaviour.
- Makes manual scaling a first-class, low-risk operation rather than an exception case.
Thank you very much, we love Nerdio!
Comments (5 comments)