Small issue with my network

[dgcarter]

Ok heres the story, At my school we have a Central Windows 2003 Server where all our client PC's (Running windows XP Professional) connect to it via an NT domain, Now when ever a user logs into a client PC windows creates a folder in Documents & Settings for that user, Now we only have 10 Gig HDD's in the client PC's so now because of this there is not enough free space on the HDD's for windows to function properly, so when our users try to login it takes forever.
So does anyone know how to stop windows fron creating a folder in Documents & Settings each time a user logs on.

Thanks in advance!

 

[killadoob]

get a bigger hdd

 

[dgcarter]

Got a problem with that, my school is short of $$$$$$$$$

 

[macPhallus]

Ok heres the story, At my school we have a Central Windows 2003 Server where all our client PC's (Running windows XP Professional) connect to it via an NT domain, Now when ever a user logs into a client PC windows creates a folder in Documents & Settings for that user, Now we only have 10 Gig HDD's in the client PC's so now because of this there is not enough free space on the HDD's for windows to function properly, so when our users try to login it takes forever.
So does anyone know how to stop windows fron creating a folder in Documents & Settings each time a user logs on.

Thanks in advance!

You can always use the same username or activate the guest account.

If this is legit, and you can provide me with (verifiable) details of your school, I will send your school a new 80GB HD.

Regards

Marcellus

 

[krycor]

can't you set it to autodelete profile on exit or reboot? I used to use a lab where this was done. Either that or set up a image system and just restore it every week or two?

 

[ghalied]

Can't you just group certain users and allow them to log on to certain workstations, say 10 per workstation, profiles certainly doesn't take up that large amount of space. Then delete the profiles of users not needed. Set up a My documents folder redirection to a network share and the 10gig hdd will only have the system, boot and applications installed.

 

[Zwick]

To fix this problem change the user profiles on the nt domain controller to be roaming profiles, that way it creates the user profile directory on the server and maps the user to that folder on logon. the only downside to this is that the login process takes a bit longer.

 

[Arcadies]

There is more than one way to skin this cat, most of the above will work, but the best idea would be to use what Zwick said. my 2c

 

[savage]

You can remove the local profile directories when a user logs out. I believe that would be defined somewhere in the domain policies somewhere. Just have a look - it's there

 

[squirrel]

To fix this problem change the user profiles on the nt domain controller to be roaming profiles, that way it creates the user profile directory on the server and maps the user to that folder on logon. the only downside to this is that the login process takes a bit longer.

This is the way our school does it

 

[ghalied]

Roaming profiles are fine but roaming profiles merge with the local profiles, so a local profile is still in existance.

At the point of logon for a roaming profile, the profile is downloaded to the local comp where the user is logging on, at log off the changes made is uploaded onto the server, but a local copy is still kept on the local comp.

If the server is down, the local profile is used and changes are only uploaded once the user logs back onto the domain.In the end your still stuck with a local profile, best to manage the users and their disk usage with your particular problem, grouping and disk quotas if you want to get really restrictive, but you won't have too worry afterwards.