Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 829
  • Last Modified:

Change user profile storage location

Currently I have AD setup and many users use terminal services on the server.

My issue is that with many of these users logging into the server the C: drive is running out of disk space.

I would like to change C:\Document and Settings\%username% to \\main2\Users\%username%

I do not know how to change where the profile is stored...
0
Tyler Laczko
Asked:
Tyler Laczko
  • 9
  • 6
  • 2
  • +1
1 Solution
 
Brum07Commented:
0
 
jmoisyCommented:
Hello,

Here you will find the Microsoft help to do this.

http://support.microsoft.com/kb/236621/en-us

Regards,
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
Tyler LaczkoAuthor Commented:
jmoisy your solution is definitely not going to work seeing how this is on a server and I'm not going to reinstall to change profile path.
0
 
exx1976Commented:
Moving the profiles to a network share is not the best solution, as it will SERIOUSLY increase network traffic and slow everything down greatly.  I would do this:


Configure roaming profiles (if they aren't already configured)
Schedule DelProf /I /D:xx to run nightly and delete local copies of profiles older than xx number of days.


That's how I used to handle it on my old TS boxes.  Worked great.

HTH,
exx
0
 
Tyler LaczkoAuthor Commented:
but everyone connects to this server daily.

also the "network share" is directly connected to the Server.
0
 
exx1976Commented:
If the storage is directly connected to the server, then you should reference it by it's local name, not \\server\share..  As soon as you reference \\server\share, it has to climb the network stack and then back down again, only to realize it's trying to talk to itself.  It creates all the same headaches, but with the benefit of not clogging the rest of the network.  LOL

You can either add drives to the server and rehome the profiles then, or rebuild the server with larger drives, or tell your users to shrink their profile sizes.  Users shouldn't be using their desktop as a file storage location.  Do your users have home drives assigned to them?

Also, you could configure a GPO to clean out the Cached Internet Files at logoff, that's usually a big consumer of space..

Have you checked the profiles lately?  Do you have any turnover?  Certainly there are at least one or two profiles in there from users who are no longer employed..    ??
0
 
Tyler LaczkoAuthor Commented:
The solution I am looking for is how to move where their profiles are stored. I think you are referencing this when you mention "You can either add drives to the server and rehome the profiles then" can you please explain how to do this.
0
 
exx1976Commented:
Server 2000, 2003, or 2008?
0
 
Tyler LaczkoAuthor Commented:
03
0
 
exx1976Commented:
It looks like the KB posted by jmoisy will work fine for server 2003.  The last portion of the KB explains how to do it.  It's certainly not something I'd ever try, especially as it's unsupported by M$, but if you're in a bind, it should do the trick.

My personal feeling would be to rebuild the box with larger drives.  Terminal Servers, by their design, shouldn't hold any data, just applications.  Apps are easy enough to put back.
0
 
Tyler LaczkoAuthor Commented:
I do not want to use the method that is not supported by MS
0
 
Tyler LaczkoAuthor Commented:
still waiting for a solution.
0
 
Tyler LaczkoAuthor Commented:
no solution forced to delete
0
 
exx1976Commented:
You were given a solution.  Just because it's not the answer you wanted to hear doesn't mean it wasn't the right answer.
0
 
Tyler LaczkoAuthor Commented:
I am looking for a solution that is supported and recommended by microsoft.

And yes that answer needs to satisfy the person asking the question.
0
 
exx1976Commented:
If you want a Microsoft supported solution, then that was also provided.  Reinstall the server.  Just because it's not what you hoped for doesn't make it wrong.
0
 
Tyler LaczkoAuthor Commented:
Just because I don't want to argue about it im giving you the points so i can close the question
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 9
  • 6
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now