I had problems with this on 2 client machines that I was using to
import. I was getting something along not enough space on the drive. I
finally found that my temp  dive was redirected to documents  and settings
and yes I had too many. I deleted these out and was back on track.

I have not really decided what to do to be proactive. I just happen to
be looking at Q275517. Might be of some interest to you also. I think
a log on/off script could be used to clean up the temp area.
Interesting that Disk Cleanup does not clean a redirected temp. I would
have thought it would.

I thought that one could not delete local files  via login/off
script...please enlighten me....

I' am not sure of the limitations of the scripts. I would have to do the
research on it first. It was just something that came to mind. Best
case scenario in my opinion is to have Disk Cleanup take care of it. I
guess possibly a scheduled task could run. I have it on a list of
something to look at but I admin it is low on my list. I am happy to
have found the issue as for sometime I had no clue what was causing me
problems. If you find a way to solve this I too would be interested.

Most of our users are on roaming profiles, which, I have scheduled a robot
to clean the temps at night. Works quite well.

You might also want to kill the spooler service once a week and delete the
contents of \winnt\system32\spool\printers. This is the location of all the
temp files  for print jobs. I don't know if it is 2000 or Metaframe, but it does
not do a very good job of cleaning up after print jobs. I clean them maybe once
every two weeks and usually there is about a gig of files in that folder...