Administrator Profile Size Crisis

[Andie]

I am having problems when updating software on a workstation as an administrator, as this seems to bump up the size of the application data folder on the C drive beyond the limits of my profile and I then can't log off! At the moment I am getting round it by cutting and pasting the relevant folder from app data on the workstation to a share on the network, but heaven only knows what trouble that is causing elsewhere.

 

We have a profile limit set for Authenticated Users (10000Kb) currently in the LNM Domain Policy GPO. I have read somewhere on here that it isn't a good idea to redirect Application Data or I might have had a go at that as a solution. So can someone help, possibly by telling me how to remove administrator users from the current GPO restriction? Or something?

 

We are running Server 2003 and have a mix of XP Prof and Win2000 workstations. Thanks.

[Disease]

Don't set quotas on the Default Domain Policy and setup seperate group policy objects and apply them to ou's thus leaving the Adm,in account with no restrictions?

[mrforgetful]

It depends where your GPO is linked as to who it affects.

 

You shouldn't really change any Default Domain policies and any policies you make to apply to users shouldn't affect the Administrator either.

 

For more information a more detailed description of your AD design would help.

 

Are your users (including administrator) all in one Organisational Unit? Is it the default 'Users' OU?

[FN-GM]

i have a account for doing installs with a mandatory profile

[NetworkGeezer]

Are your users (including administrator) all in one Organisational Unit? Is it the default 'Users' OU?

 

It's the Users container not OU as GPOs can't be applied to containers unless this is something new to Longhorn.

[mrcrazy04]

Just make an OU then, and put the users in that. That's what I did.

The default accounts are still in the users container, everything else is in an OU under a "User Accounts" one.

 

My standard profile is about 30Meg! It takes ages when logging in on the slower machines, so I had to set up a special one just for logging on to other machines!

[Andie]

Thanks for all the suggestions.

 

It depends where your GPO is linked as to who it affects.

 

You shouldn't really change any Default Domain policies and any policies you make to apply to users shouldn't affect the Administrator either.

 

For more information a more detailed description of your AD design would help.

 

Are your users (including administrator) all in one Organisational Unit? Is it the default 'Users' OU?

 

I think I checked this, and it seems to be linked to all the user containers, but I will need to check this out again for sure. We have Teacher and Pupil OUs set up. Come to think of it, not sure where the Administrator fits in on the structure, so I guess I'd better check up on that too. I'm still finding my way with GP and AD, as you've probably realised!!

[mrforgetful]

Are your users (including administrator) all in one Organisational Unit? Is it the default 'Users' OU?

 

It's the Users container not OU as GPOs can't be applied to containers unless this is something new to Longhorn.

 

No, my bad.

[Andie]

It isn't the Default Domain Policy, it's the Domain Policy. It is linked at the top of the tree, to domainname.internal, so I assume that means it applies to the whole domain.

 

Further down, we have user groups (teachers and students) with other GPOs linked to them.

 

Could I take off this particular setting in the Domain Policy, create a separate policy with this setting only and then link it into teachers and students? Or edit the setting into the Teacher and Student policies?

 

Or would that be a stupid thing to do? Is that what @disease is suggesting?

[Andie]

Anybody? I know it is summer hols, but it's good to keep the brain ticking over.....

[plock]

Yes that would work Andie

[Andie]

Thank you!