Why separate TS profile and NT profile?

G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Hi there,

I noticed in the user properties (win2k3) there are terminal server profile
and NT profile. I'm wondering why Microsoft separates these. Would this make
things messy? Of course not, but why? Could you please explain the benefit
to me?

Thanks!!
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Because users can have very different and conflicting settings in
their local profile and their TS profile.

Imagine that the clients run Windows 98 or NT 4.0 workstation, and
the Terminal Server runs 2003: that will mean that settings in one
profile have no meaning or conflict with settings in the other
profile.

Also: when you log out from a TS session, you save your roaming
profile to disk. If that is the same as your local roaming
profile, you are constently writing over your own settings, and
the local profile will always be the one that is saved last.

Very likely that profiles will become corrupted as well.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"Lei Hu" <leihu@nojunk.com> wrote on 02 nov 2004:

> Hi there,
>
> I noticed in the user properties (win2k3) there are terminal
> server profile and NT profile. I'm wondering why Microsoft
> separates these. Would this make things messy? Of course not,
> but why? Could you please explain the benefit to me?
>
> Thanks!!
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Hi Vera,

Thanks for your kind reply!! Please excuse my ignorance. I don't understand
what you mean when you say: "when you log out from a TS session, you save
your roaming profile to disk." Do you mean a TS session can also have a
roaming profile? I thought TS saves profiles on the TS machine. Explain a
bit to me please!!

Thanks!!

"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message
news:Xns9595ACA5C6987veranoesthemutforsse@207.46.248.16...
> Because users can have very different and conflicting settings in
> their local profile and their TS profile.
>
> Imagine that the clients run Windows 98 or NT 4.0 workstation, and
> the Terminal Server runs 2003: that will mean that settings in one
> profile have no meaning or conflict with settings in the other
> profile.
>
> Also: when you log out from a TS session, you save your roaming
> profile to disk. If that is the same as your local roaming
> profile, you are constently writing over your own settings, and
> the local profile will always be the one that is saved last.
>
> Very likely that profiles will become corrupted as well.
>
> --
> Vera Noest
> MCSE,CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> *----------- Please reply in newsgroup -------------*
>
> "Lei Hu" <leihu@nojunk.com> wrote on 02 nov 2004:
>
>> Hi there,
>>
>> I noticed in the user properties (win2k3) there are terminal
>> server profile and NT profile. I'm wondering why Microsoft
>> separates these. Would this make things messy? Of course not,
>> but why? Could you please explain the benefit to me?
>>
>> Thanks!!
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)

Yes, a TS-profile can be a roaming profile. In fact, that's what
it is supposed to be.

Most companies have not a single Terminal Server, but a couple of
them, in a Load Balanced setup. That means that a user connects to
a different Terminal Server with every connection.
Haveing a local profile on each server would be very confusing.

So my recommendation is: create 2 network shares on a file server,
and call them \profiles and \TSprofiles
Use these shares to store your users roaming profiles.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"Lei Hu" <leihu@nojunk.com> wrote on 03 nov 2004:

> Hi Vera,
>
> Thanks for your kind reply!! Please excuse my ignorance. I don't
> understand what you mean when you say: "when you log out from a
> TS session, you save your roaming profile to disk." Do you mean
> a TS session can also have a roaming profile? I thought TS saves
> profiles on the TS machine. Explain a bit to me please!!
>
> Thanks!!
>
> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9595ACA5C6987veranoesthemutforsse@207.46.248.16...
>> Because users can have very different and conflicting settings
>> in their local profile and their TS profile.
>>
>> Imagine that the clients run Windows 98 or NT 4.0 workstation,
>> and the Terminal Server runs 2003: that will mean that settings
>> in one profile have no meaning or conflict with settings in the
>> other profile.
>>
>> Also: when you log out from a TS session, you save your roaming
>> profile to disk. If that is the same as your local roaming
>> profile, you are constently writing over your own settings, and
>> the local profile will always be the one that is saved last.
>>
>> Very likely that profiles will become corrupted as well.
>>
>> --
>> Vera Noest
>> MCSE,CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> *----------- Please reply in newsgroup -------------*
>>
>> "Lei Hu" <leihu@nojunk.com> wrote on 02 nov 2004:
>>
>>> Hi there,
>>>
>>> I noticed in the user properties (win2k3) there are terminal
>>> server profile and NT profile. I'm wondering why Microsoft
>>> separates these. Would this make things messy? Of course not,
>>> but why? Could you please explain the benefit to me?
>>>
>>> Thanks!!