I've virtualized some servers in our domain and after a few weeks now i cannot login to them. Does this have to do with the SID? I didn't use sysprep when virtualizing them. How do I correct this?
I have had luck disconnecting the network on servers and logging in with cached credentials in some cases. You could try that to see if you can get logged in.
Do you have a local administrator account you can login with? I'm sure if you rejoined the domain it would correct any issues you are having.
For some reason, the local administrator accounts are not functional now. This has happened on two servers.
I have had luck disconnecting the network on servers and logging in with cached credentials in some cases. You could try that to see if you can get logged in.
This got me in. Thanks for your help! Great idea!
Okay, I can't rejoin this server to the domain till the morning since I startedt to run the services on another server, but once I do I also believe this will solve the problem. At that point I'll update your answer to either Helpful or Correct. It was definitely helpful, but I'd rather wait to mark your answer as Correct rather than Helpful once I can successfully rejoin to the domin.
I'm glad it worked out. Nothing worse than having a server you can't login too. Good luck tomorrow and let us know if you run into any problems.
This is almost always to do with your DNS settings - or network settings.
Very all ip config on your VMs NIC(s)
Open a cmd prompt and make sure you can ping your domain controller.
Once you have done this, also just try pinging your domain name - if you can do this, it means you are resolving the domain and should be able to authenticate - so now you simply need to follow normal AD troubleshooting.
And it just goes without saying - ALWAYS reset your local administrator password as part as your P2V pre-reqs.
Wow. That's really strange. I've had issues logging into domains occasionally after a P2V, but never with local credentials.
Out of curiosity, did you modify the vNICs prior to kicking off the P2V? (remove the default and add a different one) or did you leave all the vNICs as defaults?
Seeing as this occurred a few weeks after the fact, I'd venture to say TIME is a possible culprit. If the time on your domain controllers is off by more than 5 minutes from member workstations/servers you're attempting to authenticate to, you will fail to login. Check how your DC's are grabbing and keeping time. There are several whitepapers out there covering virtualized DC's and time synchronization...
@mittim12I was forced to rejoin the server to the domain during the day & it worked witout issues. Thanks!
