bilbus Posted October 11, 2006 Report Share Posted October 11, 2006 I just completed pushing out retrospect out to 100 client computers via group policy. Now when users go to install another software package manualy (not related to retospect) the setup fails with a installshield error of 1608. This started after retrospect was installed via GP. I have followed the information about DCOM and registering files but nothing has helped ... i need to get this fixed can anyone help? I installed this package on another computer with retrospect on it and i have the same problem, so its not the computer. Retrospect requires you to install isscript.msi along with the retrospect client. I have to assome that installing ISscript.msi is what caused the problem. thanks Quote Link to comment Share on other sites More sharing options...
bilbus Posted October 12, 2006 Author Report Share Posted October 12, 2006 Well i found out this is because you cant deploy ISScript via group policy. Do not try you will [censored] up every computer. Retrospect support will not help. you need to manualy install Isscript by hand on each pc or use a MSI wrapper to do it via GPO. Thanks retrospect Quote Link to comment Share on other sites More sharing options...
waltr Posted October 12, 2006 Report Share Posted October 12, 2006 although this problem is not limited to Retrospect (thanks Install Shield) it really should be a KB article. there are solutions posted all over the net for handling this yourself, but i've limited this search to those that mention Isscript9: http://www.google.com/search?hl=en&lr=&q="msi+wrapper"+GPO+"isscript9" hope this helps someone in the future and i'd encourage other users who have gone down this road to post solutions as well as comment on how they worked/didn't work. there is a feature request (by scottjwoodford) for this to be automated here: http://forums.dantz.com/ubbthreads/showflat.php/Cat/0/Number/74257/an/0/page/1#Post74257 i encourage anyone with this problem to add a comment to that post. cheers. Quote Link to comment Share on other sites More sharing options...
bilbus Posted April 25, 2007 Author Report Share Posted April 25, 2007 Using Windows Installer Cleanup and remove the deployed Isscript. That will fix the problem Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.