MSI deployement using GPO - Order of deployment

[mattKnight]

I have 2 GPOs set up to deploy software at machine startup (deployed on computer basis)

These deployments work when only 1 is enabled, but causes issues when both are enabled.

I think this is because one of the MSI's requires a reboot midway through the install - and so the second starts to install before the first is completed (I have many errors with the first insatll being marked as suspended)

Is it possible to force the MSI that requires teh reboot to be installed after the other MSI. My first thought was that I might be able to mark one as being dependant on the other, but GPO doesn't allow this. Likewise I can't see a mechanism for defining an order of deployment.

These 2 bits of software are kind of related (one is TAPI drivers and the other is a Phone system client tool) but some as separate MSI files


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[PU36]

Perhaps you need to write a little script for the second install package to check to see if the 1st install package is installed and if so then install.. if not then reboot and then install.

Also, it is possible to create an msp or mst (custom template) for the installation application that is dependant on the first application?

Is it possible to customize the first install to reboot after installation. It will then reboot when done and then during the next boot, AD will notice that the second application isn't installed and then install that one.

Just throwing out ideas to help get the creative juices flowing.