- Apr 9, 2009
- 7,318
- 4
- 76
Up until now, I've been working in Novell, and recently our school has decided to move to a Windows Server, (2008).
I won't be the person administrating it, but I have been asked to gather some info about how we should set up accounts (group policy, user profiles, etc...). I have a basic question about how Server 2008 handles user profiles, specifically on the user PC's.
From our initial testings we noticed that each account that logs into a computer gets it's own profile on the computer (their own documents and settings folder) built from the default user local account. Because we have labs, this will end up cluttering our workstations with the 2000 students logging into the machines. With Novell this didn't happen, we just had 1 local account and after they logged into the Novell server, they automatically logged into this account. It was clean and easy to manage. Is there a way in Server 2008 to set it up so that each log-in doesn't get their own local profile on the PC?
I've looked at a few options for profile management on server 2008, but I'm not sure what would be the best option for us. Roaming would be too much network overhead and I'd be worried about what happens when student's profiles get corrupted. Mandatory profiles also re-download a new profile each time, I assume also causing a lot of network overhead. Local profiles creates a new profile each time someone logs in, in a lab environment where a ton of kids will be logging in, I'm worried that all of the local profiles will eventually clutter and slowdown the workstation.
Ultimately we are just looking to have accounts log in, have mapped drives, use the default profile on the computer itself, and lock down certain aspects of the computer with the account's associated organizational unit group policy. Anyone have suggestions on how this can be achieved, or how this is done in environments such as labs where multiple people are logging into the same computers?
Thanks.
I won't be the person administrating it, but I have been asked to gather some info about how we should set up accounts (group policy, user profiles, etc...). I have a basic question about how Server 2008 handles user profiles, specifically on the user PC's.
From our initial testings we noticed that each account that logs into a computer gets it's own profile on the computer (their own documents and settings folder) built from the default user local account. Because we have labs, this will end up cluttering our workstations with the 2000 students logging into the machines. With Novell this didn't happen, we just had 1 local account and after they logged into the Novell server, they automatically logged into this account. It was clean and easy to manage. Is there a way in Server 2008 to set it up so that each log-in doesn't get their own local profile on the PC?
I've looked at a few options for profile management on server 2008, but I'm not sure what would be the best option for us. Roaming would be too much network overhead and I'd be worried about what happens when student's profiles get corrupted. Mandatory profiles also re-download a new profile each time, I assume also causing a lot of network overhead. Local profiles creates a new profile each time someone logs in, in a lab environment where a ton of kids will be logging in, I'm worried that all of the local profiles will eventually clutter and slowdown the workstation.
Ultimately we are just looking to have accounts log in, have mapped drives, use the default profile on the computer itself, and lock down certain aspects of the computer with the account's associated organizational unit group policy. Anyone have suggestions on how this can be achieved, or how this is done in environments such as labs where multiple people are logging into the same computers?
Thanks.
