Ok,
I've got a problem here with an MSI deployment that I'm working on (using Installshield) we have a program running in the background that needs to run per-user, this needs to start automatically without user intervention.
The problem is with GPO/AD deployment the application is started in the SYSTEM context before anyone is logged in rather than as the user who is about to log in. The application can only run once per user, and it seems that the SYSTEM process prevents the USER process from starting. This means the PCs need to be rebooted twice before the software can be deployed to the users. Any ideas how to stop this?
Basically the current workflow is:
- Installation/upgrade runs... kill background app
- install new files
- Startup background application
this works for Published applications and interactive MSI installations - it's only 'Assigned' applications that seem to have the problem. As step 3 happens in the SYSTEM context rather than the user context :(
Ideally I'd have the development team patch the EXE to prevent launching in the SYSTEM context, but that's a release cycle away and I'm looking for an installer based solution for the interim.
(Edit: I don't know Installscript... so I'm guessing VBscript is probably the way to if there's no native Installshield stuff I can use)