Environment
PlateSpin Migrate version 12.0 HF1
Situation
In PlateSpin Migrate 12, the source workloads and targets that you discover using the PlateSpin Migrate Client do not display in the PlateSpin Migrate Web Interface. PlateSpin Migrate 12 Hotfix1 provides a "SyncUI" utility that you can use to synchronize them. After the synchronization is complete, you can view the discovered workloads and targets in the Web Interface. By default, this utility s located at "..\PlateSpin Migrate Server\bin\SyncUI.exe."
IMPORTANT: Before you run this utility, you must ensure that no jobs are in progress.
To minimize disruptions to your migration efforts, run this utility only when you have many discovered resources to synchronize between the Client and the Web Interface.
IMPORTANT: Before you run this utility, you must ensure that no jobs are in progress.
To minimize disruptions to your migration efforts, run this utility only when you have many discovered resources to synchronize between the Client and the Web Interface.
Resolution
To synchronize the discovered source workloads and targets, do the following:
1. On the Migrate Server, open a Command prompt change to the location where "SyncUI.exe" is located.
2. Run the following command:
SyncUI.exe [/help] | [/verbose] | [/exportPath] |
[/clientUIImportExportExe /webUIImportExportExe]
where:
help: Displays help for the "SyncUI" utility.
verbose:Displays the verbose logging for the "SyncUI" utility.
exportPath: The full path to the folder to which you export the client discovery data, and from which you import the data to the Web Interface. The default path is "<appdata%>\PlateSpin\SyncUI". However, you can specify a different path.
clientUIImportExportExe:The path to "PlateSpin.ImportExport.exe",the Migrate Client Import and Export utility. Specify this option only if you chose a different installation location for the Migrate Server. Otherwise, the command uses the default path "C:\Program Files\PlateSpin Migrate Server\bin".
webUIImportExportExe:The path to "ImportExport.exe", the Web Interface Import and Export utility. Specify this option only if you chose a different installation location for the Migrate Server. Otherwise, the command uses the default path "c:\Program Files\PlateSpin Migrate Server\PlateSpin Forge\bin\ImportExport".
NOTE: If the PlateSpin Migrate Client has discovered Hyper-V containers, these Hyper-V containers are also listed on the Web Interface after successful synchronization. The Web Interface does not support migration of workloads to Hyper-V containers, so you can ignore them. However, If you remove these containers from the Web Interface, they also get removed from the PlateSpin Migrate Client.
1. On the Migrate Server, open a Command prompt change to the location where "SyncUI.exe" is located.
2. Run the following command:
SyncUI.exe [/help] | [/verbose] | [/exportPath] |
[/clientUIImportExportExe /webUIImportExportExe]
where:
help: Displays help for the "SyncUI" utility.
verbose:Displays the verbose logging for the "SyncUI" utility.
exportPath: The full path to the folder to which you export the client discovery data, and from which you import the data to the Web Interface. The default path is "<appdata%>\PlateSpin\SyncUI". However, you can specify a different path.
clientUIImportExportExe:The path to "PlateSpin.ImportExport.exe",the Migrate Client Import and Export utility. Specify this option only if you chose a different installation location for the Migrate Server. Otherwise, the command uses the default path "C:\Program Files\PlateSpin Migrate Server\bin".
webUIImportExportExe:The path to "ImportExport.exe", the Web Interface Import and Export utility. Specify this option only if you chose a different installation location for the Migrate Server. Otherwise, the command uses the default path "c:\Program Files\PlateSpin Migrate Server\PlateSpin Forge\bin\ImportExport".
NOTE: If the PlateSpin Migrate Client has discovered Hyper-V containers, these Hyper-V containers are also listed on the Web Interface after successful synchronization. The Web Interface does not support migration of workloads to Hyper-V containers, so you can ignore them. However, If you remove these containers from the Web Interface, they also get removed from the PlateSpin Migrate Client.