Product Version: 6.0+
Expires on: 365 days from publish date
Updated: Sept 30, 2015
Compatibility View Settings are not restored in IE 10 and 11
1. Create a new Filter in Filter Management. In this filter select the appropriate objects with which to isolate the users or groups you want to fire true for this filter.
a. Make sure in the filter properties to select "Trigger points" as one of the options.
2. Create a new Portability Ruleset in Portability Management.
a. Click on "Portability Management" and click "Create"
b. Write the following settings:
- Hive: HKCU
c. Click Save
d. This key already exists under the IE 9 and IE 9 -6.0 template. You would remove it from that rule in portability management by editing that rule. See Note at end of article.
3. In your primary config edit portability settings.
a. Add Portability Settings Rule
b. Filter: Select your newly created Filter
c. Ruleset: IE-CompatibilityVIew
d. Save Path: Choose your own save path. (ie - where current portability settings are saving).
e. Choose "save" as only option in Actions section
f. UID - This should match exactly the same UID as in you will use in secondary config. This allows both configs to save and restore from the same archive.
4. Create a new "Manual configuration"
a. Click on "Configuration Management" and click "Create"
b. Choose "Manual"
c. In the configuration window choose a name "IE-CompatibilityVIew". Make sure to use the same compression level as your primary configuration. Make sure your legacy mode is the same as your primary configuration. (It is possible to confirm that by opening your primary configuration and going to the "Main" section).
d. Click Save
e. In your newly created configuration, click on "Portability Settings" and click "Add Portability Settings Rule"
-Filter: Select your newly created Filter
-Save Path: Choose your own save path. (ie - where current portability settings are saving).
-Choose "restore" as only option in Actions section
-UID - This should match exactly the same UID as in primary rule in main config
f. In the path where you save your main ini's , ie -\\netlogon\ProfileUnity\ create a sub folder for this secondary ini. Such as "triggers" .
g. Save your new secondary ini to this new save path, ie -\\netlogon\ProfileUnity\Triggers
5. Edit your primary configuration (the one in use).
a. Click on "Trigger point" and add the following values.
- Filter: - Your newly created filter
- Type: Application Open
- Module: Portability Restore
- Application Name: postlogon.exe
Click on the blue tab shown in the red box below.
- INI Path: (specify the location (step g in above section) and the INI file name in this case "IE-CompatibilityVIew.ini")
6. Saving the attached postLogon.exe file.
Save the attached postLogon.exe (strip .renameme) file to a sub-folder on your Netlogon (or any other folder allowing the read permissions for users)
NOTE:As an example you can save to %logonserver%\netlogon\ProfileUnity\Scripts to make sure it executes.
7. Editing a primary INI file
- Create a runonce key (using "Registry" module) and include the executable.
- Action: Write Value
- Hive: HKEY_CURRENT_USER
- Key: Software\Microsoft\Windows\CurrentVersion\RunOnce
- Type: REG_SZ
- Value: Fake
- Data: %systemroot%\system32\cmd.exe /c \\your_domain\netlogon\ProfileUnity\Scripts\postLogon.exe
Save your configuration changes and update your new and the old INI files onto the share.
NOTE: Although not required you might want to remove the following key from your Portability Settings for the IE in the "Portability Manager". That will ensure the compatibility view is not saved in both the primary configuration and the new configuration.