Software Deployment

GPO might be installing files in /qb mode and i think when you are manually testing it you are not using that switch. Some of the features may be getting installed only in UI mode and hence it is getting installed properly.

what I will suggest to install it in UI mode and create a log file. In the log file you find all the features being installed and then you pass these features while you are installing through GPO. you need to pass these features to the Property ADDLOCAL with ; separated...
for example msiexec /i MSIName.MSI TRANSFORMS=MSTName.MST ADDLOCAL=Feature1;Feature2;Feature3

hope this helps...

You can also see if there are conditions set on the features and try to change these if exist so they not only gets installed in UISequence

I have noticed in the MST that the Administrator Option > Install for Profile is set to Determind by user access. Should I change this to Per-Machine install ?

It all depends on how you want to install it, to Per user or machine?
If you install the package through AD/GPO for machine then the ALLUSERS property will be changed to 1.

Per Machine, that how we do the rest of the software.

If I do that all the components have errors. Stuff about key paths and components can not have more then 1 exe or dll in there.

Yeah, we all know about shitty packages vendors do [;)]
I assume you get these errors during validation, which we often don't wan't to resolve from supplied vendor packages if we don't have to.

Have you been able to locate your feature issue and if so does the installation work when distributing the package through AD/GPO? Which application are we talking about?

The application is Crystal Reports 11 for Esri. I am trying to get it working for WinXP it works fine for Win2000. But its XP i need it working on.

Damn thing.

I will try it now, without fixing the validation errors.

If it doesn't help, try get in contact with ESRI.

ESRI Support Center

ORIGINAL: AngelD

If it doesn't help, try get in contact with ESRI.

ESRI Support Center




Been talking to them for the last few days, they havent a clue either. [:(]

Did you find anything in the Condition table?

All like this.

Then you would be interested in the conditions that set the Level to 0 in the Condition table.
If any of these features are lost during installation through AD/GPO, try to remove the condition for it or set the condition to return false.

What happens if the Level is 0 then ?

The feature is set to absent (never install)

So if I make all of them 3 it will install all of it ?

Or you can remove the condition and set the default level in the Feature table

Hmm so far i have tried put all the conditions on level 3 and it still doesnt work.

This thing has two feature, one called "HiddenRoot" which is well hidden and the other is called "CrystalReportsRoot" which has sub feature. I did details on "CrystalReportsRoot" and set the tickbox to "Required Feature" and Level to "Always install this feature".

I then ran the cmd prompt to install it the usual 'msiexec /i <msi> TRANSFORMS=<mst> and it works fine. As soon as I add '/qb' it installs but the shortcut says "Will install on on first use'

Strange and it doing my head in. I dont get it.

There may exist any CA in the InstallExecuteSequence table checking if the UILevel property < 5 (INSTALLUILEVEL_FULL).
Try to find out if the UILevel property is utilized and changing the state of the feature level.

I have found in CA, that there are IF statements saying

If <filename> > 2 then
Execute Program From Destination "[SystemFolder]msiexec.exe" /y "Path"
End

There are loads of these, so if the Level is 3 then they wont install, which is what I want.

All this is in the Execute Deferred area in the MSI Script.

In the All Custom Actions, there are Execute Program From Destination commands.