Score:0

Deploying several .msi installers through GPO using startup script

et flag

I need to find a way to deploy several .msi installers through GPO on the n-number of machines.

I found out that deploying them from a single policy is not an option since the order will not be guaranteed.

I found researched some more and found out that it's possible to run a startup script through GPO. The correct order will be ensured by the startup script.

But there is one issue with this approach. Won't the installers be deployed every time machines start? Sure there's a standard check built-in in the installers, but how does it work exactly? Is there any way to set up the GPO not to run if the install has already happened?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.