Reasons for non-working GPO?

Question

Group Policies

Good afternoon.
What reasons / errors / problems did you encounter when you set up the installation of an application (for example, 1C or others) through GPO, especially when it worked on 3 (or more) computers, but does not want to work on others?
Without going into details of errors, etc.
PS I can not understand why 1C is installed in one domain, it is installed on some computers, but not on others.
I feel the solution is somewhere at hand, but I can not find it. Might give you an idea.
Thank you.

Answer 1

1) The policy was not applied to the computer. (# gpupdate force + reboot)
2) The policy was not applied to the user (# gpupdate force + session restart)
3) The second policy is applied to some computers, creating a conflict with the first.
Although I have a similar problem, since MS Visual C ++ Redis is installed with a fresh 1C distribution kit: on some computers it is normally installed, and on some it is requested to elevate the rights to admin. Haven't found the logic yet.

Answer 2

Run rsop.msc on problem computers and see what is written in the errors.
From personal experience: at the initial stage of acquaintance with GPO, I had a problem that computers (usually Windows XP) could not wait for the policies to be applied. Perhaps the network was stupid, perhaps the computer itself (the network interface did not have time to initialize). In both cases, setting the corresponding item in the policy helped (something about waiting for network initialization, I don’t remember exactly now). True, there was a side effect: the computer began to boot a little longer.
In the case of installing software, it would be nice to check the rights of computers on the network share where the installation file is located.