/build/static/layout/Breadcrumb_cap_w.png

RunOnce and Active Setup

I want to make a setting for Internet Explorer 9 and have a problem to get this setting set. GPO can't be the solution, because the user must be able to change it. So I made an Active Setup. But when I start the IE9 for the first time it overwrites the setting. :/

I have a lot of Package with an Active Setup. But sometimes the Active Setup doesn't work because when I open the Application for the first time, it makes some Settings that overwrites my settings in the Active Setup.

But when I integrate the same settings in an RunOnce it works sporadically.

Can someone explain me, what is the difference between an Active Setup and a RunOnce Key?

I googled a lot about this. But I can't figure out what are the differents.

I saw this: http://apppackaging.wordpress.com/2011/08/28/135/ 

I dont know but if I make a RunOnce does this just work for the next user that log in? And the second one doesnt get the RegSettings? 

I think the best way is to make an advertised shortcut? But as i wrote before the problem is, I want to make a setting, that the user can chance if he don't want this setting. 

My regs I want to add:

Windows Registry Editor Version 5.00

 

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\Cache\Content]

"CacheLimit"=dword:00019000

 

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\International]

"AcceptLanguage"="en-us,de-ch;q=0.8,fr;q=0.5,es;q=0.3"

 

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]

"EnableAutodial"=dword:00000000

"SecureProtocols"=dword:000000a8

 

[HKEY_CURRENT_USER\Software\Microsoft\FTP]

"Use Web Based FTP"="no"

 

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]

"Disable Script Debugger"="yes"

"NoUpdateCheck"=dword:00000001

 

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\PhishingFilter]

"Enabled"=dword:00000001

"ShownVerifyBalloon"=dword:00000001

 

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\MINIE]

"ShowTabsBelowAddressBar"=dword:00000001

"LinksBandEnabled"=dword:00000001

"CommandBarEnabled"=dword:00000001

 

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Control Panel]

"FormSuggest"=dword:00000001

"FormSuggest Passwords"=dword:00000001

 

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\BrowserEmulation]

"LocalMachineCompatibilityMode"=dword:00000000

"IntranetCompatibilityMode"=dword:00000000

"MSCompatibilityMode"=dword:00000000

 

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]

"Use FormSuggest"="yes"

"FormSuggest PW Ask"="no"

"FormSuggest Passwords"="yes"

 

0 Comments   [ + ] Show comments

Answers (1)

Posted by: vjaneczko 10 years ago
9th Degree Black Belt
3

The differences between RO and AS are little.  They can essentially perform the same tasks;run something once per user.  One big difference between them is that AS retains what has been executed in the users regkey, where the RO does not.  So unless your ation is setup to create a log file, you don't have a log file to quickly check if something was executed, and if it failed or not.

The article you cite is failry accurate, although a bit confusing.  RunOnce will work for each user if you use the one in HKCU - it's in both HKCU & HKLM.

For your IE keys, have you looked into the IEAK?

 

 


Comments:
  • First thanks for your help. Yes, I looked into the IEAK but I cant find this settings in the IEAK. I really stuck here... I don't know why it works some times and sometimes not. I can see with regShot that the IE makes some reg change when I start it the first time. Is there a way to start the Internet Explorer in the background with the active setup? Maybe this could help. Or do you have any other ideas? - tecrumors 10 years ago
  • If you are running Vista or higher then RunOnce will not work for a standard user. See http://support.microsoft.com/kb/2021405 - olditguy 10 years ago
  • If you look at the way that an IE installation works, there is an active setup process that executes IE when the user next logs in so that the settings can be finally configured. So make sure your deployment does this also. Then write your active setup to check if there is an active IE session running and if so, put up a message to ask the user to close it. IE can write back registry setttings when it closes, so your settings could be overwritten if IE is running when you make them. Add some logging code to your AS to record the registry key before and after as a diagnostic aid. - EdT 10 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ