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?
Answers (3)
Have you updated the vbscript with new location? How are you deploying?
Also, see the sourcelist registry key: http://www.symantec.com/connect/blogs/sourcelist-msi
How to find the compressed product guid? http://www.itninja.com/question/how-to-find-compressedproductcode
Comments:
-
I did not change the VBS location, as I didn't think I would. I thought the MSI was a standalone MSI and didn;t need to remain on the network share in order for it to run.
I am deploying via a VBS in scripting in k1000 . - areiner 11 years ago -
I dont know k1000. but why would it prompt to install again after restart? - SnowLyric 11 years ago
Whenever possible, avoid repackaging. These days developers are pretty good about providing MSIs for their software. You can extract the MSI from the Java offline installer executable. Download the installer from here: http://www.java.com/en/download/manual.jsp
Follow these instructions to get the MSI: http://www.java.com/en/download/help/msi_install.xml