The system call to get account information completed. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work. Group Policy dependency (Network Location Awareness) did not start. Log Name: Microsoft-Windows-GroupPolicy/Operational I looked at the Group Policy Event Log and found some more errors:
It would have taken 1 (maybe 2) reboots for the packages to be applied to all the systems.Īm I doing something wrong or is Windows 7 that flaky applying software installation GPOs? Has anyone else found this behaviour?Īs I said in my original posting, 'the "Always wait for the network at computer startup and logon" policy is already applied through another GPO.' Is there a way of checking if the policy has actually applied? The remaining 3 took another 15 reboots after that. Using "gpresult /r" shows all the machines detect that the GPOs apply to them.Īs an example, one morning I started applying GPOs to 20 machines, and it took 3 hours and 20-30 "gpupdate /force /boot" for 17 of them to apply the packages in question. The "Always wait for the network at computer startup and logon" policy is already applied through another GPO (at least it seems so.). Next startup or logon for this user, and this may result in slow startup and boot performance. The system will wait for Group Policy processing to finish completely before the 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 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 : %%2įailed to apply changes to software installation settings. The removal of the assignment of application 7-Zip 4.65 (圆4 edition) (STATS) from policy computer Software (7-Zip 圆4) Installation GPO (2010) failed. The assignment of application 7-Zip 4.65 (圆4 edition) (STATS) from policy computer Software (7-Zip 圆4) Installation GPO (2010) failed. Source: Application Management Group Policy When the application of the packages fails, there are several event errors on the client machine:
In the case of the Windows 7 clients it takes multiple reboots (or gpupdate /force /boot) for the packages to apply to the machines (and at any one time no more than three machines can apply the packages (!?) Windows XP machines will The Windows XP clients apply these packages without problems and at the first reboot/gpupdate but the Windowsħ clients do not. Using the software installation facilities in Group Policy Objects we have several packages pushed onto the Windows XP and Windows 7 clients. We have a domain with Windows 2003 R2 and Windows 2008 R2 DCs (PDC is a Windows 2008 R2 machine), and Windows XP and Windows 7 clients.