Alright I'm fairly new to this so bare with me. I'm usiing wininstall and trying to make IE settings changes, capture them in a package and deploy that package to multiple machines so they can all have these setttings. I ran discovery on a bare system with just XP on it then made several changes to IE then ran the after snapshot but it did not capture any of the changes to the registry. I tried this several times, rebooted after making the changes but yet wininstall never recognizes the changes to the registry. What am I doing wrong?? Any help would be greatly appreciated.
0 Comments   [ + ] Show Comments

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.

Answers

0
I use a gpo to set IE settings, much easier i guess but thatsin a domain, if your not in a domain then why not use a batch file that startsIE after you change some of the registry settings, us either VB Script, kixtart or just good old .bat file. I had a .bat file that did just that at one of the places i worked (but depends on user permissions).

hope this helps

stevef
Answered 10/28/2005 by: stevef1
Senior Yellow Belt

Please log in to comment
0
I'd go for not using registrysettings but going with security templates on this one, would be easier to manage the thing centrally.. Apply it with secedit upon login with a runonce key.. Stick in the secedit commandline as a custom action in an msi that reboots the PC.. If the user/admin of the standalone machine ever wants to revert to the settings again, trigger a repair of the package and they will apply on reboot.. ;)

Bad solution.. I know.. But all roads lead to Rome!
Answered 11/01/2005 by: mgroover
Senior Yellow Belt

Please log in to comment
0
Hi RIch,

I'd agree with Stevef1 that you should use GPO for this sort of thing, but I'd say the reason why WinInstall is missing it is that it might have an exception or exclusion list that includes IE registry settings.

You can either use Regmon (www.sysinternals.com) to see what keys are being modified (but it produces large log files which can be hard to go through) or use a free snapshot utility to see what reg keys are being changed and either import them into an MSI or manually put them in.

Hope that helps

Rgds

Paul
Answered 11/01/2005 by: plangton
Second Degree Blue Belt

Please log in to comment
0
or use a free snapshot utility to see what reg keys are being changed and either import them into an MSI or manually put them in.

Try regshot it's ideal [;)]

Cheers,
Rob.
Answered 11/01/2005 by: MSIPackager
Third Degree Black Belt

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