Prevent copying roaming profile to local disk of Terminal Server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello !

Is there a way to prevent from copying the entire roaming profile from the
network to local disk of the Terminal Server when user vlogs on.

Or if it's not possible for entire profile is it possible to exclude some
folders that are put on the root of the profile to be copied ?

Thanks.
 
SuderMan said:
Hello !

Is there a way to prevent from copying the entire roaming profile from the
network to local disk of the Terminal Server when user vlogs on.

Or if it's not possible for entire profile is it possible to exclude some
folders that are put on the root of the profile to be copied ?

Thanks.
Click to expand...

Not sure if this addresses your question, but if you have TS you definitely
want to specify a TS profile path in each user's account properties, and
*not* use the default roaming profile path set up for that user.
 
Hello. Thank for reply

Yes I have for each user account a unique path to TS profile like this:

\\server\profiles$\%username%

but when user logs on Terminal Server his profile from
"\\server\profiles$\%username%" is copied to "E:\documents and
settings\%username%" of TS.

I'd like to know if it's possible to prevent from copying the whole profile
or it's part from network to TS.
 
SuderMan said:
Hello. Thank for reply

Yes I have for each user account a unique path to TS profile like this:

\\server\profiles$\%username%

but when user logs on Terminal Server his profile from
"\\server\profiles$\%username%" is copied to "E:\documents and
settings\%username%" of TS.

I'd like to know if it's possible to prevent from copying the whole
profile
or it's part from network to TS.
Click to expand...

Ah. You mean, you don't want to cache the profile on the TS box, then? What
about computer config\admin templates\system\user profiles, and enabling
"Delete cached copies of roaming profiles" ?

I don't know for sure how this works with a TS profile as opposed to a
roaming profile, but I suspect it works....
 
What I wanted to achieve is to prevent copying very big profiles accross the
network. Sometimes profile is very big causing that copying profile across
the other domains in the domain forest last too long.

I was wondering if there is some method not to copy very big profile to
distant Terminal Server or just clearly specify which folders from th profile
not to copy.

I know that this can be partially achieved using slow link detection
policies but only partially.
 
In
SuderMan said:
What I wanted to achieve is to prevent copying very big profiles
accross the network. Sometimes profile is very big causing that
copying profile across the other domains in the domain forest last
too long.

I was wondering if there is some method not to copy very big profile
to distant Terminal Server or just clearly specify which folders from
th profile not to copy.

I know that this can be partially achieved using slow link detection
policies but only partially.
Click to expand...

Not sure if this works with TS profiles, but what about:

User config\admin templates\system\user profiles, "exclude directories in
roaming profile"
and
User config\admin templates\system\user profiles, "limit profile size"

You might also consider using folder redirection policies, and other GPO
settings, to help keep the profile small anyway.
 
"limit profile size" - I don't know how it works exactly but I think it just
warn user when it's profile exceed the specified threshold.

I've tried "exclude directories in roaming profile" policy but it doesn't
works as I wanted for example long time ago I have put Notes data folder in
the root of the profile. Then I wanted to make that this folder stay on the
network share - not to follow with the rest of the profile to TS drive but
what I've noticed is that this folder not only have been copied with the rest
of the profile but also remained on the TS drive and have been removed from
the network profile after logoff. So this just doesn't work for me.

It works fine when I excluded "My documents" folder and redirected using
folder redirection policy to network share. The effect is that "My documents"
stays on the network profile and doesn't follow with profile on TS drive and
that's what I wanted to achieve with the Notes folder. Now I don't know if
it's possible at all.

Thank You.
 
I am having this same issue and am interested in a solution.
I have some users with over 1Gig a profile being copied to the TS.


Thanks in Advance.
 
In
Aneil said:
I am having this same issue and am interested in a solution.
I have some users with over 1Gig a profile being copied to the TS.
Click to expand...

What on earth is *in* a profile of that size? I'd say it would be best to
start with that. Use folder redirection, and train your users!
 
In
SuderMan said:
"limit profile size" - I don't know how it works exactly but I think
it just warn user when it's profile exceed the specified threshold.
Click to expand...

Did you try it?
I've tried "exclude directories in roaming profile" policy but it
doesn't works as I wanted for example long time ago I have put Notes
data folder in the root of the profile. Then I wanted to make that
this folder stay on the network share - not to follow with the rest
of the profile to TS drive but what I've noticed is that this folder
not only have been copied with the rest of the profile but also
remained on the TS drive and have been removed from the network
profile after logoff. So this just doesn't work for me.
Click to expand...

Well, maybe this is OT, but why would you not just make sure all the data
(such as the Notes stuff) is in the user's home directory? I don't want
anything much in the profile folders, myself, except the configuration info.
It works fine when I excluded "My documents" folder and redirected
using folder redirection policy to network share. The effect is that
"My documents" stays on the network profile and doesn't follow with
profile on TS drive and that's what I wanted to achieve with the
Notes folder. Now I don't know if it's possible at all.
Click to expand...

Sounds like you may need to rethink your data storage policies. You should
absolutely redirect My Documents, and perhaps even other folders (desktop,
etc). Your phrasing is a little confusing, though - "my documents" should
point at some place on your file server, such as the user's home
directory....and it really has nothing to do with the profile. Regarding
this Notes folder, why wouldn't you just keep it in the user's "my
documents" once it's redirected to the home directory, then?
 
I am using Roaming Profiles and Folder redirection. I guess SuderMan and I
just might not have things configured as expected.
 
Suderman,
I had the same issue with my users killing the TS with their personal
profile data being copied to the TS (I also use roaming profiles and offline
files) and taking a really long time to login. What I did was create a
basic, locked down profile using a temp user that I created. You can use
some gpo's to lock down the windows interface so it's nice and fast. Search
for a thread regarding using "loopback processing" on your TS server in it's
own OU. This is half the battle. I then copy this profile to a local folder
on the TS server using the username that the user logs in with. Then, modify
the Terminal Server tab in AD to point to the path on the TS that you copied
the profile to (like \\ts\users\%username). When the user logs in they get
exactly what every user gets when they login to the TS - without their my
docs, desktop icons, etc... The template profile is about 1.5mb. There is
probably a better way using a single central profile but I haven't
experiemented with it yet as I am the lone admin amongst 75 users. From my
experience, and through a lot trolling in these newsgroups, loopback
processing is the key to making this work.

Good luck.
 
Back
Top