Sometimes, in certain autoscale scenarios, new hosts can be created by the autoscaling engine due to maintenance being performed on existing session hosts i.e reboots or running long-running scripts.
This can cause new hosts to be created and removed shortly after the maintenance has been completed. The issue lies in the case where configuration settings or applications may have been applied to the existing hosts, which then get removed and replaced by a brand new host that may require work to be done manually before being made available to the users.
To avoid this scenario, it would be helpful in scenarios where we are creating new hosts to meet minimum host pool criteria that if any hosts were to be deleted, the newest hosts would be removed first, leaving the existing hosts untouched.
Comments (2 comments)