Anyone have any luck repackaging Meditech? The installation is self-extracting and utlimately produces 10 .exe's, according to ASP exe isolation tool.

I've created an .msi, including the connection information necessary to actually run the program, and it installs and appears to work great- but a local administrator has to run it the first time for it to function properly.

This occurs when deploying through Group Policy or by advertisement via SCCM 2007 with Administrator user rights.

If anyone has any experience- especially success- with this montrosity, I'd appreciate your help!

Nancy
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Seems that you have not enabled some entrypoints to trigger a repair or there is a permission problem when the application is launched for the first time writing stuff under example HKLM registry hive, ProgramFiles or similar.

To find permission problems download Process Monitor and search for "ACCESS DENIED" status. This should tell you what is missing. You could also capture the first-use and find out what the application writes during execution.
Answered 07/16/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD
You could also capture the first-use and find out what the application writes during execution.
This is something I routinely do. Doesn't everyone?
Answered 07/17/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity