For the University where I work, I've been creating application objects
via vendor MSI files to distribute to multi-user computers via ZEN. The
apps all install correctly in a "lights-out" configuration - associated
to a workstation, set to "force run," and running in workstation
security space. I'd like to include ZEN icons on the desktop that are
configured to run the executable after object distribution, but the
problem I'm seeing is that they all want to completely reinstall the
application for every new user that logs in, even if the application is
cached on the local system. I can't figure out why this is, except that
perhaps the app object is seeing that all the requisite HKCU registry
entries (from both the vendor MSI and the transform) are missing,
leading to a complete reinstall. Is this a likely cause?

I've been thinking about a few workarounds, and if anyone's got feedback
on these ideas I'd love to hear it.

1.) Create a simple object instead, with a distribution script that
checks the file version of (eg.) C:\Novell\GroupWise\grpwise.exe and
only runs the MSI (command line) if the version isn't right; include all
the HKCU stuff in the registry portion, which will always get pushed.
Would this work in a lights-out scenario?

2.) Create two objects - one MSI object (sans HKCU stuff in transform)
that runs as a dependency of a simple registry object. Would this still
reinstall the MSI every time?

3.) Populate all present HKCU keys at install time. This would be ideal
but I don't know if it's even possible. Seems like it should be, though...

Thanks for your help.