• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 549
  • Last Modified:

Unable To Re-add Machine to Domain

Hi all.

Lately I have noticed that when we remove a machine from our domain in order to be re-imaged, we cannot re-add it with the same machine name.  We usually end up adding an extra character to the new machine name to make this work.
We typically delete the machine name, re-image the machine and then try to join.

Thanks
0
IDMA
Asked:
IDMA
  • 3
  • 2
  • 2
  • +2
2 Solutions
 
Darrell PorterEnterprise Business Process ArchitectCommented:
How many domain controllers do you have?
Are you experiencing AD replication errors?
When you remove the computer from the domain, is the process of removing the computer correctly deleting the computer account?
What error do you receive when you attempt to add a computer back to the domain with the same name?
0
 
IDMAAuthor Commented:
-7 Dcs
-No replication errors so far
-Please enlighten me on to properly remove te computer from the domain.  Most of the time, these are machines that we get back in a non-bootable state.
-Most of the time we do not even get an error.  The joining procedure looks like it worked but then we cannot see the machine in the Computers OU.  And when performing a gpupdate, it fails.
0
 
Darrell PorterEnterprise Business Process ArchitectCommented:
Have you renamed or deleted the previous computer accounts from Active Directory manually?
The error may appear in the Security, System, or AD event log on the ADC against which you are authenticating for the join operation.
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.

 
IDMAAuthor Commented:
Yes.  Deleted manually
0
 
GiladnCommented:
Hi,

when you deploy this image back, check on active directory--> computers you should be able to reset computer account.
you can right-click the computer object in the Computers or appropriate container and then click Reset Account.
after that there will be no need to re-join the computer to the domain.

Post back,

Gilad
0
 
CamyCommented:
Resetting the account will leave the computer object there without the secure channel to the original machine, you would still need to re-join the machine to the domain - it would just use the existing computer object (with associated groups and existing location) rather than create a new one.

If rejoining the domain appear to work have your searched AD or just looked in the computers OU?

As WalkaboutTigger says there should be some entries in the event logs of the PC, what does gpupdate fail with when you try it?
0
 
GiladnCommented:
1. reset computer account.
2. re-join to domain.

please try and post back if working or not.

Gilad
0
 
hecgomrecCommented:
If the image you are using is already joined to the domain it won't work.

The image have to be of a single machine out of the domain, the desire name must be out of the AD and all replications finished.

Then take the new PC, rename it and join it to the domain.

If you can't re-create the image:

-Install the image
-Reboot
-Remove LAN connection
-Log in with an administrator account (local or domain)
-Remove the machine from the domain
-Reboot
-Re-install LAN connection
-Join the machine to the domain again (must be connected to the LAN).

Try it and post back
0
 
IDMAAuthor Commented:
I have not tested these solutions since we have not run into an new re-image until now.  I would assume that these solutions would work.
Sorry that I cannot have a definite answer.
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.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now