For linked clone pool, what will happen is an additional disk will be configured which ends up in driver installation. But for full clone pool this will not happen and that is why there is no error displayed for that. But since the user account does not have local admin privilage should not impact here because all customization that is performed there is using the admin account added in VC Server configuration page of View administrator. Hope that admin account have enough permissions.
Here my doubt is a post configuration of the newly installed hardware (for these VMs it is a new disk) requires permission and this happens when the first user login. You may try any of the following workarounds:
- On the parent VM , add new harddisk, which is similar to a persistent disk and reboot (if you login using user account you should get the same error message) authenticate with credential which has permission to install the driver. Once drivers are installed rmove the disk , shut down and take a snapshot.
- A group policy to provide special permission for the users to ensure the driver installation is not blocked
I am not very sure about the first one. But if that was the case then it could be resolved by an additional reboot after customization which did not happened during pool provisioning. Either the OS image type is demanding an additional reboot, whcih usually does not happen with other image types or that could be bug from product. I would suggest to tryout above two options to know more about it and will encourage calling VMware support.
