Add the ability to bypass the VM Deployment Options on manual Host Creation

Avatar
Dave Stephenson

This idea might be a little far out there, but I was recently testing out some Host Pool stuff and found myself wanting to easily deploy a host without the VM Deployment options (i.e. UAM Applications, Scripted Actions, etc.) being triggered so I could quickly add a vanilla host. I know I could setup a test environment (i.e. add a new host pool, customize the deployment options to not include automations, create a host, etc), but sometimes it's useful to quickly deploy a host ASAP just for a quick sanity check.

I'm guessing the logic for this would be pretty simple on the back end to implement it (IF BypassVMDeployment = true THEN Skip Script Deployment ELSE Deploy Scripts) however, I may be oversimplifying this.

Has anyone else been in this scenario before?

Related to:

VM Deployment Host Pool Properties AVD Scripted Actions
1

Comments (3 comments)

Sort by
0
Avatar
Carl Long
We appreciate your feature request—community input is essential to our ongoing development.

Next steps:
     • We will review your suggestion and update its status during the evaluation process.
     • If further clarification is needed, we'll contact you via comments.

We also encourage others to contribute through feedback and voting.
0
Avatar
Randy Lehman

The only potential problem I see with this option is users are assigned to the 1 host pool and could end up with a session on the test host. 

My testing has taken long enough for a separate host pool to make more sense. Then any test users know they are connecting to the test host.

0
Avatar
Dave Stephenson

Very good point, Randy.
It sounds like I was having a moment of insanity.😂

Best practice is to have a separate host pool for testing.
Even if you don't keep a VM in it all the time.

Please sign in to leave a comment.