Limiting Roaming profiles to Terminal Service Cluster

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hey

I"ve got two 2003 Terminal Service machines in a NLB scenerio and I would like to provide any user who logs into them a roaming profile so that they have the same desktop when they connect to different ones.
I've enabled Roaming profiles and did some local computer group policy changes on each of the the 2003 machines, but now this user is getting a roaming profile on all machines in the domain.

I've put the terminal servers in their own OU, and have been trying to find the way to turn off roaming profiles with the "Prevent Roaming Profile changes from propagating to the server" and the "Only allow local user profiles" settings but these seem to be only at the local machine level.

Is this the right approach or is there a way to point a user to a profile server on a per machine basis? Maybe there's a way to enable roaming profiles on the machine and through the AD account

Thank
Charlie
 
Why don't you remove the profile path for the user and add it to the
terminal server profile path. This way the profile is only effective when
logging into a terminal server. Another way to modify this is with the w2k3
policy. You can put the terminal servers in an OU an set loopback processing
and then set the terminal server profile path in the policy. The second is
more complicated but is effective for any user the first is only effective
for users configured this way.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
cb7 said:
Hey,

I"ve got two 2003 Terminal Service machines in a NLB scenerio and I
Click to expand...
would like to provide any user who logs into them a roaming profile so that
they have the same desktop when they connect to different ones.
I've enabled Roaming profiles and did some local computer group policy
Click to expand...
changes on each of the the 2003 machines, but now this user is getting a
roaming profile on all machines in the domain.
I've put the terminal servers in their own OU, and have been trying to
Click to expand...
find the way to turn off roaming profiles with the "Prevent Roaming Profile
changes from propagating to the server" and the "Only allow local user
profiles" settings but these seem to be only at the local machine level.
Is this the right approach or is there a way to point a user to a
Click to expand...
profile server on a per machine basis? Maybe there's a way to enable roaming
profiles on the machine and through the AD account?
 
Thanks for the info, I'll look into doing the group policy, it will probably be useful for doing changes in the future.

If I understand this correctly, the profiles will be kept and run off of the roaming profile server, and they will not be cached or synced on the local machine

Thanks
Charlie
 
Back
Top