Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Duplicate Computer Name on Network and Other Odd Things on Hyper-V

Avatar of JamesonJendreas
JamesonJendreas asked on
Windows Server 2003Microsoft Virtual ServerWindows Server 2008
3 Comments1 Solution544 ViewsLast Modified:
Ok I got an odd one here, and may have screwed something up.  Quick re-cap on whats going on - I have a web server that was out of space and long story short we decided while we truly migrate to a new server, I'm moving it to a virtual machine. So, what I did:
1. Remove the old server from my domain (added to work group)
2.  Imaged the hard drives
3. Shutdown the server
4. Restored my OS HD to a virutal machine (using shadowProtect Hardware Independent restore)
5. Mounted my data .vhd
6. Started up the VM
7. Added to the domain.

Now, whenever I add my old servers IP to the virtual server, I get that there is a duplicate computer name on my network.   The old server is completely offline and I've even renamed it.

I recently also updated my AD FSMO master to 2008 server, we're in mixed mode, but it's the master (for the time being). My troubleshooting steps were:
1. Remove the VM from the domain and shutdown
2. Check the Active directory
3. Found my server name under computers in AD (on multiple ADs)
4. Removed the entry for the hostname
5. Checked DNS records (both forward and reverse, on multiple DNS) and removed
6. Re-add the VM
7. Remove any "hidden adapters"
 

ASKER CERTIFIED SOLUTION
Avatar of binary_1001010
binary_1001010Flag of Singapore image

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Commented:
This problem has been solved!
Unlock 1 Answer and 3 Comments.
See Answers