Prev: Remote Desktop Administration not working
Next: Terminal Services will not work
From: Shay W on 31 Aug 2006 08:34
Can anyone tell me which one i should use when remote workers connecting into
the company want to view their profile. I read somewhere a few months ago
about Microsoft advising that terminal server and roaming profiles should not
point to the same place. However apart from them connecting to the terminal
server differently, shouldnt the terminal server be as an 'internel client',
thus use the roaming profile path? Also when creating a separate Terminal
Services profile path, certain things do not save, i.e the Signature on new
mail messages in Outlook. Can anyone advise me on these issues? Thanks
From: cendrars on 31 Aug 2006 11:00
Hello,

If using roaming profiles for TS users, redirect the TSProfile to a hidden
share on the network, and don't let the users play with it. Keep the
TSProfile on the same network segment as your terminal servers. This will
speed the logon process. You should also consider redirecting the additional
folders associated with the user, Appdata, My Docs, TS Homedir. This will
assist you with limiting the profile size, which will deliver better
performance.

Be sure to install UPHClean on all Terminal Servers if you are delivering
roaming profiles. Search MS for the download. Download and install the
latest version of the software.

Do some search on Roaming Profiles, there is a good deal of info out there.
Good luck.

"Shay W" wrote:

> Can anyone tell me which one i should use when remote workers connecting into
> the company want to view their profile. I read somewhere a few months ago
> about Microsoft advising that terminal server and roaming profiles should not
> point to the same place. However apart from them connecting to the terminal
> server differently, shouldnt the terminal server be as an 'internel client',
> thus use the roaming profile path? Also when creating a separate Terminal
> Services profile path, certain things do not save, i.e the Signature on new
> mail messages in Outlook. Can anyone advise me on these issues? Thanks
From: Shay W on 31 Aug 2006 11:24
Thanks for your prompt reply. Is there anyway in which the roaming and
terminal server profile can talk to each other so that they can syncronize.
My director would like to know whether it is possible for him to change
something on his roaming profile and then go home and see the same thing?


"cendrars" wrote:

> Hello,
>
> If using roaming profiles for TS users, redirect the TSProfile to a hidden
> share on the network, and don't let the users play with it. Keep the
> TSProfile on the same network segment as your terminal servers. This will
> speed the logon process. You should also consider redirecting the additional
> folders associated with the user, Appdata, My Docs, TS Homedir. This will
> assist you with limiting the profile size, which will deliver better
> performance.
>
> Be sure to install UPHClean on all Terminal Servers if you are delivering
> roaming profiles. Search MS for the download. Download and install the
> latest version of the software.
>
> Do some search on Roaming Profiles, there is a good deal of info out there.
> Good luck.
>
> "Shay W" wrote:
>
> > Can anyone tell me which one i should use when remote workers connecting into
> > the company want to view their profile. I read somewhere a few months ago
> > about Microsoft advising that terminal server and roaming profiles should not
> > point to the same place. However apart from them connecting to the terminal
> > server differently, shouldnt the terminal server be as an 'internel client',
> > thus use the roaming profile path? Also when creating a separate Terminal
> > Services profile path, certain things do not save, i.e the Signature on new
> > mail messages in Outlook. Can anyone advise me on these issues? Thanks
From: Patrick Rouse on 31 Aug 2006 11:38
No. Sharing the two profiles leads to profile corruption and possible data
loss. Imagine your boss is working via terminal server at home and saves
something on his/her desktop (not the best place fo items, but they do it
anyway). No they get into the office the next day, where they locked the
workstation console, instead of logging off. They decide to reboot because
they can't find their file and the workstation profile overwites the file
saved last night.

In addition to this scenario, terminal servers are most often not the same
OS as the desktop being used, so they should NOT be sharing the ntuser.dat,
as this causes corruption, where your boss will lose all of their settings.

Best thing you can do is redirect as much as possible out of the profiles,
i.e. my documents, start menu, desktop...

In a perfect world, it would work just like your boss wants, but it doesn't.

P.S. How often do they actually change their Outlook Signature, and how
hard is it to change in two places.


--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com


"Shay W" wrote:

> Thanks for your prompt reply. Is there anyway in which the roaming and
> terminal server profile can talk to each other so that they can syncronize.
> My director would like to know whether it is possible for him to change
> something on his roaming profile and then go home and see the same thing?
>
>
> "cendrars" wrote:
>
> > Hello,
> >
> > If using roaming profiles for TS users, redirect the TSProfile to a hidden
> > share on the network, and don't let the users play with it. Keep the
> > TSProfile on the same network segment as your terminal servers. This will
> > speed the logon process. You should also consider redirecting the additional
> > folders associated with the user, Appdata, My Docs, TS Homedir. This will
> > assist you with limiting the profile size, which will deliver better
> > performance.
> >
> > Be sure to install UPHClean on all Terminal Servers if you are delivering
> > roaming profiles. Search MS for the download. Download and install the
> > latest version of the software.
> >
> > Do some search on Roaming Profiles, there is a good deal of info out there.
> > Good luck.
> >
> > "Shay W" wrote:
> >
> > > Can anyone tell me which one i should use when remote workers connecting into
> > > the company want to view their profile. I read somewhere a few months ago
> > > about Microsoft advising that terminal server and roaming profiles should not
> > > point to the same place. However apart from them connecting to the terminal
> > > server differently, shouldnt the terminal server be as an 'internel client',
> > > thus use the roaming profile path? Also when creating a separate Terminal
> > > Services profile path, certain things do not save, i.e the Signature on new
> > > mail messages in Outlook. Can anyone advise me on these issues? Thanks
From: Shay W on 31 Aug 2006 11:52
Thank you for the reply Patrick. However my boss constantly changes his Excel
toolbar, by either add or deleting macro's that help him in his work, along
side any other stuff, i.e autotext. Is there any way in which these could be
carried over to the remote profile?



"Patrick Rouse" wrote:

> No. Sharing the two profiles leads to profile corruption and possible data
> loss. Imagine your boss is working via terminal server at home and saves
> something on his/her desktop (not the best place fo items, but they do it
> anyway). No they get into the office the next day, where they locked the
> workstation console, instead of logging off. They decide to reboot because
> they can't find their file and the workstation profile overwites the file
> saved last night.
>
> In addition to this scenario, terminal servers are most often not the same
> OS as the desktop being used, so they should NOT be sharing the ntuser.dat,
> as this causes corruption, where your boss will lose all of their settings.
>
> Best thing you can do is redirect as much as possible out of the profiles,
> i.e. my documents, start menu, desktop...
>
> In a perfect world, it would work just like your boss wants, but it doesn't.
>
> P.S. How often do they actually change their Outlook Signature, and how
> hard is it to change in two places.
>
>
> --
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.sessioncomputing.com
>
>
> "Shay W" wrote:
>
> > Thanks for your prompt reply. Is there anyway in which the roaming and
> > terminal server profile can talk to each other so that they can syncronize.
> > My director would like to know whether it is possible for him to change
> > something on his roaming profile and then go home and see the same thing?
> >
> >
> > "cendrars" wrote:
> >
> > > Hello,
> > >
> > > If using roaming profiles for TS users, redirect the TSProfile to a hidden
> > > share on the network, and don't let the users play with it. Keep the
> > > TSProfile on the same network segment as your terminal servers. This will
> > > speed the logon process. You should also consider redirecting the additional
> > > folders associated with the user, Appdata, My Docs, TS Homedir. This will
> > > assist you with limiting the profile size, which will deliver better
> > > performance.
> > >
> > > Be sure to install UPHClean on all Terminal Servers if you are delivering
> > > roaming profiles. Search MS for the download. Download and install the
> > > latest version of the software.
> > >
> > > Do some search on Roaming Profiles, there is a good deal of info out there.
> > > Good luck.
> > >
> > > "Shay W" wrote:
> > >
> > > > Can anyone tell me which one i should use when remote workers connecting into
> > > > the company want to view their profile. I read somewhere a few months ago
> > > > about Microsoft advising that terminal server and roaming profiles should not
> > > > point to the same place. However apart from them connecting to the terminal
> > > > server differently, shouldnt the terminal server be as an 'internel client',
> > > > thus use the roaming profile path? Also when creating a separate Terminal
> > > > Services profile path, certain things do not save, i.e the Signature on new
> > > > mail messages in Outlook. Can anyone advise me on these issues? Thanks
 |  Next  |  Last
Pages: 1 2
Prev: Remote Desktop Administration not working
Next: Terminal Services will not work