/build/static/layout/Breadcrumb_cap_w.png

MST/MSI Distribution

Hi All!
I am new to MSI Development. I am working on an MSI which works fine when it was executed using MSIEXEC command on a virtual machine. Now when I gave this MSI to the department who are responsible to distribute it via GPO and asked them to ditribute this MSI to a test machine using GPO, they did that but the MSI is not working in the same way as it did on the virtual machine. For example, when the MSI was executed using MSIEXEC on the virtual machine, it created a folder called ApplData (when the folder is already present, the installation over writes it) under C Drive and also it created some registry entries with the required permissions to the user. And when I go to Add/Remove programs on this virtual machine and remove the program I have installed through MSI, then the folder that was created under C Drive was removed and the same happened with the registry values it created. But on the test machine, when the same MSI was distributed through GPO, it is not over writing the folder under C Drive and also the appropriate permissions are not getting granted to the registry entries and because of this the operation of the program is getting failed.

Can any one please let me know what I have to do in this issue?
I would appreciate their help, very much.

Regards,
Satish

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ