I searched first, but didn't find this topic. However, I think there must be more people with this problem.
I am trying to deploy via GPO, but several of the machines never accept the installation. The logs show error %%1274, and verbiage like this:
"Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %%1274"
"The assignment of application Webroot SecureAnywhere from policy AV Deploy failed. The error was : %%1274"
"The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance."
I've found other forums stating I need to set the policy to "wait for network connections" or set the default wait time to 30 seconds, or 60 seconds, or off and back on, but nothing works. Some of our computers execute the installation fine, and others don't.
Anyone else experience this problem?
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Our DC is Windows Server 2012 R2, clients are all on Windows 10 Pro x64.
What Ifound out is that running the Network ID wizard (or leaving and then re-joining the domain) on the problematic computers helps - once the PC is restarted after joining the domain, it picks up every single GP and the installations of software packages happen.
What's interesting, is that the clients work as normal - e.g., they don't look like computers which lost trustrelationship with the domain or which use cached user's profile.
If anyone out there knows why on Earth computers behave like if they were not communicating properly with the domain, and how to fix it, that would be great :-)
Some of the people are reporting that you have to go higher than 60 seconds, so you could try 90 or 120.
I'll also check in with our support folks and see if they have other suggestions to try.