Skip to content

vBlog.nl

All about technology

Menu
  • Home
  • VMware Cloud Director
  • vSphere
  • Automation
    • PowerCLI
    • PowerShell
    • Terraform
  • NSX
  • Horizon DaaS
  • About Us
Menu

Horizon DaaS Migration Tool

Posted on March 13, 2019

Hi,

In this Blog post i will describe some more about the Fling Horizon Daas Migration Tool https://labs.vmware.com/flings/horizon-daas-migration-tool

From the Fling website it’s clear what this does

Horizon DaaS Migration Tool helps migrating from earlier versions of Horizon DaaS (6.1.5, 6.1.6, 7.0.0) to the latest supported version (8.0.0). The tool can be used to move persistent desktop mappings from existing tenants to a newly provisioned tenant on 8.0.0.

The migration is not an in-place migration and does require a parallel setup of VMware Horizon DaaS 8.0.0 to be available. The tool is a command line tool that must be run from a separate Ubuntu virtual machine.

How does this work?

You need a Ubuntu Server , and install the Fling on it. The documentation from the website describes this.

How to export the source tenant configuration?

Login to your Ubuntu VM. Go to /vmware/daas/migration/bin . and run python export.py -v

Example output:

root@daas-migratie:/vmware/daas/migration/bin# python export.py -v
You’ll be prompted to enter DaaS ServiceProvider and Tenant details now [Enter]:
Source service provider IP []: 10.100.10.10
Destination service provider IP []: 10.200.10.10
“Source service provider” password []:
Re-confirm “Source service provider” password []:
Source SP domain name []: SP
Source SP domain user []: adm-migratieuser
“Source SP domain” password []:
Re-confirm “Source SP domain” password []:
Provide source tenant, version no. from the list – [‘6.1.5’, ‘6.1.6’, ‘7.0.0’]. [Default: 6.1.6]: 6.1.5
Provide destination tenant, version no. from the list – [‘8.0.0’]. [Default: 8.0.0]:
Source tenant, org-Id []: 1021
Destination tenant, org-Id []: 1019

=== Input details validation ===

Source service provider Ip: “10.100.10.10”
Destination service provider Ip: “10.200.10.10”

Source SP domain name: “SP”
Source SP domain user: “adm-migratieuser”
Source tenant version: “6.1.5”
Destination tenant version: “8.0.0”
Source tenant org-Id: “1021”

Destination SP Ip: “10.200.10.10”
Destination tenant org Id: “1019”

Are the details correct ? [yes]:

DaaS Export: Progress [==================================================] 100.0% complete
DaaS Export – Done
root@daas-migratie:/vmware/daas/migration/bin#

Howto Import into the destination Tenant:

First create a file named vms_to_be_migrated.txt , in to the imported directory. in this example /vmware/daas/migration/data/10.200.10.10/1019

When ready run python import.py -v , inside the /vmware/daas/migration-toolkit/v2.0/bin directory.

Example Import output:

root@daas-migratie:/vmware/daas/migration-toolkit/v2.0/bin# python import.py -v
CA/SSL verification to be enabled [Options=yes|no, Default:yes]: no
You’ll be prompted to enter DaaS ServiceProvider and Tenant details now [Enter]:
Destination service provider IP [10.200.10.10]:
“Destination service provider appliance” password []:
Re-confirm “Destination service provider appliance” password []:
Destination SP domain name []: SP
Destination SP domain user []: adm-migratieuser
“Destination SP domain” password []:
Re-confirm “Destination SP domain” password []:
Source tenant, version no. [6.1.5]:
Destination tenant, version no. [8.0.0]:
Destination tenant, org-Id [1019]:
Require vCenter details for VM power management. What is your “destination desktop” vCenter hostname or Ip []: vc01.destinationvc.local
vCenter user []: adm-migratieuser
“vCenter password” password []:
Re-confirm “vCenter password” password []:

=== Input details validation ===
CA/SSL verification required: “False”
Fqdn: undef

Destination service provider Ip: “10.200.10.10”
Destination SP domain name: “SP”
Destination SP domain user: “adm-migratieuser”
Source tenant version: “6.1.5”
Destination tenant version: “8.0.0”
Destination tenant org Id: “1019”
vCenter host/Ip: “vc01.destinationvc.local”
vCenter user: “adm-migratieuser”

Are the details correct ? [yes]:

DaaS Import: Progress [==================================================] 100.0% complete
DaaS Import – Done
root@daas-migratie:/vmware/daas/migration-toolkit/v2.0/bin#

Now your Done , check the Daas 8 portal and see the imported VM in the pool.

Loading

Share on Social Media
twitter facebook linkedin reddit emailwhatsapptelegram

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent articles

  • vCloud Director API – Couldn’t connect to cloud server with the provided session id May 24, 2023
  • Horizon DaaS – Maximum sessions exceeded May 9, 2023
  • VMware Cloud on AWS with FSx for NetApp ONTAP December 28, 2022
  • Workspace ONE Access – Change certificate December 22, 2022
  • UI themes for VMware Cloud Director 10.4.1 and later December 16, 2022
  • VMware Tanzu Kubernetes Grid December 15, 2022
  • Workspace One Access – Not logged in to server FQDN. Please invoke Save before Sync December 12, 2022
  • NSX Edge configuration has failed. 1G hugepage support required. December 7, 2022
  • Horizon DaaS – Unable to connect to Desktop November 24, 2022
  • How to: Request and Install a Lets Encrypt Wildcard SSL on VMware Cloud Director 10.4 October 17, 2022

Tags

Automation bootstrapping Container Service Extension Credential Manager Desktone.log ESXi EUC EXi GPU Horizon DaaS Instant-Clone Logging NSX nsx-t PowerCLI PowerShell Putty Raspberry PI SSL Tanzu Terraform update vcd-cli vCenter vCloud vCloud Availability vCloud Director VDI vGPU VMware VMworld vSAN vSphere vVols workspace one Zerto

VMware Cloud Provider Blog

  • In the cloud world, one size doesn’t fit all
    by Vijoo Chacko on June 2, 2023 at 7:25 am

    The size make-up of enterprises in an industry can vary from sector to sector. Take for example, the commercial aviation industry. When did you last fly in a commercial plane that was not a Boeing or an Airbus? This is an industry clearly dominated by two major companies. Whereas the automotive industry is an example … Continued The post In the cloud world, one size doesn’t fit all appeared first on VMware Cloud Provider Blog.

  • Reminder: VMware Cloud Director Availability 4.2 and 4.3 End of General Support Approaching
    by Nikolay Patrikov on May 23, 2023 at 3:17 pm

    Keeping VMware Cloud Director Availability always up-to-date guarantees having all the latest and greatest features available for you and your tenants. But one more reason to consider it now is VMware Cloud Director Availability 4.2.x and 4.3.x will reach End of General Support (EOGS) on June 10, 2023, and will no longer be available for download from the VMware download pages. To ensure you … Continued The post Reminder: VMware Cloud Director Availability 4.2 and 4.3 End of General Support Approaching appeared first on VMware Cloud Provider Blog.

  • VMware Aria Rebranding on VMware Cloud Partner Navigator
    by Sulakshna Shrivastava on May 23, 2023 at 2:06 am

    We recently announced the renaming of the products within our Cloud Management family. These Aria rebranding updates have been implemented on the VMware Cloud Partner Navigator portal The post <strong>VMware Aria Rebranding on VMware Cloud Partner Navigator</strong> appeared first on VMware Cloud Provider Blog.

  • Upgrade vSphere now: vSphere 6.5 and 6.7 end of technical guidance is coming this November
    by Christopher Wong on May 20, 2023 at 3:00 pm

    With the general availability of VMware vSphere 8 Update 1, we would like to remind our Cloud Services Provider partner community that the end of general support for vSphere 6.5 and vSphere 6.7 was October 15, 2022. These versions are now under technical guidance until November 15, 2023. During the technical guidance phase, VMware does … Continued The post Upgrade vSphere now: vSphere 6.5 and 6.7 end of technical guidance is coming this November appeared first on VMware Cloud Provider Blog.

  • VMware NSX Migration for VMware Cloud Director 1.4.2 is now GA
    by Jaikishan Tayal on May 9, 2023 at 2:05 pm

    We’re thrilled to announce the release of the VMware NSX Migration tool for VMware Cloud Director 1.4.2! What is this Tool? If you are unaware of the VMware NSX Migration for VMware Cloud Director Tool, it can help you migrate your environment from NSX for vSphere to NSX T Data Center if you are currently … Continued The post VMware NSX Migration for VMware Cloud Director 1.4.2 is now GA appeared first on VMware Cloud Provider Blog.

©2023 vBlog.nl | Design: Newspaperly WordPress Theme