After converting a physical to virtual the physical loses domain access,why?

[digitalex]

We did a P2V with VMware converter and the convert was successful. We noirmally start the VM with no nic so we can verify all services are running and to remove some HP software that is no longer need. We then start the VM with the network card with access to the network. We then decided that the image was not working correctly and deleted the VM and wanted to restart the convert but found the physical machine was no longer able to long into the domain. Why is this? Is this because we allowed the VM to start with network activity and it updated the domain controller with the new SID?

Should we consider this a no problem and just readd it to the domain or is this a serious issue that should cause us to not keep converting?

[jjpatel]

this same thing happens to me also few months ago,

in my case we have two nic one for production network and one for backup network, after conversion process the dns registration process go wrong somehow ... so i would not be able to login to the server...

I am not sure is this the same case with you or not ? ( i just remove it from the domain and re-added it to the domain , working fine now)

[digitalex]

Sounds close. I see that it may be a problem with the OS and Domain authentication and it has to be rejoined.

[AWo]

We then decided that the image was not working correctly and deleted the VM and wanted to restart the convert but found the physical machine was no longer able to long into the domain.

Is this because we allowed the VM to start with network activity and it updated the domain controller with the new SID?

I assume you just deleted the virtual machine but not the domain account.

If it is a 1:1 clone there's no new SID, but maybe a new password between the DC and your virtual machine for the secure channel. This new password is unknown for your physical machine. You have to rejoin it to the domain (reset the host account in AD and readd it).

[TomHowarth]

if the conversion was a clone then what as probably happened is that the new VM clone has changed its Computer account's password. when you powered up your old physical box it could not attach to the domain because it is attempting to connect with invalid credentials. just reset your computer account and you should be good to go

Tom Howarth

VMware Communities User Moderator