Problems with software distribution through group policies - how to solve?

Question

Active Directory

There is a fleet of computers in the Active Directory domain up to 100 machines (stationary PCs and laptops). Operating systems - Windows 7, 8.1 and 10. Domain controller on Windows Server 2012 R2. I distribute the software in the form of MSI packages through group policies (Software configuration -> Software installation). In most cases, everything works well. But from time to time the following problem occurs on a random computer / laptop:
1. The loading of the operating system lasts half an hour or an hour, at this time it says "Please wait" on the screen;
2. If the download is not interrupted, then we do not see any errors in the log, all packages are installed / updated;
3. If the download is interrupted by turning it off / on, then the operating system will load quickly, but in the log we will see an error like:

Product: Google Update Helper -- Error 1704. An installation for 1C:Enterprise 8 (8.3.9.2309) is currently suspended. You must undo the changes made by that installation to continue. Do you want to undo those changes?

In this case, instead of Google Update Helper, there may be Adobe Acrobat Reader, and instead of 1C: Enterprise - Viber. That is, the problem is not with one product, but with different ones.
The local network works stably, the problem occurs both over the wire and through Wi-Fi. The operating system also does not matter: it is buggy on both 8-ke and 10-ke.
Has anyone encountered such a problem?
Will deploying SCCM solve the problem?

Answer 1

It seems that the problem was in the buggy viber msi package. The fact is that it is installed by default in the user profile folder, and in order to direct it to Program Files, I had to use a modification (transforms.mst), where I specified the desired installation path. And either because of this, or for another reason, but the viber installation hung at the very end of the process and caused the problems described above. I had to manually cut out this installation by running an arbitrary msi package and clicking "yes" in response to the offer to roll back the previous installation.
As for 1C: Enterprise 8, this was an isolated case: maybe the Internet connection fell off, or maybe the user turned off the laptop without waiting for the installation to finish.
The moral of this fable is this: do not distribute dubious msi packages in the enterprise (the viber msi package is dubious not only because of the screwed transforms.mst, but also because the link to it has not been published anywhere - I accidentally "caught" it by changing file extension in a regular link to an .exe file).

Answer 2

Have you tried google?
This means that someone installed something - which requested a reboot of the computer - and when the installation of something is not yet complete - when applying the policies, the following package is installed.

spoiler

https://www.google.com/search?q=Error+1704.+An+ins...