App Volumes uses a provisioning machine to capture applications in order to create AppStacks. According to the App Volumes User Guide, “the provisioning of AppStacks must be performed on a clean base image…”
In my opinion, a “clean base image” implies that this machine is not domain joined and therefore not inheriting any group policies.
In earlier versions of App Volumes, there was an option when initially configuring or later reconfiguring App Volumes’ Active Directory integration to “Allow non-domain entities.” This is an option that I always selected in order to have a non-domain joined provisioning machine.
However, now in App Volumes 2.12, that option is no longer available.
I’ve yet to figure out an option to bypass having the provisioning machine on the domain. And there’s no mention of this in the release notes.
😦
TECHNICLOUD 
Hey there Rebecca,
As a member of the EUC Professional Services team at VMware I can say that the wording is confusing. We generally want our provisioning machines to be domain joined when working with App Volumes customers in the field. When we say “clean” machine all we really mean is that it be a fresh and purpose built machine. When provisioning with App Volumes we actually don’t want a ThinApp style machine. We actually want the machine to contain applications that are not going to be App Volumes and any supporting code that won’t be in an App Volume. The best example is to have this be a clone of your VDI base image or clone this machine to be your base image.
LikeLike
Understood, but that still brings the question of why was the option of not domain joining in previous versions and the option is now removed in 2.12? Additionally, why was this change not documented in the 2.12 release notes?
LikeLike
I can’t comment publicly as there isn’t anything public facing but what I can say is, keep an eye on the patch pages.
LikeLike
Will do! Thanks.
LikeLike