I am trying to package a .msi file with appdeploy and have pretty much made the file. I am able to send it out to other units, but after it installs no .ini files are present. Does anyone know what I may be doing wrong.
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
How are you handling the INI, as a file or via the INIFile table? Does the user have appropriate permissions to write the INI to its target location?
Answered 10/29/2009 by: VBScab
Red Belt

Please log in to comment
0
Also check out if the Target location is properly set for the file...
Answered 10/29/2009 by: jinxngoblins
Senior Yellow Belt

Please log in to comment
0
If the file was created (or somehow introduced to the system) during the snapshot process it should be detected and you should see it when reviewing the detected changes. Note that AppDeploy Repackager handles INI files as files and does not use the INIFile table to handle individual entries at this time.

Note: please don't refer to the AppDeploy Repackager as simply "appdeploy" as that is confusing to most who refer to the entire site as appdeploy
Answered 11/24/2009 by: bkelly
Red Belt

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