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

AD issues after moving VM between esxi 4.1 free hosts

I have moved a VM member server 2003 to a new esx host.  I shutdown the server on the old host, copied all the VM files, uploaded to the new host's datastore, and right-clicked the configuration file and choose IMPORT.  I did change the case of the server name from all caps to all lower.  When prompted I said that the VM was MOVED to a new host.

I am seeing NETLOGON, userenv, and LSA errors when the server boots and users login.  Even after joining the machine to a workgroup, deleteing the computer account from AD, and re-joining to the domain.

Help?
Error messages:


Event Type:        Warning
Event Source:    LSASRV
Event Category:                SPNEGO (Negotiator)
Event ID:              40960
Date:                     10/14/2011
Time:                    1:40:00 PM
User:                     N/A
Computer:          ****
Description:
The Security System detected an authentication error for the server domain\****$.  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    


Event Type:        Warning
Event Source:    LSASRV
Event Category:                SPNEGO (Negotiator)
Event ID:              40960
Date:                     10/14/2011
Time:                    1:39:41 PM
User:                     N/A
Computer:          ****
Description:
The Security System detected an authentication error for the server ldap/****.  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)".

Event Type:        Error
Event Source:    Userenv
Event Category:                None
Event ID:              1030
Date:                     10/14/2011
Time:                    1:39:41 PM
User:                     NT AUTHORITY\SYSTEM
Computer:          ****
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

Event Type:        Failure Audit
Event Source:    MSSQL$CCRCSAGE50
Event Category:                (4)
Event ID:              18456
Date:                     10/14/2011
Time:                    1:39:08 PM
User:                     NT AUTHORITY\SYSTEM
Computer:          ****
Description:
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: ****]

Did the guid or something get changed when I imported the VM to the new host?
Thanks for any help you can provide.
0
pmeyerson
Asked:
pmeyerson
  • 3
  • 3
1 Solution
 
ddiazpCommented:
Was your domain controller(s) part of the move?

Did your network configuration (ip addressing) change for the new VMs?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Changing the friendly name of the server in VMware, would not have caused this issue.

Is the date and time on the new Host Server correct?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Do you have valid networking on the new host, e.g. is the Network Interface connected to the correct network?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ddiazpCommented:
on the server that has the problem,

can you start nslookup and:

set type=srv
<domainname>
set type=ns
<domainname>

and post results as well?
0
 
pmeyersonAuthor Commented:
sorry i was able to correct this issue by re-importing and choosing "I copied it" when I started up the vm for the first time.  Apparently this is the only way to retain some of the server settings.  Split credit to each for your efforts.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The network would have been effected!
0
 
ddiazpCommented:
heheh I guess the answer to my first question:

Did your network configuration (ip addressing) change for the new VMs?

Was yes which explains the problem.


pointless now. pun intended!
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

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