VMware Cloud Community
esuarez78
Contributor
Contributor
Jump to solution

P2V Servers, now cannot log in to domain

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?

Reply
0 Kudos
1 Solution

Accepted Solutions
mittim12
Immortal
Immortal
Jump to solution

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.   

View solution in original post

Reply
0 Kudos
11 Replies
mittim12
Immortal
Immortal
Jump to solution

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.  

esuarez78
Contributor
Contributor
Jump to solution

For some reason, the local administrator accounts are not functional now.  This has happened on two servers.

Reply
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

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.   

Reply
0 Kudos
esuarez78
Contributor
Contributor
Jump to solution

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.

Reply
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

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. 

Reply
0 Kudos
bulletprooffool
Champion
Champion
Jump to solution

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.

One day I will virtualise myself . . .
wtfmatt
Enthusiast
Enthusiast
Jump to solution

And it just goes without saying - ALWAYS reset your local administrator password as part as your P2V pre-reqs.

Reply
0 Kudos
esuarez78
Contributor
Contributor
Jump to solution

@wtfmatt,

The local account WAS reset before the P2V.  For some odd reason I couldn't log in using that account till after I tried what @mittim12 suggested.  After @mittim12's advice I could login to the local and admin domain account profile.

Reply
0 Kudos
wtfmatt
Enthusiast
Enthusiast
Jump to solution

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?

Reply
0 Kudos
hicksj
Virtuoso
Virtuoso
Jump to solution

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...

Reply
0 Kudos
esuarez78
Contributor
Contributor
Jump to solution

@mittim12I was forced to rejoin the server to the domain during the day & it worked witout issues.  Thanks!

Reply
0 Kudos