Groupe des Utilisateurs Altiris Suisses et Francophones Group

SUZY1401,

This sounds like it would be better solved with the IEAK (new installs) and Group Policy Preferences (existing installs/enforcement). I wouldn't use activesetup for this at this point.

https://technet.microsoft.com/en-us/ie/bb219517.aspx

https://support.microsoft.com/en-us/kb/2898604

We have a requirement to uncheck two checkboxes of Certification Revocation Check from IE and i did follow the same steps that Eswar mentioned ( As we do not have Wise currently) and created the scripts accordingly.I noticed that the Active setup stub path gets created correctly under the required path of HKLM but it just creates the folder under Installed Components under HKCU but the stubpath does not show up and niether the registry .reg file runs for any logged on user.

Please enlighten me as I am kind of started with packaging and trying the Active setup method for the first time.

Thanks in Advance....

nice post..i proceed the same for packaging an application. after installion proces ,my application has not opening.. wats the cause for this? does the problem is due to registry setting?

http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/2f0ed426-bba1-4b77-834c-5e3056d8403f/

The biggest limitation of using Active Setup for IE registry keys is that Active Setup only runs when the active setup keys in HKCU do not exist, and HKLM does, OR, if the version information in HKCU is less than the version information in HKLM.
In most cases that means that Active Setup will run once for each user, unless the user's profile is flushed or the version number in HKLM is incremented.
This can allow the IT literate user to make later changes to the IE setup and not have them overwritten, as they would be if the settings are implemented by group policy or any other mechanism that refreshes the settings regularly.

If the application contains Advertised Entry Points (ie. Shortcuts or File Extensions), then why don't you just move any component containing HKCU entries (ie. CurrentUser component) into the top level parent feature? Since self healing checks move up to each parent feature up until it reaches the top level parent feature, if the HKCU entries are missing for whichever user tries to use the application, then a self heal is initiated.

But then again, if there are no entry points then by all means, use Active Setup.

What you said is true.

Before optiong for Active Setup, we have to look if there are HKLM entries to do the trick.

I just borrowed the registry entries from Pascal's article.

The process that i described above is used when ever we have requirements like suppressing EULA OR registration OR runonce etc.... [sometimes by adding HKCU entires you can suppress the these screens]. 

Ex: I followed the above process for MapPoint 2009 as i have to add the following registry entries:

[HKEY_CURRENT_USER\Software\Microsoft\MapPoint\16.0\USA]
"EULA"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\MapPoint\16.0\USA]
"Registration"=dword:00000001
 

Anytime your are considering self-healing or activesetup then you must want to make a machine change. So the first thing that should come to mind is "Can this be done with HKLM keys?" The answer for the settings above is yes. There is no need to make a package or use activesetup when a coulple "REG ADD" commands can be used to accomplish this with HKLM. HKLM can't always be used, but the majority of the time it can as in this IE proxy example.

Regardless, nice article on the use of Activesetup.

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MigrateProxy"=dword:00000001
"ProxyEnable"=dword:00000001
"ProxyServer"="192.168.100.200:8080"
"ProxyOverride"="<local>"                                                                                  ------------------------------------------------------------------------ 

If i had to add the above entries to the machine, i make use of active setup registry entries and a simple vbscript: 

1. Compile the above registry entries to a Registry File [Proxy.reg]

2. Write a vbscript to copy the Registry File [Proxy.reg] to a standard location onto the machine.

Note: We always copy "Active Setup" related files to a standard location on the machine before executing them [c:\Program Files\<ORGANIZATION>\ActiveSetup\].

3. Write an Active Setup registry entry to the registry using vbscript like 

'--------------------------------------------------------------------------------------------Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv")

strKeyPath = "SOFTWARE\Microsoft\Active Setup\Installed Components\IE_Proxy"

oReg.CreateKey HKEY_LOCAL_MACHINE,strKeyPath

strValueName = "StubPath"
strValue = "regedit /s c:\Progra~1\<ORGANIZATION>\ActiveSetup\Proxy.reg"
oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName1 = "Version"
dwValue1 = 1
oReg.SetDWORDValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName1,dwValue1
'--------------------------------------------------------------------------------------------

4. Now your vbscript is ready. Create an Altiris software delivery task to execute the vbscript.

Note: Make sure REG file in the source directory

Once altiris executes the vbscipt, the script will copy the REG file to the specified location and add ACTIVE SETUP registry entries. When ever the user/users logs in after reboot, Active Setup registry entry will be executed and HKCU registry entries will be added.

Good luck.

Thanks,

Eshwar

Good article. But I can hardly see some of the embaded pictures. 

I'm waiting for the article on how to do this using SVS....

Good job 

If your Computers are using SVS, and your next CMS level 1 licence maintenance update will include SVS (rename SWV), because of the change in 2009. It will be possible to create a "CURRENT_:USER" registry data layer. You can agregate all "Current user" customizations in a single data layer. More easy to build & maintain & test...