Re: disk quotas

Hello Vera, and thanks for your cooperation, you've been so helpful

From what I've seen in the server, the locally cached profile gets created
in c:\docs and settings\%username%, but it doesn't contain the "my documents"
big content of each user, it contains "only" the Favorites, cookies, local
settings, recent documents, USer Data, Start Menu,etc and ntuser.* files. As
soon as the user logs-off this local copy folder is erased.

The "my Documents" folder is redirected to (i.e.) \\tsserver\tsusers , so,
for every user now there's a \\tssserver\tsusers\%username%\My Documents
folder with all their stuff and a \\tsserver\tsusers\%username%\desktop
folder.
Both this folders are successfully redirected as I've stated in the Folder
Redirection Policy parameter to \\tsserver\tsusers. This location
\\tsserver\tsusers is the same one I've set up as "TS User Home directory",
besides that, not withstanding it's a UNC, it actually resides in the F:\
local disk of the tsserver machine, so the redirection is actually taken
place to the same machine, not to a network file server. This situation is
the intended one so everything is almost fine, the issue is that users are
getting about 1 minute delay when logging-on. I hope is not a matter of the
locally cached profile size because I've checked that size already.

Any other suggestion you can have , please?

Thanks a lot!

Alfredo



"Vera Noest [MVP]" wrote:

Yes, it's not a good idea to have the profile and the home
directory in the same folder.
When you logon to the server, a copy of the profile is created on
the system disk of the TS, in C:\Documents and Settings. This
locally cached copy of the profile will in your case also contain
all documents, mp3 files, videos, and whatever the users store in
the home directory. Means you will need a *huge* system disk, and
it will slow down the logon process.

If you separate the profile from the home folder, and keep the
profiles as small as possible (by redirecting My Documenst to the
home directory), you will need much less space on the system drive
and speed up logons.

By the way, Application Data and Desktop are by default stored in
the profile, so you don't have to redirect them separately, if you
want to to be stored in the same place as the profile.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?QWxmcmVkbw==?= <Alfredo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 03 jun 2006 in microsoft.public.windows.terminal_services:

I'm reposting this 'cause it seems that there was an error in
the first try:

I'm very sorry Vera, I don't understand what you mean with:

So you've made their home directory part of their profile?

I've set in my TS Locked down GPO, under Computer
Config/Administrative Templates/Windows Components/Terminal
Services these two parameters:

Set Path for TS Roaming Profiles= \\tsserver\usersdir

TS User Home Directory= \\tsserver\usersdir (exactly the same
place)

Besides that, I've set the Folder Redirection in the GPO under
User Configuration/WindowsSettings/Folder Redirection these
parameters:

Application Data: Basic Redirection to \\tsserver\usersdir
Desktop: Basic Redirecton to \\tsserver\usersdir
My Documents: Basic Redirecton to \\tsserver\usersdir

So basically I've almost everything redirected to the same
location which indeed is a shared folder in the F:\ NTFS
partition on the same TS Machine.

Is this a bad implementation?

I've enabled the Diskquotas on the F:\ drive to 400MB per user
and then the problem with those 9 users appeared....


Thanks for the comprehension and I'm sorry if I'm mislead...
That's not recommended, because it will take up a lot of space
on the system disk of the TS and it will cause delays during
logon. You should create a separate TS profile and a home
directory for each user (both on a shared network drive), and
redirect their "My Documents" folder to their home directory.
That way, only their profile will have to be loaded on to the
TS when they logon, not the whole content of their home
directory (which could contain GBs of Word documents, pdf
files, etc.)

The users that can't logon probably have a home directory /
profile which size exceeds their disk quota limit, and thus
they are refused. That's the whole idea behind disk quotas, but
I would never apply it to user profiles. In fact, I would never
apply it at all, since it's an administrative task that I can
be without, and disk space is cheaper than the costs of
administrating the disk quotas.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?QWxmcmVkcA==?= <Alfredp@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 02 jun 2006 in
microsoft.public.windows.terminal_services:

Hello Vera and thaks for the input, I'm having an strange
behaviour because after I 've enabled disk quotas there are
about 9-10 users which can't logon because of this:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1500
Date: 6/2/2006
Time: 9:44:45 AM
User: INTERBOLSA\jrincon
Computer: TERMINALSRV
Description:
Windows cannot log you on because your profile cannot be
loaded. Check that you are connected to the network, or that
your network is functioning correctly. If this problem
persists, contact your network administrator.

DETAIL - There is not enough space on the disk.

.....However some other users can actually log-in, and their
Home Directory is successfully created in the redirected
folder within the NTFS quota-enabled volume. Disk quota is
the same for everybody.

I don't understand what could be happenning

Thanks



"Vera Noest [MVP]" wrote:

Check if this helps:

816100 - How To Prevent Domain Group Policies from Applying
to Administrator Accounts and Selected Users in Windows
Server 2003 http://support.microsoft.com/?kbid=816100

Have you considered giving the users a home directory on a
fileserver, in stead of on the TS?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?QWxmcmVkbw==?= <Alfredo@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 02 jun 2006:

Hello there

I've enabled disk quotas in my TS Locked down GPO under
Computer Config/Administrative Templates/System/Disk
Quotas in order to limit the amout of information the
users will copy to their home directory. How can I avoid
this disk Quota restiction applies to the Domain Admins
user group?

Thanks


Alfredo

.

Relevant Pages

  • Re: disk quotas
    ... User Configuration/WindowsSettings/Folder Redirection these parameters: ... You should create a separate TS profile and a home directory for ... only their profile will have to be loaded on to the TS ... which size exceeds their disk quota limit, ...
    (microsoft.public.windows.terminal_services)
  • Re: disk quotas
    ... When you logon to the server, a copy of the profile is created on ... I've set the Folder Redirection in the GPO under ... administrating the disk quotas. ...
    (microsoft.public.windows.terminal_services)
  • Re: Question about mapping a shared folder
    ... Folder Redirection because it relies 100% on DNS. ... mandatory profile has listed so as long as I stick with that drive ... I just change my Group Policy and the users home directory path. ...
    (microsoft.public.windows.server.general)
  • Re: Roaming Problems
    ... yes on the original setup profiles and folder ... redirection where both in the same folder ... Did you put your roaming profile directory in the same folder as your ...
    (microsoft.public.windows.server.sbs)
  • Re: Roaming Problems
    ... roaming from the AD and reset each user back to a local profile they still ... and are being complicated by folder ... Change your Folder Redirection policy to "move files to original ... Clear the roaming profile path on each user in AD. ...
    (microsoft.public.windows.server.sbs)