I'm having an issue with some 'new' vendor supplied InstallShield apps (setup.exe and .msi's)

Package is created and tested with Admin ID- no issues
Load Package as admin, run as user - no issues
Deliver package with LANDesk- no icon, no files, no add/remove. Reports to Landesk as succesful. You can hear it chugging on the local machine but nothing is showing up.

The LanDesk service runs as system. Packages install as 'system'.
If I log into the client machine, stop the service, start the service to log in w/ ANY account that has rights to run as a service, log out, log in as client, installs go just fine.

Some background. Landesk has been in place here for years (patched and current). Hundreds of packages and updates run succesfully all the time. WISE is the packaging tool of choice. This has happened with 5 recent packages GroupWise 7.x vendor supplied is one of them, and four others, various vendors. No changes made to vendor MSI's. Wrappers for the packages have not changed. So I don't believe it is our 'process' as everything else runs as expected. This issue seems to be specifically with LanDesk and InstallShield.

For some reason it is obviously having trouble with the context in which the package is being run. Can stop the service on the fly but because of XP SP2 you can no longer change context when running as system (ie. cant stop the service and 'runas \\domain\anotheruser NET START SOMESERVICE')

Has anyone else had this issue yet? I will be happy to provide additional info if needed.

0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity