William here. Remember the story from Tuesday? So was there a disk quota problem or not? Was I just going out on a crazy limb? What do you think?
The answer: No, not crazy. Not really. Disk quotas really were being applied and enforced. The status of “Disk quotas are enabled” proved that and when you add the fact that the disk quota settings were dimmed, this proved the settings were being applied from Group Policy. I told my friend that Disk quotas likely were being enforced on system accounts from Group Policy and those system accounts had exceeded their enforced limits. No way, he says, not possible. Not only possible, I said, but that is what’s happening.
I told him to do me a favor and right-click the system disk, select Properties, click Show Quota Settings on the Quota tab. I asked again if the status read: Disk quotas are enabled. He said yes. I asked again if the quota settings were dimmed (meaning they could not be modified because they were being enforced from Group Policy). He said yes. I told him to click Quota Entries and look for an “Above Limit” warning status for system accounts.
He did. Disk quotas were being enforced on the System, Network Service and Local Service accounts and those accounts had exceeded their enforced limits. I told him there’s your problem but he said the settings couldn’t possibly be coming from Group Policy because neither local policy nor domain policy was enforcing disk quotas. He added and how in the world is this causing our problem?
My answer: Group Policy did at one time, and still is, applying and enforcing disk quotas. The reason? How is this causing the problem? And how is the problem resolved? What do you think?
Write to me with your answers at williamstanek at aol dot com. Or just tune in on Tuesday for the sequel: “Okay, here’s what happened and why tunnel vision isn’t good.”
William R. Stanek
williamstanek at aol dot com
Twitter at williamstanek