Active Directory computers have a $ after the name

Recently computers in Active Directory started having a $ added to the end of the name.  When I open the properties of the computer it does not have a $.  Only when you view a computer in an OU does it show the $.  It only happens for about half the computers and servers.  There were no new policies applied to our network.  
mike926Asked:
Who is Participating?
 
t_hewlettCommented:
Tis very strange, I would exspect to this happening to new machines if the database was corrupt, but the fact that it is the older machines and server which have been affected is weird.
As you rebuilt the machines I can see the issue being resolved but it will not address the machine you can not rebuild... if any and it still leaves the question of why and will it re appear over time. If so will it be the same machines.....
It would be nice to find some sort of explanation, as I say if it was the AD being corrupt then it would should up in the event logs or DC diag would flag some thing....
Dont you hat eissue like this :-(
0
 
cshepfamCommented:
that means its hidden.  its only for the administrator to see.
0
 
cshepfamCommented:
try going to your folder options and select the reveal hidden files option
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
mike926Author Commented:
This is actually concerning Active Directory and not windows folders and files.  However, i already have that option set to view hidden files.
0
 
t_hewlettCommented:
This is a strange one, are you saying that the PC computer object within AD has a $ on the end of the object name? The 2 replys above seem to be thinking this is a share you are talking about. Unless I`m getting it wrong.....

This sounds like corruption in the build process to me, how do you build and add new machines to the domain?
I have seen machines accounts created with a whole load of grabage added to the end of the the object name. I think even disjoining and renaming the machines and then rejoining the account to the domain failed to solve the issue, but worth a try. A total rebuild was required, I think this was some thing to do with the process or image used for the ghosting section but not to sure.
As the $ sign is an invalid characture on for an object name this does seem like corruption to me. Is this just happening for new machine accounts and are you should the machine accounts dont already exist. This should not matter as the error returned should be clear that there is already a machine in there with the name. I can only guess you have some issue with the build/creation of the machine account. Can you add any details for the issue and the process ussed...?
0
 
mike926Author Commented:
That is correct...it's the computer object in AD that has the $.  

It's strange because new computer objects over the past couple months don't have the $, but older computers do including most of our servers like Exchange and Domain Controllers.  It was fine for a couple years and then all the sudden the $ popped up at the end of the computer object.  We have 3 network classifications and the other 2 dont have this issue and they all get the same images, policies, updates, etc.
0
 
t_hewlettCommented:
I must admit to having never seen this before, I`ll have a dig round as I`m a nosiy bugger but if you think of any thing or find any info give  us an update.
0
 
ChiefITCommented:
Mike:

It might be a good idea to get a copy of the files you want to keep off of that machine for now. This appears to be a possible corruption of the AD database.

Once you backed up your files, can you look at a DCdiag and event viewer files to see if we have any errors that can help us troubleshoot.

Since this effects about half of your computers, is this specific to one domain controller on a mulit domain controller domain? Maybe we have a mixed domain problem and the differences between the domain controllers is causing the issue.
0
 
mike926Author Commented:
I ran dcdiag and all tests passed for all 3 of our domain controllers and there are no errors in the event logs.  I guess it could be a corruption issue.  We have to rebuild all of our servers over the next few months anyway because of new policies and vulnerabilities that exist on the server.  Hopefully once that happens it will fix the issue.    I don't think its caused any issues, but it was just more of a nuisance than anything else so I was curious on what might have caused it.
0
 
ChiefITCommented:
There are tools to look at the contents of the Access tokens, Also known as the SID or security identifier. I think looking into the computer's SID contents would really help out in this case.

I am providing the whole link because I think this information is very useful in figuring it out.

 http://technet2.microsoft.com/windowsserver/en/library/6361e9c2-73ad-49c3-a012-6d09cebd31611033.mspx?mfr=true
0
 
ChiefITCommented:
How goes the battle?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.