Re: Unable to delete local user profile in win2K server...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mark-Allen Perry (mark-allen_at_mvps_dot_org)
Date: 09/27/04 

Date: Mon, 27 Sep 2004 21:19:45 +0200

I've had this problem many times on client computers and the best way has been to reboot (yeah, I know...), log on locally as local admin and then delete it.

But I've also had pretty good luck logging in as a "local admin", meaning not through TS as an admin. You didn't specify which way you went. Since the machines were on the client site, I used PCAnywhere and was able to delete it.

Maybe someone else has a better way. If so, I would love to know it also. 

-- 
And always try the MS KB first before posting.
The answer is probably already posted.
MS KB: http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO
----
Mark-Allen Perry
ALPHA Systems
Marly, Switzerland
mark-allen_AT_mvps_DOT_org
  "Brad Pears" <donotreply@notreal.com> wrote in message news:ejeLzILpEHA.3624@TK2MSFTNGP10.phx.gbl...
  I am logged on as the administrator to our windows 2000 terminal server. I
  have been configuring all our TS users to use a roaming profile - and once I
  have copied the existing profile to the new shared profile location, I am
  deleting the local one - so that the next time they log on, it will change
  to a type of "roaming". This has been working great except for one user. The
  "Delete" button remains greyed out.
  This user is not currently logged on and has no special privs...
  If I try to delete her profile from the documents and settings directory
  instead, I get a sharing violation on "usrclass.dat" - The source or
  destination file may be in use.
  Short of rebooting my server (which is tough to schedule these days) is
  there any way I can "unlock" this file so as to be able to delete this
  user's local profile??
  Until I can get this done, the sysetem will not write profile changes back
  to the new shared profilke I have configured for her...
  Thanks,
  Brad
Quantcast