Ah the fun of domains...

Associate
Joined
3 Feb 2003
Posts
1,771
Location
Sydney, Australia
Just had a tech decide to install a pc using the same computer name as one already attached to the network...

This has completely fooked both pc's and all the profiles on them I'm guessing because the SID's have been transferred to the new pc.

Is there a simple way to undo this? Renaming one of the pc's doesn't seem to be having the desired effect ;(
 
You give a techy who doesn't even check the absolute basics like machine name convention Domain Admin rights?

Mistake number 1! :)
 
Last edited:
How did he get it on the domain with the same name?

As long as the first machine wasn't currently attached to the network it is possible.
When joining the second machine to the domain they would have got the message "There is already a Computer Account for the machine xxxx - Do you wish to use it?"
A click on "Yes" and job done.
This would have ony failed if the original machine was still on the network and using that computer account.

As for a fix:
It all gets very messy now.
Probably best to drop both machines off the network, delete the computer account and then rejoin them both.
10-15 minutes work and probably the cleanest way.
 
Thanks guys, he's new to the company apparently and this was his first job at the facility. He may not be around too long...

I've reconnected both pc's. The main problem is the local profiles. It seems to have removed all permissions from the old pc which is a bit of a ball ache as it's a shared machine with quite a few accounts on it and documents saved in their local profile.

I think I'm going to have to copy the profile settings then region the p's and copy the profiles back across.
 
No I have never seen this either. Sounds a bit odd why would anyone want two machines with the same name ?

It isn't so that you can add a second PC with the same name.
It's if you are replacing a machine on the network.

Classic Example:

I have a users laptop on my network called jsmith.
John's laptop took a fall down a flight of stairs - not good.
John's new laptop arrives, I call it jsmith and add it on to the network.

I'm prompted that there is already a computer account for jsmith and do I want to use it for this machine.
If I say yes then the computer account is updated for the replacement machine.
If I say no then I'm prompted to choose a different name for this replacement machine.
 
It isn't so that you can add a second PC with the same name.
It's if you are replacing a machine on the network.

Classic Example:

I have a users laptop on my network called jsmith.
John's laptop took a fall down a flight of stairs - not good.
John's new laptop arrives, I call it jsmith and add it on to the network.

I'm prompted that there is already a computer account for jsmith and do I want to use it for this machine.
If I say yes then the computer account is updated for the replacement machine.
If I say no then I'm prompted to choose a different name for this replacement machine.

I have been working with domains for years and never seen that option !
 
Cant you just right click the computer account that you want working again and click "Reset account" within AD?

Should regenerate a SID for that machine.
 
I promise you this does happen and does exist - I'm not making it up. :)
I too have been working with networks for a long time - my first job in the industry was looking after NT 3.51 Domains.

If you fancy the test - do the following:

Assuming you have a Win2003 AD Domain.
Find a computer account that already exists in the AD, however the machine is currently NOT attached to the network.
Take either a WinXP or Vista workstation and attempt to join it to the domain (using the wizard) with the name that already exists.

You will get the prompt:
Computer account already exists for machine xxxx - do you wish to use it?
 
Easiest way would be to drop the machines into a workgroup delete the computer accounts from the AD and rename the PC's then re-add them.

I've seen the computer exists message several times it's no biggie.



M.
 
Back
Top Bottom