In our environment, Personal Desktops may be deployed into several different AD OU containers. Currently, the target AD OU is defined at the Host Pool level rather than as part of the VM deployment configuration. As a result, we must either maintain a separate host pool for each AD OU, which is difficult to manage, or rely on external automation for deployments, which reduces the value of Nerdio’s built-in deployment features.
We would like to request the ability to specify the target AD OU for domain join during Virtual Machine deployment, rather than having it inherit the AD OU configured in the host pool settings.
Comments (0 comments)