Solved

Stopping roaming profiles on certain servers

Posted on 2001-06-26
2
301 Views
Last Modified: 2010-04-13
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
Comment
Question by:darrenburke
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 13

Accepted Solution

by:
ocon827679 earned 300 total points
ID: 6230890
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
 
LVL 4

Author Comment

by:darrenburke
ID: 6231522
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

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
There is a lot to be said for protecting yourself and your accounts with 2 factor authentication.  I found to my own chagrin, that there is a big downside as well.
Come and listen to Percona CEO Peter Zaitsev discuss what’s new in Percona open source software, including Percona Server for MySQL (https://www.percona.com/software/mysql-database/percona-server) and MongoDB (https://www.percona.com/software/mongo-…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question