No permission to view Security Log in Event Viewer

Captain

Distinguished
Apr 8, 2004
27
0
18,530
Archived from groups: microsoft.public.win2000.security (More info?)

Hello everyone. Been trying to track this down- we recently upgraded to
Exchange 2003 and since, users are not able to view or delete their security
logs in Event Viewer. I am a network admin and have network admin rights and
am unable to view or delete even my own logs. Is there an active directory
policy that enables/disables this behavior?
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.security (More info?)

Do you have Domain admin rights ?
Are the users local administrators of their computers ?

"Captain" <Captain@discussions.microsoft.com> wrote in message
news:21D2C51B-FCF0-4805-91C3-B5F4634CBE27@microsoft.com...
> Hello everyone. Been trying to track this down- we recently upgraded to
> Exchange 2003 and since, users are not able to view or delete their
> security
> logs in Event Viewer. I am a network admin and have network admin rights
> and
> am unable to view or delete even my own logs. Is there an active
> directory
> policy that enables/disables this behavior?
 

Captain

Distinguished
Apr 8, 2004
27
0
18,530
Archived from groups: microsoft.public.win2000.security (More info?)

Yes, I have domain admin rights. Some times it works for everyone and other
times, it doesn't. Yes, the users are local administrators of their
machines, as well. Really strange!

"Richard Hrubizna" wrote:

> Do you have Domain admin rights ?
> Are the users local administrators of their computers ?
>
> "Captain" <Captain@discussions.microsoft.com> wrote in message
> news:21D2C51B-FCF0-4805-91C3-B5F4634CBE27@microsoft.com...
> > Hello everyone. Been trying to track this down- we recently upgraded to
> > Exchange 2003 and since, users are not able to view or delete their
> > security
> > logs in Event Viewer. I am a network admin and have network admin rights
> > and
> > am unable to view or delete even my own logs. Is there an active
> > directory
> > policy that enables/disables this behavior?
>
>
>