OS-based MSI

  • Thread starter Thread starter Henrik Johansson
  • Start date Start date
H

Henrik Johansson

Yesterday we accidentally applied SP1 for WinXP on a Win2k client by using
MSI in a GPO with the result that it failed complaining about bad ntldr when
trying to reboot...
All clients (except of some exlusions) in the office will be replaced with a
new computer with WinXP (OEM) and was by that reason deploying the SP for XP
by using MSI-installing through GPO on the clients.

A solution for the problem would be to restructure the OU:s to insert a
OS-level and place Win2k in one OU and WinXP in another, but it was a little
bit to late at night so we just denied access for the computer which had the
problem and a working partner went to repair the installation.

Just a little thaught: Is there any way to make a OS-version check in the
MSI-deploying so for example servicepacks are only installed on correct
OS-version?
 
Windows Server 2003 brings GPO filtering by using WMI queries. This would be
the best method to apply GPO as you can easily make WMI query to exclude
different type OS versions.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com
 
Yes, you can define minimum system requirements for an MSI to install
(within the MSI).
You can also write a custom action to check the OS of the computer and
CancelInstallation if it does not meet your criteria.

To do this, you will need to edit the MSI using Orca (though I've never used
it), Wise, InstallShield, or some similar product.

\\ MadDHatteR
 
Thanks
After some searching I found where to setup the conditions for system
requirements in Veritas WinInstall.

/Henrik
 
Back
Top