Hi All,
I'm a Windows 2000 systems administrator at a company that uses Group Policy to deploy it's software. We therefore either Publish (most common) or assign applications to OU's within the AD.
My problem is that increasingly software houses are creating MSI's using Install Shield that are difficult to Publish within AD as they use the setup.exe (ie Install Shield script engine) to set parameters and launch the MSI. My must recent example is Adobe Acrobat 6.0.
Trying to publish the MSI directly always fails ... does anyone know a way to work around this using an .MST or something similar?
Regards
Paul