Remote Profiles, change to Local?

[Scott Townsend]

When we first installed our TS we had intensions of having multiple TS to
handle the load. Well we only have one TS and do not see any plans to add
another.

We initially set up the TS to store the user's Profile on a Different
Server.

Now I'd like to get it so all of the profiles are local to the server.

So for instance I have the Following in the Registry
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders]
"AppData"="\\\\Server\\Profiles\\stownsend\\Application Data"

I'd like to get all of the users to have it point to the local Documents and
Settings folder for all of the Shell folders.

Seems like I originally did it with a Group Policy, but now its not defined.
Can I just Define it and have it point to the local folder?

Thanks,
Scott<-

 

[Guest]

All you have to do is remove the profile path in each user's account, so the
local profile will not continue to be copied to the netowrk at logoff. If
you had enabled DeleteRoamingCache, you'll want to disable this and log
everyone on/off once before disabling their roaming profile.

That being said, I wouldn't do what you're wanting to do (unless the roaming
profiles are problematic), as roaming profiles are great to have when you
need to upgrade hardware or bring a second machine online. If at some point
you need beefier hardware, you can set it up at your leisure and when people
logon for the first time their roaming profile will automatically be
downloaded.


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

 

[Scott Townsend]

On the Profile Tab of the user's Properties there is no entry for the User
Profile 'Profile Path' or the Home Folder 'Local Path'.

I guess I have a Few Issues. The Server that the Profiles are on is Dying.
Its BSODed several times causing the TS to not function what so ever. So I
want to get rid of the Server. We are in the Process of beefing up our Main
Data file server. So I had thought about moving them all to that server, but
we have not had great success with the Profiles on Remote Servers. We only
have the one TS that people use for a desktop. The other TS they use they
launch directly into the App, so there isn't much there besides a Printer
that they need.

The interesting thing is in the User Profiles under the System Properties,
there are only 6 or so profiles out of 55 listed as Roaming. All the others
are listed as Local. My Profile says Local. Though if I drag a folder from
root of C:\ to my desktop, it copies it to the Server where I have the
Profiles Stored. I believe there is an abandoned GPO that redirected the
user profile folders to the Remote Server.

Thank you for your Assistance...

Scott<-

All you have to do is remove the profile path in each user's account, so
the
local profile will not continue to be copied to the netowrk at logoff. If
you had enabled DeleteRoamingCache, you'll want to disable this and log
everyone on/off once before disabling their roaming profile.

That being said, I wouldn't do what you're wanting to do (unless the
roaming
profiles are problematic), as roaming profiles are great to have when you
need to upgrade hardware or bring a second machine online. If at some
point
you need beefier hardware, you can set it up at your leisure and when
people
logon for the first time their roaming profile will automatically be
downloaded.


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

When we first installed our TS we had intensions of having multiple TS to
handle the load. Well we only have one TS and do not see any plans to
add
another.

We initially set up the TS to store the user's Profile on a Different
Server.

Now I'd like to get it so all of the profiles are local to the server.

So for instance I have the Following in the Registry

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders]
"AppData"="\\\\Server\\Profiles\\stownsend\\Application Data"

I'd like to get all of the users to have it point to the local Documents
and
Settings folder for all of the Shell folders.

Seems like I originally did it with a Group Policy, but now its not
defined.
Can I just Define it and have it point to the local folder?

Thanks,
Scott<-