WPHIT
asked on
Event ID 1085 - Internet Explorer Zonemapping failed to execute
Hi All,
We are having some issues with users logging onto our Windows 2003 server domain. We have a list of over 1000 sites in a Group Policy mapped to Internet explorer zones 1 and 2.
On some of our Windows XP Pro Sp3 machines, Event ID 1085 is logged in the Event Viewer stating that The Group Policy Client-side extension Internet Explorer Zonemapping failed to execute.
In the Userenv.log on the client machine, I can see the following entries:
"USERENV(290.888) 13:55:00:513 ProcessGPOs: Processing extension Internet Explorer Zonemapping
USERENV(290.888) 13:55:00:560 ReadStatus: Read Extension's Previous status successfully.
USERENV(290.888) 13:55:00:591 CompareGPOLists: Different entries found.
USERENV(290.888) 13:55:00:638 ProcessGPOList: Entering for extension Internet Explorer Zonemapping
USERENV(290.888) 13:55:00:669 UserPolicyCallback: Setting status UI to Applying Internet Explorer Zonemapping policy...
USERENV(290.888) 13:55:00:732 LogExtSessionStatus: Successfully logged Extension Session data
USERENV(290.888) 13:55:02:450 ProcessGPOList: Extension Internet Explorer Zonemapping returned 0xd.
USERENV(290.888) 13:55:02:497 ProcessGPOList: Extension Internet Explorer Zonemapping doesn't support rsop logging
USERENV(290.888) 13:55:02:529 ProcessGPOs: Extension Internet Explorer Zonemapping ProcessGroupPolicy failed, status 0xd."
I've been through the list of URL's in the zonemapping and there's no invalid characters or misformed URL's.
Any ideas on what's causing this?
Thanks
We are having some issues with users logging onto our Windows 2003 server domain. We have a list of over 1000 sites in a Group Policy mapped to Internet explorer zones 1 and 2.
On some of our Windows XP Pro Sp3 machines, Event ID 1085 is logged in the Event Viewer stating that The Group Policy Client-side extension Internet Explorer Zonemapping failed to execute.
In the Userenv.log on the client machine, I can see the following entries:
"USERENV(290.888) 13:55:00:513 ProcessGPOs: Processing extension Internet Explorer Zonemapping
USERENV(290.888) 13:55:00:560 ReadStatus: Read Extension's Previous status successfully.
USERENV(290.888) 13:55:00:591 CompareGPOLists: Different entries found.
USERENV(290.888) 13:55:00:638 ProcessGPOList: Entering for extension Internet Explorer Zonemapping
USERENV(290.888) 13:55:00:669 UserPolicyCallback: Setting status UI to Applying Internet Explorer Zonemapping policy...
USERENV(290.888) 13:55:00:732 LogExtSessionStatus: Successfully logged Extension Session data
USERENV(290.888) 13:55:02:450 ProcessGPOList: Extension Internet Explorer Zonemapping returned 0xd.
USERENV(290.888) 13:55:02:497 ProcessGPOList: Extension Internet Explorer Zonemapping doesn't support rsop logging
USERENV(290.888) 13:55:02:529 ProcessGPOs: Extension Internet Explorer Zonemapping ProcessGroupPolicy failed, status 0xd."
I've been through the list of URL's in the zonemapping and there's no invalid characters or misformed URL's.
Any ideas on what's causing this?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys, there were a few mis-entered entries in the list that I couldn't spot. The detailed logging and a lot of trial and error has helped, the policy is now working fine again.
Thanks
Thanks
I had this error too, but discovered that in my case the error was adding two letter domain which causes an error both in the security zones in Internet Explorer.
F.x. adding http://*.ab.nu will cause an illegal character or syntax error, but adding http://*.abc.nu will succeed, because it's a three letter domain name, although the syntax and special characters is exactly the same as before. To add to the confusion the error message in IE does not mention this. If you use *.com or *.gov it will work though for a two letter domain name. You can provoke the error also by trying to add it manually in IE.
The cause is that Microsoft does not allow any two letter domain names in top level domain names being added in the IE security zones:
http://support.microsoft.com/kb/259493
F.x. adding http://*.ab.nu will cause an illegal character or syntax error, but adding http://*.abc.nu will succeed, because it's a three letter domain name, although the syntax and special characters is exactly the same as before. To add to the confusion the error message in IE does not mention this. If you use *.com or *.gov it will work though for a two letter domain name. You can provoke the error also by trying to add it manually in IE.
The cause is that Microsoft does not allow any two letter domain names in top level domain names being added in the IE security zones:
http://support.microsoft.com/kb/259493
ASKER
Thanks for your reply.
I've already removed all links that don't follow the standard format in the 1st link, this was done yesterday when the problem first appeared.
Am I best starting again with a new Policy? Is there a way to export/import the list of sites for editing?
Cheers