From this link I understand that my two options are:
- NTFS Quotas
- The "Limit profile size" policy setting
I prefer option (1) because I really want to limit the overall size of everyone's profile so a single user can't fill up the C:/ drive. However, if the quota is reached, I'm concerned I'd be unable to even log in as Administrator remotely to delete files or increase the quota. I don't think I can eg: limit "c:\documents and settings" except for "c:\documents and settings\administrator"
The alternative I can think of is applying an NTFS quota to each user's profile individually when the user is created – more work but at least I have the fine-grained control. This is what I'm currently considering unless you have a better idea?
In response to comments on the answers: this is a standalone TS environment with no other servers and all users use the TS exclusively.
Best Answer
We have found that redirecting as many folders as possible greatly reduces the amount of data that ends up the profile. I would be reluctant to redirect appdata though, you may want to test that.
Personally, I think that a terminal server that will need to support many users needs to have a huge C:\ partition. This is especially true if not redirecting any/many folders. It's also a good idea to have the profiles removed on logoff - assuming that the profiles are roaming and the correct folders are redirected.
Also note that you can re-define where user profiles are stored, so if space is limited on your C:\ partition that may be an option.
User Profiles on Windows Server 2008 R2 Remote Desktop Services
https://blogs.msdn.com/b/rds/archive/2009/06/02/user-profiles-on-windows-server-2008-r2-remote-desktop-services.aspx