Re: TS profile locations and type...
- From: "Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Jul 2006 02:55:24 -0700
Yes, when you specify a network location as a profile path, then
the profiles become roaming.
The GPO setting is here:
Computer Configuration - Administrative templates - Windows
components - Terminal Services
"Set path for TS roaming profiles"
Note that you should not add %username% here, just something like
\\server\TSprofiles.
Maybe I expressed myself a bit unclear about the advantages of
using a GPO.
No matter where you specify the TS profile path, in AD or a GPO, it
will be applied to all Terminal Servers.
BUT: it's most likely that you need to configure a bunch of other
settings as well, one of which is the "Delete cached copies of
roaming profiles" setting. And that's where the advantage of a GPO
becomes clear.
And think about all other settings: time-out settings, local drive
and audio redirection setting, redirected custom Desktop and Start
Menu, hide the system drive on the TS, etc.
You can configure all this on each TS separately, but even when you
tick all settings off on a checklist and are as accurate as one can
be, sooner or later you'll forget something and the 2 servers
become slightly different. That's where the troubleshooting hell
begins....
One GPO which is linked to the OU which contains your Terminal
Servers will make sure that all settings are applied to all servers
in the OU.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?TXJwdXNo?= <Mrpush@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
27 jul 2006:
Vera,.
Thanks for the info.
You mentioned "TS Roaming profile path" with a GPO. Now you got
me. I quess when I specify TS profiles in a share, they become
"roaming". But I do not see where I can add the path in the
GPO's???
So you are saying set a "TS profiles path" in a GPO so that it
points users to the single TS profile share no matter what TS
they log into. But I does this not happen when you set the TS
path in AD user properties?
Sorry, a bit confused on this issue.
Thanks,
Mark
"Vera Noest [MVP]" wrote:
comments inline
=?Utf-8?B?TXJwdXNo?= <Mrpush@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 27 jul 2006 in microsoft.public.windows.terminal_services:
Hello,
I have 2 TS's on my network to split the connections of upto
50 users.
My question is how to manage PROFILES. My users will logon
to Active Directory and I'd like them to use ROAMING profiles
so they follow them around. I know how to set this in AD by
adding the path.
However, in their Terminal server sessions, I do NOT want
them to have the same profiles as on their workstation they
get from AD. I'd rather they just have a simple clean
profile, possibly even a mandatory one. They need not change
things around, there TS desktops are simply to run our
industry application, really nothing else.
That's a wise decision. Users should never use the same profile
for their TS sessions as for their normal workstation session,
for the reasons you describe, as well as to avoid profile
corruption.
I know when users logon to a TS session, they get the default
on the TS. But then what happens if I add a path in the AD
TS tab for a TS profile? Does it take the AD roaming profile
for the AD users, or do they still get the default TS
profile?
What you specify in the AD account properties, under the
Terminal Services profile path, is just the location where the
TS profiles should be stored.
When users log on to the TS for the first time, they always get
a copy of the Default User profile on the TS as a starting
profile. When they log off, this profile is either stored
locally on the TS (if you didn't specify a TS profile in AD),
or it is stored in the location you specified in AD.
I quess I'll need to keep 2 sets of profiles in 2 separate
shares, one for romaing AD logons and one for TS logins.
Exactly!
Next question, where is the best place to keep my AD profiles
and my TS profiles?
Ideally, on two separate shared folders on a separate
fileserver.
Last question, how do I create a "template" profile for TS
users?
This article should help to modify the Default User profile on
the TS.
305709 - HOW TO: Create a Custom Default User Profile
http://support.microsoft.com/?kbid=305709
Have you considered using a Group Policy to set the TS specific
roaming profile path?
Advantages are that the settings in the GPO apply to both of
your Terminal Servers, so you minimize the risk that the 2
servers have different settings.
What you also might want to configure is this setting (to avoid
that their locally stored copy of the roaming profile fills up
the harddisk of your TS):
Computer Configuration - Administrative Templates - System -
User profiles
"Delete cached copies of roaming profiles"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
- Follow-Ups:
- Re: TS profile locations and type...
- From: Mrpush
- Re: TS profile locations and type...
- References:
- Re: TS profile locations and type...
- From: Vera Noest [MVP]
- Re: TS profile locations and type...
- From: Mrpush
- Re: TS profile locations and type...
- Prev by Date: RE: Client printer mapping - Windows Server 2003 TS
- Next by Date: Drive Mapping issue - Please HELP
- Previous by thread: Re: TS profile locations and type...
- Next by thread: Re: TS profile locations and type...
- Index(es):
Relevant Pages
|