Software Deployment

Hi Johan,
do i interpret this right? You are trying to install EN via GPO to standard users? If yes, this can't work at all! The ENX.MSI hast the 'ALLUSERS' property set to '1' by default. Therfore, most likely an install without admin rights isn't built in by the vendor. If you explore ENX.msi, you can see several Custom Actions outside the 'Script' (that means, not between 'InstallInitalize + InstallFinalize sequence of the InstallExecuteSequence table).
Read the manual please, there it is a section that explicitly refers to GPO installations. And it mentions only installations to the Computer context.


Are you trying to get the user profile based stuff to each user?

Regards, Nick

Hi Nick,

Yes I am trying to install EN via GPO publishing to the Add/Remove Programs. Why should this be a problem in X, when it was fine in 9.0!!

I've had a look at the install manual, and it says:

"Note: If you are using Group Policy to push SPSS for Windows, the assigned deployment method
is preferred. You can use the published deployment method, but you must push the file named
ISScript*.msi (for example, ISScript1150.msi) before pushing SPSS for Windows. This MSI file
can be found in the SPSS directory on the CD-ROM."

So I installed ISScript1150.msi before hand, and still get the same error.

You said that install without Admin right's isn't built in, but when the User pulls the app from the Add/Remove, aren't they installing it as a SYSTEM user?

At the moment I'm not worrying about the user profile stuff, although that would be nice also.

Many thanks,
Johan

Hi Johan,
now, its getting even more confusing: Are we talking Endnote or SPSS now?
If it's still Endnote: On the EN manual, there is no ref to publishing this SW, as i mentioned in my previous post.

You are right with the standard user getting elevated privileges for installing published or advertised packages under the users context.
BUT: That needs properly authored MSI packages. That especially means, all the things, which change something in the system MUST lie on the MSI script portion of the install.
Unfortunately, this is not the case with this package.
A solution, you can try: Open ENX.msi in ORCA and move all the custom actions after the 'InstallFinalize' sequence in the InstallExecuteSequence in front of it. But this means you have to make them defered (add 1024 to the type of the appropriate CA in the custom action table). But this could, but does not necessarily work, as the author maybe intentionally put this CA's outside of the script.

Hope this clarifies the situation.

Regards, Nick