Error:
Live migration of 'Virtual Machine WIN2012-STD' failed. Virtual machine migration operation for
'WIN2012-STD' faile...
4. In the Properties dialog box, click the Delegation tab.
5. On the delegation tab, select Trust this computer for delega...


To move virtual machine AND/OR storage: Select cifs.
[This is required if you want to move the storage along with the v...
I don’t see this Service as listed. What should I do?

How to add this as ‘Available Service’?
If in case you don't see "V...
command from an elevated command prompt. To open an elevated command prompt, click Start, rightclick Command Prompt, and t...
PS C:Windowssystem32>
setspn -S "Microsoft Virtual System Migration Service/WIN2012-R2-A" WIN2012-R2-A
setspn -S "Microsof...
Upcoming SlideShare
Loading in...5
×

HYPERV-2012-LIVE_MIGRATION-ERROR-0x80090303

4,867
-1

Published on

The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
4,867
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
29
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

HYPERV-2012-LIVE_MIGRATION-ERROR-0x80090303

  1. 1. Error: Live migration of 'Virtual Machine WIN2012-STD' failed. Virtual machine migration operation for 'WIN2012-STD' failed at migration source 'WIN2012-R2-A'. (Virtual machine ID F0938596-2A3B-46B59BE9-B23902253561) The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'WIN2012-R2-B': The specified target is unknown or unreachable (0x80090303). The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: The specified target is unknown or unreachable (0x80090303). Cause: The Service Principal Name (SPN) for the remote computer name does not exist and/or it is not added as constrained delegation for Kerberos. Resolution: Configure constrained delegation: If you have decided to use Kerberos to authenticate live migration traffic, configure constrained delegation before you proceed to the rest of the steps. You must use an account that is a member of the Domain Administrators group to configure constrained delegation. 1. Open the Active Directory Users and Computers snap-in. For example, to do this from Server Manager, select the server if it not already selected. After the server is selected, click Tools, and then click Active Directory Users and Computers. This opens the Active Directory Users and Computers snapin. 2. From the navigation pane, select the domain and double-click the Computers folder. 3. From the Computers folder, right-click the computer account of the source server and then click Properties.
  2. 2. 4. In the Properties dialog box, click the Delegation tab. 5. On the delegation tab, select Trust this computer for delegation to the specified services only. Under that option, select Use Kerberos only. 6. Click Add. 7. In the Add Services dialog box, click Users or Computers. 8. In the Select Users or Computers dialog box, type the name of the destination server [WIN2012-R2B]. Click Check Names to verify that you typed the name correctly, and then click OK. 9. In the Add Services dialog box, in the list of available services, do the following and then click OK.  To move virtual machines alone: Select Microsoft Virtual System Migration Service only. [In my case I am only testing moving a Virtual Machine, hence I selected only ‘Microsoft Virtual System Migration Service’]
  3. 3.  To move virtual machine AND/OR storage: Select cifs. [This is required if you want to move the storage along with the virtual machine, as well as if you want to move only a virtual machine’s storage. If the server is configured to use SMB storage for Hyper-V, this should already be selected] 10. On the Delegation tab of the Properties dialog box, verify that the services you selected in the previous step are listed as the services to which the destination computer can present delegated credentials. Click OK. 11. From the Computers folder, select the computer account of the destination server and repeat the process. In the Select Users or Computers dialog box, be sure to specify the name of the Source server.
  4. 4. I don’t see this Service as listed. What should I do? How to add this as ‘Available Service’? If in case you don't see "Virtual Machine Management Service" in the list of Available services that means, SPN is not registered for this property. Solution: Use ‘Setspn’ to set the target principal name for Virtual Machine Management Service. What is Setspn? Setspn Reads, modifies, and deletes the Service Principal Names (SPN) directory property for an Active Directory service account. You use SPNs to locate a target principal name for running a service. You can use setspn to view the current SPNs, reset the account's default SPNs, and add or delete supplemental SPNs. Setspn is a command-line tool that is built into Windows Server 2008. It is available if you have the Active Directory Domain Services (AD DS) server role installed. To use setspn, you must run the setspn
  5. 5. command from an elevated command prompt. To open an elevated command prompt, click Start, rightclick Command Prompt, and then click Run as administrator. Note: It is not usually necessary to modify SPNs. They are set up by a computer when it joins a domain and when services are installed on the computer. In some cases, however, this information can become stale. For instance, if the computer name is changed, the SPNs for installed services must be changed to match the new computer name. Also, some services and applications may require manual modification of a service account's SPN information to authenticate correctly. To VERIFY and view a list of the SPNs that a computer has already registered with Active Directory from a command prompt, use the PS C:Windowssystem32> setspn –l hostname To find the host name for a computer from a command prompt, type hostname, and then press ENTER. Service Principal Names (SPNs) can only be constructed by using the account base name as the Computer parameter, for example in our case computer parameter are: WIN2012-R2-A & WIN2012-R2B. My HYPERV HOSTS are:[It’s a 2 node cluster running WIN2012-R2 STD]   WIN2012-R2-A WIN2012-R2-B On each host, Right click on the Powershell and select ‘Run ISE as Administrator’.
  6. 6. PS C:Windowssystem32> setspn -S "Microsoft Virtual System Migration Service/WIN2012-R2-A" WIN2012-R2-A setspn -S "Microsoft Virtual System Migration Service/WIN2012-R2-A.test.com" WIN2012-R2-A Checking domain DC=test,DC=com Registering ServicePrincipalNames for CN=WIN2012-R2-B,CN=Computers,DC=test,DC=com Microsoft Virtual System Migration Service/WIN2012-R2-A Updated object Checking domain DC=test,DC=com Registering ServicePrincipalNames for CN=WIN2012-R2-B,CN=Computers,DC=test,DC=com Microsoft Virtual System Migration Service/WIN2012-R2-A.test.com Updated object PS C:Windowssystem32> **************************Repeat these steps on the 2nd Host**************************** ***********Once the SPNs are registered, follow the steps 1-8, as mentioned previously*********** If you are still facing this error, then ensure that all the Prerequisites requirement for Live Migration are met, please read the Microsoft TechNet article for more information. Configure Live Migration and Migrating Virtual Machines without Failover Clustering http://technet.microsoft.com/en-us/library/jj134199.aspx For Error code '0x80070569', please see the following KB: Starting or Live Migrating Hyper-V virtual machines may fail with error 0x80070569 on Windows Server 2012-based computers http://support.microsoft.com/kb/2779204/en-us Prepared by – ashwinwriter@gmail.com

×