Initiating a repair .
I am a packager , recently has started using GPO.
Due to some repetitive installations, components of one package have got corrupted on few users’s PC and requied to be healed without uninstalling the same.
Usually application recovers their missing files during shortcut invocation under self healing process but this application doesn’t contain any shortcut . Redeploying the application doesn't heal any component.
So, a repair is required to be initiated and I dont find any option to do the same.No options to pass msiexec switches e.g.“msiexec /f [ProductCode]†to repair the package – I wonder there is no option to initiate repair in GPO .
I can neither pass properties like reinstall ,reinstallmode via GPO to initiate reinstall which also seems strange.
Is thee any alternative way where we can recover lost components of the package without uninstall/install again option , we dont want to initiate uninstall due to some concern.
Due to some repetitive installations, components of one package have got corrupted on few users’s PC and requied to be healed without uninstalling the same.
Usually application recovers their missing files during shortcut invocation under self healing process but this application doesn’t contain any shortcut . Redeploying the application doesn't heal any component.
So, a repair is required to be initiated and I dont find any option to do the same.No options to pass msiexec switches e.g.“msiexec /f [ProductCode]†to repair the package – I wonder there is no option to initiate repair in GPO .
I can neither pass properties like reinstall ,reinstallmode via GPO to initiate reinstall which also seems strange.
Is thee any alternative way where we can recover lost components of the package without uninstall/install again option , we dont want to initiate uninstall due to some concern.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Posted by:
deepak_2007
14 years ago
Posted by:
anonymous_9363
14 years ago
Oh wait...I'm sorry, I mis-read. You want to repair. Well, with no advertised entry-points, you are up th eproverbial creek. You will need to uninstall/re-install. What is the "concern" with that? You should be able to test it to death on your test VMs/VPCs before you push it out to users. If it fails in the live environment after extensive testing, it will most likely be due to factors other than the package's uninstallation. Again, logging will show what fails. If, as you say, there are only a few users, the failures shouldn't be too time-consuming. If push comes to shove, you can always rebuild the workstation and let GP deployment do the rest.
Posted by:
deepak_2007
14 years ago
Posted by:
anonymous_9363
14 years ago
For machine-based installs, you'd have to attend the machine (or remote to it) and run the repair/re-install: there's no mechanism in GP to do that. For user-based installs, you'd do the same but you'd have to use the user account which triggered the install, having assigned it appropriate rights to complete the install.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.