I've changed track with the testing this afternoon and moved the test pools over to Instant Clones rather than LC's - touchwood, it's behaving at the moment. No errors during VM creation, App Volumes behaving itself. Time will tell with a few days of testing though.
I've not implemented any silly workarounds involving disabling the AV service / including batch files.
The concerns I encountered with Instand Clone is the application of the UEM GPO, vmware does not recommend using GPO loopback processing. Did you manage to apply this GPO? and how?
I've not made any changes to the UEM configuration and it does seem to be applying fine on the Instant Clones (we also use Loopback processing: Replace within that policy). UEM has been solid as a rock for quite some time now.
The proof is in the pudding - shall do some more testing and see if anything comes to light over the next few days.
I do not understand my UEM GPO with loopback Proccessing does not work at home, can you help me on this?
What do you have in the scope of this GPO?
Careful with instant clones and computer OU assignments, I have yet to open an SR, but if the cp-template file has an appstack attached, all instant clones will fail to provision. Its because the snapshot relies on a appstack vmdk which is missing. If you specifically limit the attachments to the naming prefix used you are fine, its because the cp-template has an ad object as well but its it113412341234 or something similar.
1 person found this helpful
Like sjesse said. If you assign the appstack to the OU when the template is created and joined to the domain then the appstacks will attach to the template and you get all kinds of issues. You need to also restrict the appstack assignment by name so that it doesn't apply to machines with the name it#########
If you have templates that vSphere can't delete because of this you will need to find the datastore that it is on and delete the folder and then remove from inventory the vm. At least that is what I had to do to delete the vm.