I'm seeing some posts about similar issues which suggest that the problem may be related to https://support.microsoft.com/en-us/kb/3000483
Some people are reporting that adding registry keys to reduce the security used to connect to the netlogon and sysvol shares they were able to get policies applying correctly. Those cases weren't directly related to SCCM or OSD though, so I'm not certain it's exactly the same issue. Tomorrow I may try adding those keys to the task sequence just before it joins the domain, if I don't find any more solid info in the mean time. Steve On Tue, Mar 29, 2016 at 5:41 PM, Marable, Mike <[email protected]> wrote: > I too have seen this. I created an elaborate series of scripts that would > run at the completion of a build. The scripts would run a series of > GPUpdates and reboots and it had the same results that you’re seeing. > Sometimes it would work, other times it wouldn’t. > > > > Our Windows 10 deployment plans have been delayed and I’ve been pulled > into other projects so I haven’t been able to work on it. > > > > What frustrated me is that this problem never happened after a Windows 7 > machine was built. We use a single task sequence to build either Windows 7 > or 10. I can build a machine once as Windows 7 and GPOs apply perfectly, > then rebuild that same machine as Windows 10 and the GPOs do not apply. > > > > Mike > > > > > > *From: *<[email protected]> on behalf of Steve Whitcher < > [email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Tuesday, March 29, 2016 at 6:28 PM > *To: *"[email protected]" <[email protected]> > *Subject: *[mssms] Windows 10 clients not getting GPO after successful > OSD TS > > > > When deploying windows 10 to clients using a new task sequence, I'm having > an issue where the task sequence appears to complete successfully, but the > client hasn't applied group policies completely. In the system log are > instances of event 1058 from group policy, saying that it couldn't access > the file. > > > > Sometimes, after waiting a while, or after restarting the client a couple > of times, the issue seems to resolve itself. Other times I've wrestled > with it for a while and never did get the policies to apply. > > > > Has anyone else seen this behavior? What would cause this issue? > > > > ********************************************************** > Electronic Mail is not secure, may not be read every day, and should not > be used for urgent or sensitive issues > >
