Solved

Not supported VM

  • 15 November 2017
  • 6 replies
  • 2447 views
K
Badge +1
I am getting an error about the source VM being not supported. The strange thing is it is in the list as possible supported VM's. Are there roles that are not supported (i.e. Domain Controller)? How does one obtain the logs to review? What are the checks it runs to ensure being supported for migration?

Actual Error:

Xtract
The following vm(s): 'XXX-XXX' are not supported in the source inventory 'DTLA',please update your migration plan and remove these vms before proceeding.
icon

Best answer by aluciani 29 March 2019, 21:38

Hi @kderenard2



👉 We don't support moving over Domain Controllers using Move.



ESXi Migration Limitations

For ESXi, migration of 25 VMs in a plan is qualified and supported.



The following migrations are not recommended, but can be performed with some limitations.


  • Exchange should be migrated by installing newer versions of Exchange Server in parallel with existing production environments, then move user mailboxes from the old system to the new one. For best practices, see Step-by-step Exchange Migration.
  • Domain Controllers should be migrated by preparing a new domain controller, and then migrating the Flexible Single Master Operations (FSMO) roles. For best practices, see Microsoft best practices for migrating domain controllers.
  • SQL Server should be migrated by installing a new SQL Server, and then performing the migration operations. For best practices, see Microsoft SQL Server 2012 best practices.
  • Time taken for migration depends on the size of the VM, data churn rate within the VM during migration, and network bandwidth/connectivity between source and on-premises data center.
View original
This topic has been closed for comments

6 replies

sandeepmp
Rank
Userlevel 4
Badge +19
kderenard2

Can you please provide more details.

Source
Destination

What OS and what is the application running in it
aluciani
Userlevel 7
Badge +35
Hi @kderenard2

Do you have any additional material to add?
Follow me on Twitter: https://twitter.com/AngeloLuciani
aluciani
Userlevel 7
Badge +35
Hi @kderenard2 - did you make any progress on this or are you still facing the issue?
Follow me on Twitter: https://twitter.com/AngeloLuciani
aluciani
Userlevel 7
Badge +35
Hi @kderenard2 Any update on this item?
Follow me on Twitter: https://twitter.com/AngeloLuciani
R
@kderenard2
Do you solve the issue?
aluciani
Userlevel 7
Badge +35
Hi @kderenard2

👉 We don't support moving over Domain Controllers using Move.

ESXi Migration Limitations
For ESXi, migration of 25 VMs in a plan is qualified and supported.

The following migrations are not recommended, but can be performed with some limitations.
  • Exchange should be migrated by installing newer versions of Exchange Server in parallel with existing production environments, then move user mailboxes from the old system to the new one. For best practices, see Step-by-step Exchange Migration.
  • Domain Controllers should be migrated by preparing a new domain controller, and then migrating the Flexible Single Master Operations (FSMO) roles. For best practices, see Microsoft best practices for migrating domain controllers.
  • SQL Server should be migrated by installing a new SQL Server, and then performing the migration operations. For best practices, see Microsoft SQL Server 2012 best practices.
  • Time taken for migration depends on the size of the VM, data churn rate within the VM during migration, and network bandwidth/connectivity between source and on-premises data center.
Follow me on Twitter: https://twitter.com/AngeloLuciani