topic Re: Should App Volumes provisioning machine be a domain member or workgroup in Horizon Desktops and Apps

Should App Volumes provisioning machine be a domain member or workgroup

Joediallo — Wed, 04 Dec 2019 19:55:05 GMT

What is the best practice around App Volumes provisioning machine? Should the machine be on domain or in a workgroup?

Re: Should App Volumes provisioning machine be a domain member or workgroup

sjesse — Wed, 04 Dec 2019 20:10:41 GMT

I've always domain joined them, I think its in a guide somewhere.

Re: Should App Volumes provisioning machine be a domain member or workgroup

Suman1209 — Fri, 06 Dec 2019 07:47:30 GMT

The provisioning virtual machine usually joins the same domain as the production virtual machine. However, this is dependent on the applications that are being provisioned. Some application requirements and licensing models require that the virtual machine shares a common SID with the production virtual machine.

Find the Official Document from Vmware

Best Practices for Provisioning Virtual Machines and Applications

If This Solved your query Pls Mark as answered !

Re: Should App Volumes provisioning machine be a domain member or workgroup

HussamRabaya — Sat, 07 Dec 2019 20:07:33 GMT

it must be in domain , because when you provision Appstack you need to map it to VM(capture VM) , you would search with DNS name and if it not in domain you will not find it , so in order to proceed you will have to join it to domain

Re: Should App Volumes provisioning machine be a domain member or workgroup

mchadwick19 — Tue, 10 Dec 2019 15:45:38 GMT

Not true, you can enable the "Allow non-domain joined entities" option in your managers. When you install the AppVolumes agent on the non-domain system and enter the manager address it will register as a machine in your AV database and be available for AppStack provisioning and assignments. Here is the KB: VMware Knowledge Base