RE: [ActiveDir] Group Policy and IE Zone Security

[Darren Mar-Elia]

Title: Message

Yuck (technical term). Dr. Watson isn't a good thing. Loading a Win2K .adm should not cause a Dr. Watson on the MMC. Not sure why you're getting a SQLServerAgent error--that's pretty unrelated to policy. If its possible, you may want to delete this GPO and start from scratch. It sounds like its sufficiently buggered up that starting over may be best.   -----Original Message----- From: Charles Campbell [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 5:51 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Group Policy and IE Zone Security Well, I did a reset with no problems… I tried setting to preference mode, but seem unable to input any changes. I tried adding the *.adm files for IE (inetcorp.adm and inetset.adm), however, when I go to access the settings, I see the following: The inetset.adm file is not for Windows 2000. These settings will not be displayed. I see the same error message for inetcorp.adm.   When trying to access the “Advanced” settings under User Config/IE Maintenance/Advanced, I can see Corporate settings and Internet Settings listed. When I try to access either one of those policies, I get the following 2 errors: Source: DrWatson Event ID: 4097 The application, mmc.exe, generated an application error The error occurred on 08/13/2003 @ 08:41:52.547 The exception generated was c0000005 at address 02324FD8 (<nosymbols>)   And Source: SQLServerAgent Category: Alert Engine Event ID: 318 Unable to read local eventlog (reason: The data area passed to a system call is too small).   I am assuming that I am seeing these errors due to the problem stated above (that the *.adm file isn’t for Windows 2000).   Other than that… I am at a loss as to what is happening. Any ideas? Thanks,   Charles     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Mar-Elia Sent: Tuesday, August 12, 2003 16:08 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Group Policy and IE Zone Security   IE Maintenance has two modes--preference and mandatory. Preference says, "hand down IE policy but then let the user change it" whereas mandatory says, "reinforce it all the time". You can see this by right clicking the IE Maintenance node and choosing either Preference mode or "Reset Browser Settings". You might try a reset--I have seen weirdness around preference mode in the past.