Re-Activating A Deployed MSI
I'm currently deploying msi package using the Active Directory GPO. I deployed an msi package let me call it msi1 to 1000 users. The deployment is a per machine deployment. The msi1 package is suppose to upgrade a package named msi2 which exist on the desktops. On some desktops, the installation goes on succefully with out any problems, where on some desktops, i receive the below error message
An install for msi2 is currently suspended. You must undo the changes made by that install to continue. Do you want to undo those changes?
I really wasn't able to find any solution for the problem due to that the deployment is done per machine. If any one has the solution for the above, i will really be appreciated.
Another solution which i'm trying to look for, is there a way in which i can delete a registry key related to the Active Directory deployment of msi package and which will cause the msi to get installed again. Cause normally if you delete all the keys which are under installer the deployment of the package doesn't re-activate.
An install for msi2 is currently suspended. You must undo the changes made by that install to continue. Do you want to undo those changes?
I really wasn't able to find any solution for the problem due to that the deployment is done per machine. If any one has the solution for the above, i will really be appreciated.
Another solution which i'm trying to look for, is there a way in which i can delete a registry key related to the Active Directory deployment of msi package and which will cause the msi to get installed again. Cause normally if you delete all the keys which are under installer the deployment of the package doesn't re-activate.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
MSIMaker
19 years ago
Technically you can only have up to 4 msiexec.exe proccesses running before things go pear shaped and bomb out.
Check the users desktop with Task Manager and see how many you have running and kill them all. This will clear the first problem.
Your second problem is to work out why you had them running in the first place.....most likely a defective package.
Check the users desktop with Task Manager and see how many you have running and kill them all. This will clear the first problem.
Your second problem is to work out why you had them running in the first place.....most likely a defective package.
Posted by:
mohd
19 years ago
Regarding the first problem, i cant check it due to that the package is deployed per machine. Even though, not all the PC's give the error. It only happens on some even though they are of the same specifications.
The second one is not actually a problem, but i'm looking for a way on forcing the msi to install itself even if it was installed. I deleted the keys related to a specific msi. The keys were located under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt\
If you delete the key, the msi does install itself, but it takes time until it synchronises. So, i'm not really sure if this is the right keys i'm deleting.
The second one is not actually a problem, but i'm looking for a way on forcing the msi to install itself even if it was installed. I deleted the keys related to a specific msi. The keys were located under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt\
If you delete the key, the msi does install itself, but it takes time until it synchronises. So, i'm not really sure if this is the right keys i'm deleting.
Posted by:
sean_c_roberts
19 years ago
Might the RemoveExistingProducts action, normally found in the Execute Immediate script be the problem?
Is MSI1 trying to remove MSI2 at the same time as MSI1 is being installed?
Also, is there anything you can identify as a difference between the machines on which the deployment was successful and those on which it was not?
Just brainstorming...
Is MSI1 trying to remove MSI2 at the same time as MSI1 is being installed?
Also, is there anything you can identify as a difference between the machines on which the deployment was successful and those on which it was not?
Just brainstorming...
Posted by:
mohd
19 years ago
Sorry guys that i completly forgot about replying back to this topic.
Thanks a lot to all for the info provided.
The problem didn't occur on all machines, some of the machines kept getting this problem.
The package wasn't developed by me, so i didnt understand much on what the package was actually doing. What really happend is that the package starts uninstalling the old msi and for some reason it just fails when started installing the new msi. When scanning the registry, you'll find that the msi is already stamped there as if it is installed, but actually not all the files are installed. So i did the following.
1.Created a wisescript exe file which contains the missing files.
2.Executed the msiexec.exe /FAMSU Product Code to force self repair the package.
The exe had to be executed manually on the pc's which had the problem.
Thanks a lot to all for the info provided.
The problem didn't occur on all machines, some of the machines kept getting this problem.
The package wasn't developed by me, so i didnt understand much on what the package was actually doing. What really happend is that the package starts uninstalling the old msi and for some reason it just fails when started installing the new msi. When scanning the registry, you'll find that the msi is already stamped there as if it is installed, but actually not all the files are installed. So i did the following.
1.Created a wisescript exe file which contains the missing files.
2.Executed the msiexec.exe /FAMSU Product Code to force self repair the package.
The exe had to be executed manually on the pc's which had the problem.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.