Roaming profiles
in [Terminal Services]
|
From: nix40 on 10 Nov 2009 11:01 I do not like using roaming profiles. It's a pain. Here's my situation. I have three windows 2003 windows servers. Server1 is not doing much, server2 is a terminal server with licensing, office and an application on it. Server3 was just built. My goal is two put server3 into TS and create a NLB for server 2 and server 3. I looked at server2 and noticed users have excell spreadsheets all over their desktops. Reason is they export data from the app running in ts to an excel spreadsheet. I don't wanna do roaming profiles. Does anyone know a good work around? What I'm thinking is since server1 doesn't have much of anything on it, I was going to create a session directory and put it on server1, move my licensing to server1 and than on the terminal services tab for each user ID I would put in a profile path pointing to server1.
From: Soo Kuan Teo [MSFT] on 16 Nov 2009 13:11 How many domain users do you have? It appears to me that your suggestion is a form of 'roaming profile', i.e. the user profile is not stored on local machine. Thanks Soo Kuan -- This posting is provided "AS IS" with no warranties, and confers no rights. "nix40" <nix40(a)discussions.microsoft.com> wrote in message news:177DDCE5-82BC-4116-A06F-60DE7BEA33C7(a)microsoft.com... >I do not like using roaming profiles. It's a pain. Here's my situation. > I have three windows 2003 windows servers. Server1 is not doing much, > server2 is a terminal server with licensing, office and an application on > it. > Server3 was just built. > My goal is two put server3 into TS and create a NLB for server 2 and > server > 3. I looked at server2 and noticed users have excell spreadsheets all over > their desktops. Reason is they export data from the app running in ts to > an > excel spreadsheet. I don't wanna do roaming profiles. Does anyone know a > good work around? > > What I'm thinking is since server1 doesn't have much of anything on it, I > was going to create a session directory and put it on server1, move my > licensing to server1 and than on the terminal services tab for each user > ID I > would put in a profile path pointing to server1.
From: Lanwench [MVP - Exchange] on 18 Nov 2009 18:57 nix40 <nix40(a)discussions.microsoft.com> wrote: > I do not like using roaming profiles. It's a pain. Here's my > situation. > I have three windows 2003 windows servers. Server1 is not doing much, > server2 is a terminal server with licensing, office and an > application on it. Server3 was just built. > My goal is two put server3 into TS and create a NLB for server 2 and > server > 3. I looked at server2 and noticed users have excell spreadsheets all > over their desktops. Reason is they export data from the app running > in ts to an excel spreadsheet. I don't wanna do roaming profiles. > Does anyone know a good work around? > > What I'm thinking is since server1 doesn't have much of anything on > it, I was going to create a session directory and put it on server1, > move my licensing to server1 and than on the terminal services tab > for each user ID I would put in a profile path pointing to server1. Roaming profiles are fine if you know how to set them up right and keep them tiny. Plus, with TS you should have a profile path specified via GPO. The real answer to your issue here is to use folder redirection for My Docs and Desktop (possibly also Application Data). You should do that whether or not you use TS, whether or not you use roaming profiles.
|
Pages: 1 Prev: Printer Sessions not clearing on log off Next: smart card removal problem |