We are in the process of creating an .msp. The one we just created for some reason will not redeploy using Group Policy correctly. I followed these steps to redploy in the AD environment:

1. Apply the patch to the admin location using the following command: msiexec /a <original .msi file and location> /p <.msp file and location>
2. Start the Microsoft Management Console (MMC) Active Directory Users and Computers snap-in (go to Start, Programs, Administrative Tools, and click Active Directory Users and Computers).
3. Right-click the domain, organizational unit (OU), or object that has the policy that contains the deployed software, and select Properties.
4. Select the Group Policy tab.
5. Select the Group Policy Object (GPO) that contains the program you patched and click Edit.
6. Expand the options to access the location at which the software is deployed.
7. Right-click the deployed package and select All Tasks.
8. Click Redeploy Application.
9. Log off client machine and log back on.

When i log back into the client machine the managed software appears to be redeploying. But, when it finishes and i check the files on the client machine, the files are not updated.

I believe i am doing everything correctly on the admin and client machines, am i though??

Or, is there something wrong with the authoring of the msp?? If i run the msi directly from the patched admin in the AD environment i get all updated files fine. So in general the msp looks good, just in the case of redeploy in AD it doesnt seem to really work.

The log files look fine, REINSTALL and REINSTALLMODE seem to be set correctly.

Any help on this would be greatly appreciated.

- Natalie
0 Comments   [ + ] Show 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.


Your redeploy is most likely occurring from the local cached copy of the msi and not the patched copy.

You may have to remove the app from Group Policy and then readd it
Answered 06/17/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
It turned out it was the way i was applying the command line to apply the patch to the domain controller...even though the patch was correctly applied to the domain controller.

Answered 06/23/2004 by: nripsher
Yellow Belt

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