This is pretty basic but did you define which MST file to use when you created the package in the group policy (under the modifications tab) ?
I have a strange problem!
We're installing Lotus Notes 7.0.2 MSI package with an MST file.
It works when it's distributed with SMS and it works when I run the installation by hand (using command line options such as "transforms=" and so on)
The problem comes when Notes is installed via GPO.
Program gets installed and everything seems ok, but certain aspects of the program doesn't work.
When I try to run "Modify" on the installation via "Add Remove Programs" I see that almost all the installation-features have been disabled - like I'd never chosen them (which I have, of course)
The features aren't "NOT installed" but they're nok quite there anyway... it's hard to describe properly.
Has anyone got any ideas as to how this is?
Should the GP install do the same as I do when I run "msiexec /i <installationfile> transforms=xxx.mst /qb!" ??
This is pretty basic but did you define which MST file to use when you created the package in the group policy (under the modifications tab) ?
Thank you for the reply!
Yes I did define it, so it shouldn't be the cause of my problems. And even without the MST, the MSI itself would intall several more features than is the case right now.
When I view the msi log it says "Product Registered: Entering Maintenance Mode" which means that WinInstaller believes the product is installed already - but it isn't!
ProductState property gets set to "5" and then everything starts to go wrong from there.
For some reason, when I run the install manually, the log says "Product Not Registered" and then a full install is performed - as it should!