J
Jim Raykowski
Guest
Good Morning,
Specs first i guess. We are VMware View Shop with about 5 or 6 base\golden images that we use to launch our linked clone pools. What has been standard practice for us is we update the base\golden image take a snap shot and then recompose the base\golden image which in turn deploys updated linked clone pools. We do have several group policies that once the linked clone computer joins the domain they are not to update at all, we manage that every 4 to 6 weeks.
I am checking this morning and our work group base\golden image are now pulling the group policy that says don't update. Why would this happen? We do have 2016 DC's and use KMS because we still have some Win 7 and S2K8 systems around.
If we use gpedit and set the local policy to update it will be pushed to all linked clones and they will update. How do we find out how this happened and stop it on a work group computer?
TIA,
Jim
More...
Specs first i guess. We are VMware View Shop with about 5 or 6 base\golden images that we use to launch our linked clone pools. What has been standard practice for us is we update the base\golden image take a snap shot and then recompose the base\golden image which in turn deploys updated linked clone pools. We do have several group policies that once the linked clone computer joins the domain they are not to update at all, we manage that every 4 to 6 weeks.
I am checking this morning and our work group base\golden image are now pulling the group policy that says don't update. Why would this happen? We do have 2016 DC's and use KMS because we still have some Win 7 and S2K8 systems around.
If we use gpedit and set the local policy to update it will be pushed to all linked clones and they will update. How do we find out how this happened and stop it on a work group computer?
TIA,
Jim
More...