I ran into this problem whilst trying to lock down Web access on a Metaframe server farm at a high school. It seemed...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
that when we added sites to the restricted list in IE's Content Advisor, the administrator could not access them, however other users could still browse to the sites!
It appears that we hit a bug in IE that, to my knowledge, is as yet unknown at MS. I certainly could not find any references to it on Microsoft's knowledge bases. I did find several other reports, on technical forum sites, from administrators experiencing the same problem -- but no solutions.
I was able to reproduce the problem in a test environment, and have come to the following conclusions:
- This function is definitely set on a per machine basis. No information is written to the users' hive of the registry when changes are made to the accepted sites list.
- The site list information is stored in the registry in the following location:
- Additional sites are added to this structure by copying this, but adding 1 to the numbers above. (e.g. "PRNumPolicy"=dword:0000002...etc.)
- Only users with admin rights can change the values in this content advisor section.
- Once set on a machine, the site listing should take effect for ALL USERS. This is not the case. The setting does take effect for all members of the ADMINISTRATORS group.
- If set by a user without admin rights, the site list will last for an individual session and will block the selected sites, but will not be saved.
- In analyzing the permissions on the PICSRules key, we found that, by default, the following permissions are set: ADMINISTRATORS FULL CONTROL, EVERYONE READ.
- In order for the settings in the Accepted Sites list to take effect for a user, they require 'Full Control' over the Policies registry key. (Note: It may in fact be possible to limit this a little further to 'change' permissions on the PRPolicy key. However, I have not tested this, as it is largely academic.)
Conclusion: Contrary to instructions listed in the relevant MS technical articles, it appears that on an NT based machine, users require the ability to change these keys in order for the site list to be read into Internet Explorer. Note that this allows us to utilize the 'Allowed Sites' feature in a fashion that is not recognized by MS -- on a 'per-user' basis. I haven't checked this on a Windows 2000 box, but would be interested to hear any results.