• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 306
  • Last Modified:

Stopping roaming profiles on certain servers

Is there a way to stop terminal server profiles roaming to certain terminal servers?  My problems is that I have a farm of NT4.0 Terminal/Citrix servers and all users have terminal server profile paths in their user accounts.  This all works fine.  However the network now has several dozen windows 2000 servers running terminal services (in Admin mode) for administration and maintenance.   My problems is that when a user remotely connects to one of these 2000 servers they will download their NT4.0 TSE profile to it.  My problem gets worse as we are about to bring eight new Win2k Terminal servers in Application mode that users will access.  We cannot have NT40 profiles on these server (and visa versa).

Does anyone know a way to stop a specific server from downloading a roaming profile and to always use a local one.  I tried setting the slow network connection as high as it would go but these servers are on a giga-bit backbone and the logon sails right by the slow net detection!

Any ideas?
0
darrenburke
Asked:
darrenburke
1 Solution
 
ocon827679Commented:
You might have a couple options, but as long as you specify a roaming profile in the users' properties, then you're going to download their NT profile at least once.  You could add a registry change in the TSE login script that will set the users' profile to local, at least you only have to worry about downloading it once, after that the local will always be used.  The key to look at is HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\@SID.  You want to set the Reg_DWord to a 0 for local.
Another option you might have is to use a system variable for the server that you want profiles to go to rather than the server name itself.  We implemented this corporately and it works great.  Basically you set variables for each server that you want to house profiles.  These variables need to be applied to all workstations and server, specifically terminal servers, in the network.  Then you apply to each user the variable that corresponds to their profile server in User Manager.  It goes somethng like this:
Make a list of variables for all servers that house profiles:
%profile1% = server1
%profile2% = server2, etc.

Use a script to apply these variables to all workstations and servers.

Change each user's properties for their profile to reflect the variable:
\\%profile1%\profiles\%username%

If you want you can change the variables on the Terminal Servers to a central location.

Either way you still have the user profiles on the Terminal Servers because profiles get created for every user regardless.  You can't get around that issue.  The nice thing that the second suggestion gives you is a potentially smaller user profile on the Terminal Server if you specify it's variable different than regular network use (no terminal Server).  This keeps the size of all of the profiles down, which also affects the registry size.
0
 
darrenburkeAuthor Commented:
You are a genius!   Thank you.  I am going with the second suggestion, i.e setting local environment variables for the location of the profile path.

Thanks again

Darren
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now