User cannot logon on their computers because security log is full

Hi Experts,

Today I faced a weird problem with a client's active directory network. Because of a problem with replication, all sysvol content was deleted. After that all policies stopped to be applied at the computers. This was expected. Unexpected was the fact that no one could log in in their computers because of the following error:

The security log on this system is full

The error appears as a message box before user logon input. Users are not member of local admins, so they can't logon at all.

There is no GPO that enforces Logs configuration at the computers for retention or rotation at all. The only configuration we have in Domain is that Default Domain Policy sets some Audit Policies (sucess an failure for most events).

It's a fact that we are logging a lot of events at computers (much of them I know is useless. we will fix it soon). The Security Logs at the computers might be full or very close to its storage capacity. But we can't have it as the root cause of the problem since when domain policies were fixed, the error message gone away, users can login and security log keeps been filled up.

What is worse is that many users tried to logon this morning at the company's network with their laptops. As they couldn't logon, because of the security log error, they went back home and tried to work through vpn. Unfortunately when they started their laptops, the error message appeared again and didn't let them to log in to the computer.

These outside users came with a problem that we couldn't solve. They don't have local admins rights and we couldn't logon to their computers with our domain admins credentials because they were working from home. If someone asks "why dind't we give local admin's password to these users and instruct them to logon locally and fix the problem? Because we are not allowed to do that. All computers at the domain share the same local admin password. If we give it to one user, we have to change it all over the domain that span 3 different countries.

Anyone has any idea why this problem happened? In other words, If GPO fails to be applied at computer level, the security log issue doesn't let users to login on.


Rodrigo Garcone
Who is Participating?
AcklesConnect With a Mentor Commented:
SandeshdubeySenior Server EngineerCommented:
Use Group Policy to Set Your Application,security and System Log Security in default domain policy.Once this is set the user will not face login issue when the event log gets full on the worksation.

Default Domain policy\Computer Configuration\Windows Settings\Security Settings\Event Log

Policy                                                          Setting
Maximum application log size                 10240 kilobytes
Maximum security log size                     10240 kilobytes
Maximum system log size                       10240 kilobytes
Retention method for application log           As needed
Retention method for security log               As needed
Retention method for system log                As needed

garconerAuthor Commented:

Tks for the reply but this is not the answer for the question. I know this settings you presented and it has been done. The issue is if gpo fail to be applied, even with the settings you suggested configured at gpo level, the security log error occurs
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Since you have problem with sysvol replication, you will have to do it on computers locally.
garconerAuthor Commented:
Hi Ackles,

Tks for the reply. The question is not related on how to configure Security Logs locally or using GPO. I know how to do that.

The question is why when gpo fails to be applied the log is full message appears and block users from log in to their computers.
As you know that GPO get's applied at time scheduel which is either setup as default or specified via GP.
Now there are also Security GPO's which are applied even if there has nothing changed, I mean you are aware that only when there is a change in GPO they get applied, however Security GPO's are always applied even if there is no change. This might be the reason as Audit & other policies fail to apply & in turn fill up the logs.

Does that make sense?

garconerAuthor Commented:
Yes, it makes a lot of sense. That's answer the question. tks!
Glad that helped, Thanks for points!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.