"Error" installing MSI package via GPO - Server 2012 R2
Solved
Jonathrashmetal
Posted messages
12
Status
Membre
-
Jonathrashmetal Posted messages 12 Status Membre -
Jonathrashmetal Posted messages 12 Status Membre -
Hello, I have recently started doing some system administration on Windows 2012 Server (R2)
I would like to deploy an MSI package (7zip or other) via a GPO using "Policy/Software Settings/Software Installation". When I select my package, which is indeed on a network share accessible to everyone, I get a message saying "There is no installation data object in Active Directory", regardless of whether I choose "computer configuration" or "user configuration"... See attached image.
I have searched online and found no information regarding this "error"; has anyone encountered this type of issue before?
When recreating other GPOs, sometimes the package gets through and I can configure deployment modes, etc. However, I still cannot get the package to install at Windows startup (but one thing at a time; for now, I am really interested in finding a clue regarding this "installation data" object)
Thank you, have a good day.
Best regards.
I would like to deploy an MSI package (7zip or other) via a GPO using "Policy/Software Settings/Software Installation". When I select my package, which is indeed on a network share accessible to everyone, I get a message saying "There is no installation data object in Active Directory", regardless of whether I choose "computer configuration" or "user configuration"... See attached image.
I have searched online and found no information regarding this "error"; has anyone encountered this type of issue before?
When recreating other GPOs, sometimes the package gets through and I can configure deployment modes, etc. However, I still cannot get the package to install at Windows startup (but one thing at a time; for now, I am really interested in finding a clue regarding this "installation data" object)
Thank you, have a good day.
Best regards.
2 réponses
Hello,
I would like to add a little comment, especially on best practices.
It is the PDC of the domain in question that allows the modification of the GPOs, not the "first DC of the forest" (and even less a schema or infrastructure master, etc...).
You just pointed out a small issue: replication.
It is precisely by deploying MSI packages via GPOs that you add issues with replication between DCs.
What I recommend is to manage the installation of packages through other means, and absolutely not to use GPOs with MSI for package deployment.
By the way, when you have something other than an MSI, how do you do it?
Use startup scripts on the computers to launch the installations of your software.
Moreover, it's easier to update a script than 50 GPOs...
When we modify the script, we do not need to modify the GPO (and thus we avoid certain work in the directory and AD replication).
Look into installing MSI with MSIEXEC in batch. (or a batch that launches PowerShell/VBS, depending on the client population...)
Furthermore, you also need to review the mastering chain, to implement these software solutions at the base level from the start.
Otherwise, there are products like SCCM or even OCS (or even chocolatey...).
Using a registry "compactor" on top of a registry "cleaner" would be equivalent to rinsing your throat with a swig of Jack Daniels after swallowing a pint of snake oil....
I would like to add a little comment, especially on best practices.
It is the PDC of the domain in question that allows the modification of the GPOs, not the "first DC of the forest" (and even less a schema or infrastructure master, etc...).
You just pointed out a small issue: replication.
It is precisely by deploying MSI packages via GPOs that you add issues with replication between DCs.
What I recommend is to manage the installation of packages through other means, and absolutely not to use GPOs with MSI for package deployment.
By the way, when you have something other than an MSI, how do you do it?
Use startup scripts on the computers to launch the installations of your software.
Moreover, it's easier to update a script than 50 GPOs...
When we modify the script, we do not need to modify the GPO (and thus we avoid certain work in the directory and AD replication).
Look into installing MSI with MSIEXEC in batch. (or a batch that launches PowerShell/VBS, depending on the client population...)
Furthermore, you also need to review the mastering chain, to implement these software solutions at the base level from the start.
Otherwise, there are products like SCCM or even OCS (or even chocolatey...).
Using a registry "compactor" on top of a registry "cleaner" would be equivalent to rinsing your throat with a swig of Jack Daniels after swallowing a pint of snake oil....
Jonathrashmetal
Posted messages
12
Status
Membre
3
Hello Kelux, thank you for this informative clarification!
Well, I finally solved my problem. In fact, the DC on which the GPO was created was the first in the forest (infrastructure and schema master, etc.) and was located geographically several hundred kilometers away from the share where the MSI was (local NAS), so the message in question "installation data object" (which actually represents the package) appeared as long as the package had not been retrieved to Active Directory of this DC (inter-site network speed was pretty poor). I just needed to try 4 times for it to work... And regarding the issue with applying the GPO, it was because of the permissions on the share itself; there were no permissions for domain computers, which is unfortunate since it's a "computer configuration" GPO. Anyway, it's working now :)