AD Assistance - corrupt recycling bin

osaddictosaddict London, UK
edited June 2010 in Science & Tech
I've created a new AD account (by copying an existing one, as permissions and access will be identical).

When I log on to a machine (any machine on the domain, not just one) I get an error message:

'The recycle bin on \\DomainName\DFS\Users\Username is corrupted. Do you want to empty the recycle bin for this drive'

Now I've had this once before and I deleted the account in question and recreated it, somebody else had created the account so I just put it down to them doing something odd.

This time it's happening and deleting the user doesn't work...

I think it could be connected to the fact that the user I am creating DID exist a while ago and was deleted. As such there was a home directory for them on the server - it whinged about this on creation.

I deleted the account and then deleted the users folder and tried to create the account again. It again complained about the home directory existing.

Any ideas what's causing (both) these errors and how I can rectify? - I'm fairly confident the home directory does NOT exist for this user as I deleted it!

Comments

  • kryystkryyst Ontario, Canada
    edited June 2010
    Delete the account. Delete the home directory, I don't know if you have exchange or other servers but if you do make sure that it's not tied up there anyway. Also if you have other directories that the user may have had specific security permissions for like on a file server you have to make sure they are purged to. Now if you delete the user what you'll see if you look into file security is a user that is listed as S1123124314 (well s and a series of alpha/#). That is a link to a deleted user. Those may need to be purged also.

    Then ideally you probably should reboot the server(s) that are AD members.
  • osaddictosaddict London, UK
    edited June 2010
    kryyst wrote:
    Delete the account. Delete the home directory, I don't know if you have exchange or other servers but if you do make sure that it's not tied up there anyway. Also if you have other directories that the user may have had specific security permissions for like on a file server you have to make sure they are purged to. Now if you delete the user what you'll see if you look into file security is a user that is listed as S1123124314 (well s and a series of alpha/#). That is a link to a deleted user. Those may need to be purged also.

    Then ideally you probably should reboot the server(s) that are AD members.

    Thanks Kryyst, this seems to be working now. I have a feeling I was being a bit impatient between deleting her folder and creating the user again.

    On a side note, when clicking on a file share to which the user had access and clicking the security tab I see a very brief flicker of an entry that looks like it has a red exclamation mark on and perhaps the S343423324 you mention. But as I say, the briefest of a a flicker, and just once!

    Not overly sure what this is, but hey, it's working and I don't have to butcher my naming convention as a nasty bodge :D
  • kryystkryyst Ontario, Canada
    edited June 2010
    Not sure why you would see a flicker of an account. I've only ever seen it there as a permanent account in security settings. But working is working and sometimes that's all you need to worry about.
Sign In or Register to comment.