VMware Horizon Community
rooster147
Contributor
Contributor

Group Policy processing on new machines

Has anybody else ran into issues with Group policy applying to machines that have been freshly provisioned? I have VM's that roll off the line but grab the appropriate policy. Doing a GP result on the Virtual desktop shows an error complaining about time synchronization but, the system clock is correct and using the w32tm command I have the appropriate time server and time. I checked and make sure that the vm isn't trying to sync time with the host and that was set appropriately. The only thing that seems rather strange is when you do a gp result on the machine it lists domain\machinename with "machine name" being the parrent VM not the linked clone. If manually force a GP update it fixes this but no matter how many times I reboot the VM it doesn't pick up what it should. Anybody else come across this?

Reply
0 Kudos
1 Reply
Gaurav_Baghla
VMware Employee
VMware Employee

1)please check for If the machines are actually getting Customized as you said it is taking the parent machine name and not the linked clone name seems to be a customization problem.

2)VMware KB: Timekeeping best practices for Windows, including NTP

Regards Gaurav Baghla Opinions are my own and not the views of my employer. https://twitter.com/garry_14
Reply
0 Kudos