Hope this is the right forum, I did see some redeploy questions here and none in the Group Policy forum so thats why I put my post here:

I have a simple application, assigned to computers via a group policy object. It's a simple MSI.
The only change to the new version of the application is a single exe file. Instead of doing a new MSI-package I thought I could change the exefile from where the group policy gets it's files.

I changed the exe in the administrative installation (Program Files\...\...exe) on my network share and did Redeploy on the package in the group policy. After reboot the machine runs the installation but it seems like it runs it from locally cached MSI. It doesnt install the new exefile. With repair it doesnt either install the new exefile. If I delete the exefile and then click on an advertised shortcut the installation adds the new exefile.

The new exefile has a newer changed date. Should that make that it would run the msi from the share rather than the local msi? How does it work with reploy if I only change files and dont use .msp´s
Thank you in advance
// Jogge
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


One thing to try: open the .msi file with Orca or another table editor, and bump up version number in the File table.
Answered 10/04/2005 by: revizor
Third Degree Blue Belt

Please log in to comment
Yeah, I can do that but...
Shouldn't it work to only change the exefile in the administrative share!? If I change the exefile to another exe (same name ofcourse) but with a newer date and do redeploy on the policy.
I guess the problem is that the exe doesnt have any fileversion but I thought it also would work when the date differ?

// Jogge
Answered 10/04/2005 by: everts
Yellow Belt

Please log in to comment