Move Not Detecting Correct OS | Nutanix Community
Skip to main content
Question

Move Not Detecting Correct OS


Trying to migrate a Server 2008 R2 server, and when I try to do a manual migration and run the script on the server, its saying its not running a supported OS.  

 

Support is trying to help, but we really aren’t getting anywhere, and I’m running up against a hard deadline to get this server migrated.

This topic has been closed for comments

3 replies

Forum|alt.badge.img+1
  • Adventurer
  • 9 replies
  • January 8, 2025

@Fayejaz 
Hi,

The following information may help someone with more knowledge:

- AOS version

- Script summary

- Detailed error message

 


JeroenTielen
Forum|alt.badge.img+8
  • Vanguard
  • 1361 replies
  • January 8, 2025

What you can do is the following:

  1. Create snapshot of the original virtual machine;
  2. Install the VirtIO drivers in the original vm;
  3. Nutanix Move the virtual machine (manual preperation, you already done this with the VirtIO driver installation)

  • Author
  • Voyager
  • 1 reply
  • January 8, 2025

We are using Move 5.5, running on AOS version 6.1.0.  When we run the automatic move it fails we see this in the console - 

Failed to execute guest command: 'C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\NutanixMove.bat --retain-ip C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\RetainIP.ps1 C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\wmi-net-util.exe --uninstall-vmware-tools C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\UninstallVMwareTools.ps1 --install-ngt C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\InstallNGT.ps1 --cleanup C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\cleanup_installation.ps1 --xml C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\TaskNutanixMoveOnStartConfig.xml --retain-ipv6-disabled-config C:\Users\ADMINI~1\AppData\Local\Temp\vmware200\RetainIPv6DisabledConfig.ps1' ExitCode: '1'.

 

When we run the script manually, we get this (IP x’d out) - 

Setting up the User VM with Xtract: x.x.x.x using script: 5.5.0 with arguments: retainIP:True, installVirtio:True, setSanPolicy:True, uninstallVMware
Tools:True, minPSVersion:4.0.0, installNgt:True
PowerShell version 5.1.14409 is supported
Global:Config -> ScriptVersion 5.5.0 | CurrentStep 0 | XtractIP x.x.x.x
OS Arch: @{osarchitecture=64-bit}
Hostname: xxxxxxxx
User VM OS () is not supported for migration. Supported Windows OSs are Microsoft Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, Window
s 7, 8, 10, 11.. Exiting.

 

We have uninstalled the virtio drivers that are automatically installed and tried an earlier version, and we get the same results.

 

This is the script from the manual attempt (I just x’d out the ips) - 

powershell.exe -command {Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::ServerCertificateValidationCallback = { $true }; [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12 -bor [Net.SecurityProtocolType]::Tls13; $scriptPath = (New-Object System.Net.WebClient).DownloadString('https://' + 'x.x.x.x' + '/resources/uvm/win/esx_setup_uvm.ps1'); $retainIP = $true; $installNgt = $true; $installVirtio = $true; $setSanPolicy = $true; $uninstallVMwareTools = $true; $minPSVersion = '4.0.0'; $virtIOVersion = '1.2.3.9'; Invoke-Command -ScriptBlock ([scriptblock]::Create($scriptPath)) -ArgumentList 'x.x.x.x',$retainIP,$setSanPolicy,$installNgt,$minPSVersion,$installVirtio,$uninstallVMwareTools,$virtIOVersion}