Headaches with Winzip9.0 via GPO
Hello,
I repackaged Winzip9.0 with Wise Installer Editor. We do not want the winzip quickpick to be autoloaded in the system tray so that is removed, as well as desktop shortcut.
Here is the problem. When I try to push 9.0 via Active Directory and a Group Policy, it seems to only be installing the application as an advertisment only. Once the first user logs on, zip files are not actually associated with anything. They have to trip Winzip from the startmenu shortcut to cause a self-heal, and install/register all the missing components.
I am not just talking about HKCU keys needing repair, but initially the Winzip Program files folder only contains 4 chm files. After the shortcut is tripped, then all the dll's and exe's are there.
So one thing I tried was before I did my setup capture in Wise, I changed the setting from "scan advertising info into advertising tables" to "scan to both tables and registry" and then even "leave in registry". But even when there are no advertising options on the packages Components tab, the initiall install still doesn't copy down the exes and dlls and such.
If we leave the quickpick in the systemtray, then the first logon trips this shortcut which repairs winzip properly. Zips are then properly assiciated. But we don't want that quickpick. I tried writing vbscripts to simply cause a repair of the package, but the repair keeps adding this repair script to the runonce key (or startup folder)......... just a continous repair loop then.
I don't know why Winzip, which is installed on virtually every pc in the universe, is giving me so much trouble!!
I am sure I am missing something simple because winzip shouldn't be this tough. How do I get the MSI to install all the files and registry keys initially like every other package I create????
Thanks for your help
I repackaged Winzip9.0 with Wise Installer Editor. We do not want the winzip quickpick to be autoloaded in the system tray so that is removed, as well as desktop shortcut.
Here is the problem. When I try to push 9.0 via Active Directory and a Group Policy, it seems to only be installing the application as an advertisment only. Once the first user logs on, zip files are not actually associated with anything. They have to trip Winzip from the startmenu shortcut to cause a self-heal, and install/register all the missing components.
I am not just talking about HKCU keys needing repair, but initially the Winzip Program files folder only contains 4 chm files. After the shortcut is tripped, then all the dll's and exe's are there.
So one thing I tried was before I did my setup capture in Wise, I changed the setting from "scan advertising info into advertising tables" to "scan to both tables and registry" and then even "leave in registry". But even when there are no advertising options on the packages Components tab, the initiall install still doesn't copy down the exes and dlls and such.
If we leave the quickpick in the systemtray, then the first logon trips this shortcut which repairs winzip properly. Zips are then properly assiciated. But we don't want that quickpick. I tried writing vbscripts to simply cause a repair of the package, but the repair keeps adding this repair script to the runonce key (or startup folder)......... just a continous repair loop then.
I don't know why Winzip, which is installed on virtually every pc in the universe, is giving me so much trouble!!
I am sure I am missing something simple because winzip shouldn't be this tough. How do I get the MSI to install all the files and registry keys initially like every other package I create????
Thanks for your help
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
artiahc_elay
18 years ago
Posted by:
radeon7500
18 years ago
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.