TS Profiles

[Cary Shultz]

Good morning!

Okay, Okay......I know that several of you in here will kill me for this!
Vera, Patrick, Jeff,.....sorry...but I did not do this!!!! I am simply
trying to fix some things and want to make sure that I do not break things
in the process....

Anyway, a client has a small Terminal Server farm (two servers). A Terminal
Server Profile was not implemented. Yikes! I know!

Anyway, most are using a Thin Client but some still use a PC / Laptop to
access the Terminal Server. Some of the of these good people are Sales
Folks who are almost never in the office and log on to their laptops locally
(read: the "log on to:" part is populated with "mymachine (this computer)").

Anyway, I really would like to set this up properly. Is it a bad idea -
after the fact - to implement TS Profiles?

My Documents and Desktop are already being re-directed via Group Policy and
the Terminal Servers are locked down via GPO - Loopback Policy.

I even have the PROFILE$ folder created for this....the person behind me did
not do that part of his tasks -AND- I did not check to make sure that things
were done...so, ultimately, my bad!

Thanks,

Cary

 

[Vera Noest [MVP]]

Re: TS Profiles

No, you can still do this.
Since the users logon to their laptops with a local account, they
will already have different profiles for their laptops and the TS.
Their current TS profiles will be stored on the Terminal Servers.
When you define a TS profile path with a GPO, next time they logon
they will still get their local TS profile (because the TS roaming
profile folder is still empty), and when they logoff, their TS
profile will be saved in the roaming TS profile path.

Only problem with this is that they will have different profiles on
the 2 Terminal Servers. So one of those will be lost in this
scenario. I'd make a copy of all local TS profiles befor
implementing this, so that you can manually try to merge some
settings if needed.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 25 okt
2008 in microsoft.public.windows.terminal_services:

> Good morning!
>
> Okay, Okay......I know that several of you in here will kill me
> for this! Vera, Patrick, Jeff,.....sorry...but I did not do
> this!!!! I am simply trying to fix some things and want to make
> sure that I do not break things in the process....
>
> Anyway, a client has a small Terminal Server farm (two servers).
> A Terminal Server Profile was not implemented. Yikes! I know!
>
> Anyway, most are using a Thin Client but some still use a PC /
> Laptop to access the Terminal Server. Some of the of these good
> people are Sales Folks who are almost never in the office and
> log on to their laptops locally (read: the "log on to:" part is
> populated with "mymachine (this computer)").
>
> Anyway, I really would like to set this up properly. Is it a
> bad idea - after the fact - to implement TS Profiles?
>
> My Documents and Desktop are already being re-directed via Group
> Policy and the Terminal Servers are locked down via GPO -
> Loopback Policy.
>
> I even have the PROFILE$ folder created for this....the person
> behind me did not do that part of his tasks -AND- I did not
> check to make sure that things were done...so, ultimately, my
> bad!
>
> Thanks,
>
> Cary

 

[Cary Shultz]

Re: TS Profiles

Vera,

Quick question: I tested this out on the Production server but with two
test accounts and via the ADUC (when I do this for real it will be via GPO).

Question: it looks like only that specific user has access to the
\\FS1\TSPROFILES$\testts folder. I can probably change this by taking
ownership of it and modifying permissions on it. However.....

Is it possible that I simply precreate the folders inside that
\\FS1\TSPROFILES$ folder? I would guess that I could and have the folders
inheirit the permissions set on the TSPROFILES folder?

Is this worth doing?

Thanks,

Cary
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9B42E48ADA14Averanoesthemutforsse@207.46.248.16...
> No, you can still do this.
> Since the users logon to their laptops with a local account, they
> will already have different profiles for their laptops and the TS.
> Their current TS profiles will be stored on the Terminal Servers.
> When you define a TS profile path with a GPO, next time they logon
> they will still get their local TS profile (because the TS roaming
> profile folder is still empty), and when they logoff, their TS
> profile will be saved in the roaming TS profile path.
>
> Only problem with this is that they will have different profiles on
> the 2 Terminal Servers. So one of those will be lost in this
> scenario. I'd make a copy of all local TS profiles befor
> implementing this, so that you can manually try to merge some
> settings if needed.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 25 okt
> 2008 in microsoft.public.windows.terminal_services:
>
>> Good morning!
>>
>> Okay, Okay......I know that several of you in here will kill me
>> for this! Vera, Patrick, Jeff,.....sorry...but I did not do
>> this!!!! I am simply trying to fix some things and want to make
>> sure that I do not break things in the process....
>>
>> Anyway, a client has a small Terminal Server farm (two servers).
>> A Terminal Server Profile was not implemented. Yikes! I know!
>>
>> Anyway, most are using a Thin Client but some still use a PC /
>> Laptop to access the Terminal Server. Some of the of these good
>> people are Sales Folks who are almost never in the office and
>> log on to their laptops locally (read: the "log on to:" part is
>> populated with "mymachine (this computer)").
>>
>> Anyway, I really would like to set this up properly. Is it a
>> bad idea - after the fact - to implement TS Profiles?
>>
>> My Documents and Desktop are already being re-directed via Group
>> Policy and the Terminal Servers are locked down via GPO -
>> Loopback Policy.
>>
>> I even have the PROFILE$ folder created for this....the person
>> behind me did not do that part of his tasks -AND- I did not
>> check to make sure that things were done...so, ultimately, my
>> bad!
>>
>> Thanks,
>>
>> Cary

 

[Vera Noest [MVP]]

Re: TS Profiles

There's a GPO setting for this as well:

Computer Configuration - Administrative templates - System - User
profiles
"Add the Administrators security group to roaming user profiles"

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

"Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26 okt
2008 in microsoft.public.windows.terminal_services:

> Vera,
>
> Quick question: I tested this out on the Production server but
> with two test accounts and via the ADUC (when I do this for real
> it will be via GPO).
>
> Question: it looks like only that specific user has access to
> the \\FS1\TSPROFILES$\testts folder. I can probably change this
> by taking ownership of it and modifying permissions on it.
> However.....
>
> Is it possible that I simply precreate the folders inside that
> \\FS1\TSPROFILES$ folder? I would guess that I could and have
> the folders inheirit the permissions set on the TSPROFILES
> folder?
>
> Is this worth doing?
>
> Thanks,
>
> Cary
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9B42E48ADA14Averanoesthemutforsse@207.46.248.16...
>> No, you can still do this.
>> Since the users logon to their laptops with a local account,
>> they will already have different profiles for their laptops and
>> the TS. Their current TS profiles will be stored on the
>> Terminal Servers. When you define a TS profile path with a GPO,
>> next time they logon they will still get their local TS profile
>> (because the TS roaming profile folder is still empty), and
>> when they logoff, their TS profile will be saved in the roaming
>> TS profile path.
>>
>> Only problem with this is that they will have different
>> profiles on the 2 Terminal Servers. So one of those will be
>> lost in this scenario. I'd make a copy of all local TS profiles
>> befor implementing this, so that you can manually try to merge
>> some settings if needed.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 25
>> okt 2008 in microsoft.public.windows.terminal_services:
>>
>>> Good morning!
>>>
>>> Okay, Okay......I know that several of you in here will kill
>>> me for this! Vera, Patrick, Jeff,.....sorry...but I did not do
>>> this!!!! I am simply trying to fix some things and want to
>>> make sure that I do not break things in the process....
>>>
>>> Anyway, a client has a small Terminal Server farm (two
>>> servers).
>>> A Terminal Server Profile was not implemented. Yikes! I
>>> know!
>>>
>>> Anyway, most are using a Thin Client but some still use a PC /
>>> Laptop to access the Terminal Server. Some of the of these
>>> good people are Sales Folks who are almost never in the office
>>> and log on to their laptops locally (read: the "log on to:"
>>> part is populated with "mymachine (this computer)").
>>>
>>> Anyway, I really would like to set this up properly. Is it a
>>> bad idea - after the fact - to implement TS Profiles?
>>>
>>> My Documents and Desktop are already being re-directed via
>>> Group Policy and the Terminal Servers are locked down via GPO
>>> - Loopback Policy.
>>>
>>> I even have the PROFILE$ folder created for this....the person
>>> behind me did not do that part of his tasks -AND- I did not
>>> check to make sure that things were done...so, ultimately, my
>>> bad!
>>>
>>> Thanks,
>>>
>>> Cary

 

[Cary Shultz]

Re: TS Profiles

Geez! Okay....Rookie mistake. I did not look at the settings and, like I
said, was just testing. Next time I will look before asking!

Thanks, Vera. That was a waste of time......well, maybe not. For the lazy
(like me...in this case) here is the answer.

Thanks again,

Cary

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9B4384AF8B4CFveranoesthemutforsse@207.46.248.16...
> There's a GPO setting for this as well:
>
> Computer Configuration - Administrative templates - System - User
> profiles
> "Add the Administrators security group to roaming user profiles"
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26 okt
> 2008 in microsoft.public.windows.terminal_services:
>
>> Vera,
>>
>> Quick question: I tested this out on the Production server but
>> with two test accounts and via the ADUC (when I do this for real
>> it will be via GPO).
>>
>> Question: it looks like only that specific user has access to
>> the \\FS1\TSPROFILES$\testts folder. I can probably change this
>> by taking ownership of it and modifying permissions on it.
>> However.....
>>
>> Is it possible that I simply precreate the folders inside that
>> \\FS1\TSPROFILES$ folder? I would guess that I could and have
>> the folders inheirit the permissions set on the TSPROFILES
>> folder?
>>
>> Is this worth doing?
>>
>> Thanks,
>>
>> Cary
>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
>> in message
>> news:Xns9B42E48ADA14Averanoesthemutforsse@207.46.248.16...
>>> No, you can still do this.
>>> Since the users logon to their laptops with a local account,
>>> they will already have different profiles for their laptops and
>>> the TS. Their current TS profiles will be stored on the
>>> Terminal Servers. When you define a TS profile path with a GPO,
>>> next time they logon they will still get their local TS profile
>>> (because the TS roaming profile folder is still empty), and
>>> when they logoff, their TS profile will be saved in the roaming
>>> TS profile path.
>>>
>>> Only problem with this is that they will have different
>>> profiles on the 2 Terminal Servers. So one of those will be
>>> lost in this scenario. I'd make a copy of all local TS profiles
>>> befor implementing this, so that you can manually try to merge
>>> some settings if needed.
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 25
>>> okt 2008 in microsoft.public.windows.terminal_services:
>>>
>>>> Good morning!
>>>>
>>>> Okay, Okay......I know that several of you in here will kill
>>>> me for this! Vera, Patrick, Jeff,.....sorry...but I did not do
>>>> this!!!! I am simply trying to fix some things and want to
>>>> make sure that I do not break things in the process....
>>>>
>>>> Anyway, a client has a small Terminal Server farm (two
>>>> servers).
>>>> A Terminal Server Profile was not implemented. Yikes! I
>>>> know!
>>>>
>>>> Anyway, most are using a Thin Client but some still use a PC /
>>>> Laptop to access the Terminal Server. Some of the of these
>>>> good people are Sales Folks who are almost never in the office
>>>> and log on to their laptops locally (read: the "log on to:"
>>>> part is populated with "mymachine (this computer)").
>>>>
>>>> Anyway, I really would like to set this up properly. Is it a
>>>> bad idea - after the fact - to implement TS Profiles?
>>>>
>>>> My Documents and Desktop are already being re-directed via
>>>> Group Policy and the Terminal Servers are locked down via GPO
>>>> - Loopback Policy.
>>>>
>>>> I even have the PROFILE$ folder created for this....the person
>>>> behind me did not do that part of his tasks -AND- I did not
>>>> check to make sure that things were done...so, ultimately, my
>>>> bad!
>>>>
>>>> Thanks,
>>>>
>>>> Cary

 

[Vera Noest [MVP]]

Re: TS Profiles

No problem, Cary, I'm glad I could help.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26 okt
2008 in microsoft.public.windows.terminal_services:

> Geez! Okay....Rookie mistake. I did not look at the settings
> and, like I said, was just testing. Next time I will look
> before asking!
>
> Thanks, Vera. That was a waste of time......well, maybe not.
> For the lazy (like me...in this case) here is the answer.
>
> Thanks again,
>
> Cary
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9B4384AF8B4CFveranoesthemutforsse@207.46.248.16...
>> There's a GPO setting for this as well:
>>
>> Computer Configuration - Administrative templates - System -
>> User profiles
>> "Add the Administrators security group to roaming user
>> profiles"
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26
>> okt 2008 in microsoft.public.windows.terminal_services:
>>
>>> Vera,
>>>
>>> Quick question: I tested this out on the Production server
>>> but with two test accounts and via the ADUC (when I do this
>>> for real it will be via GPO).
>>>
>>> Question: it looks like only that specific user has access to
>>> the \\FS1\TSPROFILES$\testts folder. I can probably change
>>> this by taking ownership of it and modifying permissions on
>>> it. However.....
>>>
>>> Is it possible that I simply precreate the folders inside that
>>> \\FS1\TSPROFILES$ folder? I would guess that I could and have
>>> the folders inheirit the permissions set on the TSPROFILES
>>> folder?
>>>
>>> Is this worth doing?
>>>
>>> Thanks,
>>>
>>> Cary
>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>> wrote in message
>>> news:Xns9B42E48ADA14Averanoesthemutforsse@207.46.248.16...
>>>> No, you can still do this.
>>>> Since the users logon to their laptops with a local account,
>>>> they will already have different profiles for their laptops
>>>> and the TS. Their current TS profiles will be stored on the
>>>> Terminal Servers. When you define a TS profile path with a
>>>> GPO, next time they logon they will still get their local TS
>>>> profile (because the TS roaming profile folder is still
>>>> empty), and when they logoff, their TS profile will be saved
>>>> in the roaming TS profile path.
>>>>
>>>> Only problem with this is that they will have different
>>>> profiles on the 2 Terminal Servers. So one of those will be
>>>> lost in this scenario. I'd make a copy of all local TS
>>>> profiles befor implementing this, so that you can manually
>>>> try to merge some settings if needed.
>>>> _________________________________________________________
>>>> Vera Noest
>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>> TS troubleshooting: http://ts.veranoest.net
>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>
>>>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on
>>>> 25 okt 2008 in microsoft.public.windows.terminal_services:
>>>>
>>>>> Good morning!
>>>>>
>>>>> Okay, Okay......I know that several of you in here will kill
>>>>> me for this! Vera, Patrick, Jeff,.....sorry...but I did not
>>>>> do this!!!! I am simply trying to fix some things and want
>>>>> to make sure that I do not break things in the process....
>>>>>
>>>>> Anyway, a client has a small Terminal Server farm (two
>>>>> servers).
>>>>> A Terminal Server Profile was not implemented. Yikes! I
>>>>> know!
>>>>>
>>>>> Anyway, most are using a Thin Client but some still use a PC
>>>>> / Laptop to access the Terminal Server. Some of the of
>>>>> these good people are Sales Folks who are almost never in
>>>>> the office and log on to their laptops locally (read: the
>>>>> "log on to:" part is populated with "mymachine (this
>>>>> computer)").
>>>>>
>>>>> Anyway, I really would like to set this up properly. Is it
>>>>> a bad idea - after the fact - to implement TS Profiles?
>>>>>
>>>>> My Documents and Desktop are already being re-directed via
>>>>> Group Policy and the Terminal Servers are locked down via
>>>>> GPO - Loopback Policy.
>>>>>
>>>>> I even have the PROFILE$ folder created for this....the
>>>>> person behind me did not do that part of his tasks -AND- I
>>>>> did not check to make sure that things were done...so,
>>>>> ultimately, my bad!
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cary

 

[David G. Hoch]

Re: TS Profiles

Reading through this post was very interesting (thanks for the good
information), but it did bring up a question that I'm hoping you can answer.

I always set up my TS environments with Roaming Profiles for all users
(stored in Profiles$), but never set up TSProfiles. It has been my
understanding, maybe incorrectly, that setting up TS profiles on a system
with roaming profiles for everyone would be redundant. Am I mistaken? If
so, what does having TS Profiles do for the users that just having Roaming
Profiles does not do?

Thanks for your insight.

--David



"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9B43ED5ABFC85veranoesthemutforsse@207.46.248.16...
> No problem, Cary, I'm glad I could help.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26 okt
> 2008 in microsoft.public.windows.terminal_services:
>
>> Geez! Okay....Rookie mistake. I did not look at the settings
>> and, like I said, was just testing. Next time I will look
>> before asking!
>>
>> Thanks, Vera. That was a waste of time......well, maybe not.
>> For the lazy (like me...in this case) here is the answer.
>>
>> Thanks again,
>>
>> Cary
>>
>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
>> in message
>> news:Xns9B4384AF8B4CFveranoesthemutforsse@207.46.248.16...
>>> There's a GPO setting for this as well:
>>>
>>> Computer Configuration - Administrative templates - System -
>>> User profiles
>>> "Add the Administrators security group to roaming user
>>> profiles"
>>>
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26
>>> okt 2008 in microsoft.public.windows.terminal_services:
>>>
>>>> Vera,
>>>>
>>>> Quick question: I tested this out on the Production server
>>>> but with two test accounts and via the ADUC (when I do this
>>>> for real it will be via GPO).
>>>>
>>>> Question: it looks like only that specific user has access to
>>>> the \\FS1\TSPROFILES$\testts folder. I can probably change
>>>> this by taking ownership of it and modifying permissions on
>>>> it. However.....
>>>>
>>>> Is it possible that I simply precreate the folders inside that
>>>> \\FS1\TSPROFILES$ folder? I would guess that I could and have
>>>> the folders inheirit the permissions set on the TSPROFILES
>>>> folder?
>>>>
>>>> Is this worth doing?
>>>>
>>>> Thanks,
>>>>
>>>> Cary
>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>>> wrote in message
>>>> news:Xns9B42E48ADA14Averanoesthemutforsse@207.46.248.16...
>>>>> No, you can still do this.
>>>>> Since the users logon to their laptops with a local account,
>>>>> they will already have different profiles for their laptops
>>>>> and the TS. Their current TS profiles will be stored on the
>>>>> Terminal Servers. When you define a TS profile path with a
>>>>> GPO, next time they logon they will still get their local TS
>>>>> profile (because the TS roaming profile folder is still
>>>>> empty), and when they logoff, their TS profile will be saved
>>>>> in the roaming TS profile path.
>>>>>
>>>>> Only problem with this is that they will have different
>>>>> profiles on the 2 Terminal Servers. So one of those will be
>>>>> lost in this scenario. I'd make a copy of all local TS
>>>>> profiles befor implementing this, so that you can manually
>>>>> try to merge some settings if needed.
>>>>> _________________________________________________________
>>>>> Vera Noest
>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>
>>>>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on
>>>>> 25 okt 2008 in microsoft.public.windows.terminal_services:
>>>>>
>>>>>> Good morning!
>>>>>>
>>>>>> Okay, Okay......I know that several of you in here will kill
>>>>>> me for this! Vera, Patrick, Jeff,.....sorry...but I did not
>>>>>> do this!!!! I am simply trying to fix some things and want
>>>>>> to make sure that I do not break things in the process....
>>>>>>
>>>>>> Anyway, a client has a small Terminal Server farm (two
>>>>>> servers).
>>>>>> A Terminal Server Profile was not implemented. Yikes! I
>>>>>> know!
>>>>>>
>>>>>> Anyway, most are using a Thin Client but some still use a PC
>>>>>> / Laptop to access the Terminal Server. Some of the of
>>>>>> these good people are Sales Folks who are almost never in
>>>>>> the office and log on to their laptops locally (read: the
>>>>>> "log on to:" part is populated with "mymachine (this
>>>>>> computer)").
>>>>>>
>>>>>> Anyway, I really would like to set this up properly. Is it
>>>>>> a bad idea - after the fact - to implement TS Profiles?
>>>>>>
>>>>>> My Documents and Desktop are already being re-directed via
>>>>>> Group Policy and the Terminal Servers are locked down via
>>>>>> GPO - Loopback Policy.
>>>>>>
>>>>>> I even have the PROFILE$ folder created for this....the
>>>>>> person behind me did not do that part of his tasks -AND- I
>>>>>> did not check to make sure that things were done...so,
>>>>>> ultimately, my bad!
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Cary

 

[Vera Noest [MVP]]

Re: TS Profiles

How do you set up your roaming profiles? In the AD account
properties?
From:

246132 - User Profile and Home Directory Behavior with Terminal
Services
http://support.microsoft.com/?kbid=246132

"If a Terminal Services Profile is specified, this path is used. If
this path is not specified, but a User Profile is specified, this
path is used."

So in your case, your users use the same profile on their
workstation and the Terminal Server. That is not a recommended
setup, as it might easily cause profile corruption.
I can also confuse users, since the profile will contain settings,
desktop and menu items which are not applicable on either the
client or the TS.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"David G. Hoch" <dhoch@dghtechnologies.com> wrote on 29 okt 2008
in microsoft.public.windows.terminal_services:

> Reading through this post was very interesting (thanks for the
> good information), but it did bring up a question that I'm
> hoping you can answer.
>
> I always set up my TS environments with Roaming Profiles for all
> users (stored in Profiles$), but never set up TSProfiles. It
> has been my understanding, maybe incorrectly, that setting up TS
> profiles on a system with roaming profiles for everyone would be
> redundant. Am I mistaken? If so, what does having TS Profiles
> do for the users that just having Roaming Profiles does not do?
>
> Thanks for your insight.
>
> --David
>
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9B43ED5ABFC85veranoesthemutforsse@207.46.248.16...
>> No problem, Cary, I'm glad I could help.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 26
>> okt 2008 in microsoft.public.windows.terminal_services:
>>
>>> Geez! Okay....Rookie mistake. I did not look at the settings
>>> and, like I said, was just testing. Next time I will look
>>> before asking!
>>>
>>> Thanks, Vera. That was a waste of time......well, maybe not.
>>> For the lazy (like me...in this case) here is the answer.
>>>
>>> Thanks again,
>>>
>>> Cary
>>>
>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>> wrote in message
>>> news:Xns9B4384AF8B4CFveranoesthemutforsse@207.46.248.16...
>>>> There's a GPO setting for this as well:
>>>>
>>>> Computer Configuration - Administrative templates - System -
>>>> User profiles
>>>> "Add the Administrators security group to roaming user
>>>> profiles"
>>>>
>>>> _________________________________________________________
>>>> Vera Noest
>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>> TS troubleshooting: http://ts.veranoest.net
>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>
>>>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on
>>>> 26 okt 2008 in microsoft.public.windows.terminal_services:
>>>>
>>>>> Vera,
>>>>>
>>>>> Quick question: I tested this out on the Production server
>>>>> but with two test accounts and via the ADUC (when I do this
>>>>> for real it will be via GPO).
>>>>>
>>>>> Question: it looks like only that specific user has access
>>>>> to the \\FS1\TSPROFILES$\testts folder. I can probably
>>>>> change this by taking ownership of it and modifying
>>>>> permissions on it. However.....
>>>>>
>>>>> Is it possible that I simply precreate the folders inside
>>>>> that \\FS1\TSPROFILES$ folder? I would guess that I could
>>>>> and have the folders inheirit the permissions set on the
>>>>> TSPROFILES folder?
>>>>>
>>>>> Is this worth doing?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cary
>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>>>> wrote in message
>>>>> news:Xns9B42E48ADA14Averanoesthemutforsse@207.46.248.16...
>>>>>> No, you can still do this.
>>>>>> Since the users logon to their laptops with a local
>>>>>> account, they will already have different profiles for
>>>>>> their laptops and the TS. Their current TS profiles will be
>>>>>> stored on the Terminal Servers. When you define a TS
>>>>>> profile path with a GPO, next time they logon they will
>>>>>> still get their local TS profile (because the TS roaming
>>>>>> profile folder is still empty), and when they logoff, their
>>>>>> TS profile will be saved in the roaming TS profile path.
>>>>>>
>>>>>> Only problem with this is that they will have different
>>>>>> profiles on the 2 Terminal Servers. So one of those will be
>>>>>> lost in this scenario. I'd make a copy of all local TS
>>>>>> profiles befor implementing this, so that you can manually
>>>>>> try to merge some settings if needed.
>>>>>> _________________________________________________________
>>>>>> Vera Noest
>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>>
>>>>>> "Cary Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on
>>>>>> 25 okt 2008 in microsoft.public.windows.terminal_services:
>>>>>>
>>>>>>> Good morning!
>>>>>>>
>>>>>>> Okay, Okay......I know that several of you in here will
>>>>>>> kill me for this! Vera, Patrick, Jeff,.....sorry...but I
>>>>>>> did not do this!!!! I am simply trying to fix some things
>>>>>>> and want to make sure that I do not break things in the
>>>>>>> process....
>>>>>>>
>>>>>>> Anyway, a client has a small Terminal Server farm (two
>>>>>>> servers).
>>>>>>> A Terminal Server Profile was not implemented. Yikes! I
>>>>>>> know!
>>>>>>>
>>>>>>> Anyway, most are using a Thin Client but some still use a
>>>>>>> PC / Laptop to access the Terminal Server. Some of the of
>>>>>>> these good people are Sales Folks who are almost never in
>>>>>>> the office and log on to their laptops locally (read: the
>>>>>>> "log on to:" part is populated with "mymachine (this
>>>>>>> computer)").
>>>>>>>
>>>>>>> Anyway, I really would like to set this up properly. Is
>>>>>>> it a bad idea - after the fact - to implement TS Profiles?
>>>>>>>
>>>>>>> My Documents and Desktop are already being re-directed via
>>>>>>> Group Policy and the Terminal Servers are locked down via
>>>>>>> GPO - Loopback Policy.
>>>>>>>
>>>>>>> I even have the PROFILE$ folder created for this....the
>>>>>>> person behind me did not do that part of his tasks -AND- I
>>>>>>> did not check to make sure that things were done...so,
>>>>>>> ultimately, my bad!
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Cary

 

[Leythos]

Re: TS Profiles

In article <Xns9B46A110723F9veranoesthemutforsse@207.46.248.16>,
vera.noest@remove-this.hem.utfors.se says...
> "If a Terminal Services Profile is specified, this path is used. If
> this path is not specified, but a User Profile is specified, this
> path is used."
>
> So in your case, your users use the same profile on their
> workstation and the Terminal Server. That is not a recommended
> setup, as it might easily cause profile corruption.
> I can also confuse users, since the profile will contain settings,
> desktop and menu items which are not applicable on either the
> client or the TS.
>

Not all of us use domain computers or even workstations for our terminal
server users.

We have 80+ Terminal Server users in the field at remote offices that
use Neoware and Wyse thin-client devices over the net that never log on
to the domain with a PC.

We've not had any problems with this.

--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)

 

[Vera Noest [MVP]]

Re: TS Profiles

Leythos <spam999free@rrohio.com> wrote on 30 okt 2008 in
microsoft.public.windows.terminal_services:

> In article <Xns9B46A110723F9veranoesthemutforsse@207.46.248.16>,
> vera.noest@remove-this.hem.utfors.se says...
>> "If a Terminal Services Profile is specified, this path is
>> used. If this path is not specified, but a User Profile is
>> specified, this path is used."
>>
>> So in your case, your users use the same profile on their
>> workstation and the Terminal Server. That is not a recommended
>> setup, as it might easily cause profile corruption.
>> I can also confuse users, since the profile will contain
>> settings, desktop and menu items which are not applicable on
>> either the client or the TS.
>>
>
> Not all of us use domain computers or even workstations for our
> terminal server users.
>
> We have 80+ Terminal Server users in the field at remote offices
> that use Neoware and Wyse thin-client devices over the net that
> never log on to the domain with a PC.
>
> We've not had any problems with this.

That's why I started with this question:

>> How do you set up your roaming profiles? In the AD
>> account properties?

Obviously, my post doesn't apply to your situation, because you
*do* use different profiles.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___