AppDeploy MSI has to remain in same location at all times?
Hey guys- I have been messing with AppDeploy on a clean virtual enviornment to get some MSI's rolling out from EXEs that I would like to push out silently. For instance, I ran Java EXE on my virtual machine, went through all the processes with AppDeploy and had my MSI ready to go. I copied this MSI to a network share and pointed the VBScript to it and installed it. Later that day, I moved the MSI to another location (house cleaning) and upon me moving it, users who had Java installed from that particular AppDeploy MSI were prompted to install it from my network share upon restarting their computer, and since the MSI wasn't there, they were not able to install it.
Is that how the AppDeploy MSI's are supposed to be or is there a way to get an MSI completely installed locally on a machine and not rely on that network share with the MSI?
Community Chosen Answer
The Java EXE extracts an MSI so you would best be advised to use that. Repackaging it will involve a world of pain, not the least of which will be updating it at the next release.