N
NoneOfBusiness
First off,I am posting this Win2003 AD question here because i didn't
see a windows2003.group policy group.
We are in the process of setting up a dedicated file server cluster
that we would like to have disk quotas apply to and we like to manage
these quotas via Group Policy, instead of in Quota Manager on the
servers themselves. Ideally, we would like to do it this way to manage
the quotas by groups of users who have different quota requirements
instead of individually within quota manager.
For example, we have two groups, a 50 meg user and a 100 meg user.
When a user reached their quota and we want to give them more space,
we move them to the larger group where the group policy handles the
quota limits.
I know already that this cannot be done via quota manager on the
servers. It is individual users only. We are a site of 3000+ users so
doing it this way would be a management nightmare. Before you ask, we
are currently using novell for file/print services and ADS for Citrix
and our enterprise application user management. We have been tasked
with migrating everything off of Novell. This is to be a key necessity
before we can fully move file services.
But anyway, what i have done already is this for testing.
1) Created a new OU and added a test file server into it.
2) I have blocked inheritence to this OU so that only the group policy
with quotas will be involved.
3) I created a new group of users and added a couple of test domain
users in the group which the policy applies to.
My theory was that by doing this, the policy would only apply to the
server in the OU. I tried it without the users and with the users in
the OU as well and no luck. Disk quotas do not work on the test
server. The only way they will work at all is if i turn on quotas on
the server and manage by user on said machine, which is what i am
trying to avoid anyway. The policies are ineffective.
What am i missing? Has anyone successfully done this and if so, how
did they accomplish it? if i can get it working on this test box, then
porting the policy to a file cluster should not prevent me much of an
issue.
TIA
see a windows2003.group policy group.
We are in the process of setting up a dedicated file server cluster
that we would like to have disk quotas apply to and we like to manage
these quotas via Group Policy, instead of in Quota Manager on the
servers themselves. Ideally, we would like to do it this way to manage
the quotas by groups of users who have different quota requirements
instead of individually within quota manager.
For example, we have two groups, a 50 meg user and a 100 meg user.
When a user reached their quota and we want to give them more space,
we move them to the larger group where the group policy handles the
quota limits.
I know already that this cannot be done via quota manager on the
servers. It is individual users only. We are a site of 3000+ users so
doing it this way would be a management nightmare. Before you ask, we
are currently using novell for file/print services and ADS for Citrix
and our enterprise application user management. We have been tasked
with migrating everything off of Novell. This is to be a key necessity
before we can fully move file services.
But anyway, what i have done already is this for testing.
1) Created a new OU and added a test file server into it.
2) I have blocked inheritence to this OU so that only the group policy
with quotas will be involved.
3) I created a new group of users and added a couple of test domain
users in the group which the policy applies to.
My theory was that by doing this, the policy would only apply to the
server in the OU. I tried it without the users and with the users in
the OU as well and no luck. Disk quotas do not work on the test
server. The only way they will work at all is if i turn on quotas on
the server and manage by user on said machine, which is what i am
trying to avoid anyway. The policies are ineffective.
What am i missing? Has anyone successfully done this and if so, how
did they accomplish it? if i can get it working on this test box, then
porting the policy to a file cluster should not prevent me much of an
issue.
TIA