Not sure if this will help but i had this problem and decided to do the following which worked.
Its possible that some machines are failing to find the SRV Record of the KMS server.
To avoid this you can manually specify the KMS Server. on your Maser Template
Manually Specifying a KMS Host
Administrators can manually assign a KMS host to KMS clients by using KMS host caching. Manually assigning a KMS host disables auto-discovery of KMS on the KMS client. A KMS host is manually assigned to a KMS client by running:
slmgr.vbs /skms <value>:<port>
so en example will be slmgr.vbs /skms <gb-contoso-01.corp.local>:<1688>
hope it helps
Thanks for the reply. I might give this a try. I though if a VM could not contact KMS during Sysprep there would be a provisioning error in View. I may be mistaken.