Jump to content
Welcome to our new Citrix community!
  • Guidelines for Migration from CVAD On-Prem to Citrix DaaS–Control Layer: Part 2


    cugcblogs

    UddaveJajoo22Rnd.png by Uddave Jajoo, Indianapolis CUGC Leader

    This is in continuation to the previous blog post Guidelines for Migration from CVAD on Prem to Citrix DaaS – Control Layer: Part ). In this blog, I focus on the process of Exporting Site Database configuration from On-Prem XenDesktop Sites and Importing it to the Citrix Cloud Site.

    Part 2: Control Layer

    1. Install the Citrix ACT Tool.
    2. Export the on-premises site configuration.
    3. Merge your site data config to Citrix Cloud using ACT Tool.

    To begin with this process, download the tool and install the MSI by using the prompts as shown below. An icon for “Auto config” would be created.

    Install the Citrix ACT Tool
    Run the MSI on your On-Premises DDC, by right-clicking on the AutoConfig_PowerShell_x64.msi installer and clicking on Install.  [attachment=9684:name]
    Read the License Agreement and check the box if you accept the terms. Then click Install:  [attachment=9685:name]
    Files are copied and the progress bar continues moving until it finishes the install.  [attachment=9686:name]
    After the MSI runs, a window indicating successful completion pops up. Click Finish to close the MSI setup window.

    Note: Upon successful execution, the MSI creates the corresponding folder structure, located in C:\Users\<username>\Documents\Citrix\AutoConfig<!–NeedCopy–> , and also a desktop icon called Auto Config, which launches a PowerShell command prompt.
    This tool is the one used on subsequent steps.  
    [attachment=9687:name]

     

    Export the on-premises site configuration
    1. After running the MSI installer on the previous step, you get an Auto Config shortcut automatically created on the Desktop. Right-click this shortcut and click Run as Administrator.

    2. Run the Export-CvadAcToFile command. This command exports policies, manually provisioned catalogs, and delivery groups. It also exports applications, application folders, icons, zone mappings, tags, admin roles and scopes, and other items.

    Note: For MCS machine catalogs and delivery groups, refer to the steps on Requisites for Importing Site Configuration using different Provisioning Methods section in this guide.

    [attachment=9688:name]
    3. Once the tool finishes running, the overall status shows as True and the export process is completed (the output lines shown match the following illustration). 

    Note: If there are any errors, diagnostic files are created in the action-specific subfolders (Export, Import, Merge, Restore, Sync, Backup, Compare), which can be found under %HOMEPATH%\Documents\Citrix\AutoConfig<!–NeedCopy–> 

    [attachment=9689:name]
    4. The resulting .yml files are now in the current user’s Documents\Citrix\AutoConfig path.

    [attachment=9690:name]
    Get the required information:
    Customer ID:
    Go to the API Access tab and copy the Customer ID value, which can be found next to the customer ID<!--NeedCopy--> text as seen on the following screenshot (red rectangle):

    [attachment=9691:name]
    ClientID & Secret
    Get the ClientId and Secret from the existing already created Secret Client (Cloud Connector installation)

    [attachment=9692:name]

     

    Import your Site Configuration into Cloud

    During this step, you obtain the customer connection details, manually create your Zone mappings, and import the configuration to your Cloud tenant. 
    CustomerInfo.yml
    1. First, open your CustomerInfo.yml<!--NeedCopy--> file using a text editor application, such as Notepad. The following screenshot shows the CustomerInfo.yml<!--NeedCopy--> file values that must be edited (underlined in red):

    < # Created/Updated on 2020/01/29 16:46:47
                CustomerId: ‘markhof123’
                ClientId: ‘6713FEA6-46CC-4F8A-BC71-539F2DDK5384’
                Secret: ‘TwBLaaabbbaaaaaaaaaaw==’
                Environment: Production
                AltRootUrl: ‘’
                StopOnError: False
                AlternateFolder: ‘’
                Locale: ‘en-us’
                Editor: ‘C:\Program Files\Notepad++\notepad++.exe’
                Confirm: True
                DisplayLog: True>

    [attachment=9693:name]
    2. Paste the ID<!--NeedCopy--> and Secret<!--NeedCopy--> values onto the corresponding fields in the CustomerInfo.yml<!--NeedCopy--> file:

    [attachment=9694:name]
    ZoneMapping.yml
    Manually create the Zone Mapping file (ZoneMapping.yml)

    On-Premises Zones cannot be automatically migrated to a cloud Resource Location, so they must be mapped using the ZoneMapping.yml<!–NeedCopy–> file.

    Note: Migration failures occur if the zone is not mapped with a homonymous resource location (a Resource Location with the exact same name).
    1. Primary: You can find this name under your On-Premises Citrix Studio console > Configuration > Zones. (Example primary for XenDesktopNA: XenDesktopZone)

    [attachment=9695:name]
    2. Back in the same directory where your .yml files reside (Documents\Citrix\AutoConfig)<!--NeedCopy-->, open up the ZoneMapping.yml<!--NeedCopy--> using Notepad or your preferred text editor. 

    Note: The Primary<!--NeedCopy--> value must be replaced with the name of your corresponding Zone you want to migrate objects from (in your on-premises environment).

    [attachment=9696:name]
    3. Still on the ZoneMapping.yml<!--NeedCopy--> file, the Name_Of_Your_Resource_Zone<!--NeedCopy--> value must be replaced with your Cloud Resource Location name. This value can be found on your cloud portal under the Hamburger menu > Resource Locations:

    [attachment=9697:name]
    4. Copy your Resource Location name (Example: XenDesktopResourceLocation1):

    5. Paste this value on the ZoneMapping.yml file instead of the Name_Of_Your_Resouce_Zone value:

    [attachment=9698:name]
    6. When mapping Zones to different Resource locations, the file must look like this instead:

    [attachment=9699:name]
    CvadSecurity.yml
    7. Back in the same directory where your .yml files reside (Documents\Citrix\AutoConfig), open up the CvadAcSecurity.yml using Notepad or your preferred text editor.

    [attachment=9700:name]

    8. In the CvadAcSecurity.yml file, enter the username and password for your hypervisor connection, then Save the file.

    [attachment=9701:name]

    HostConnections.yml
    In terms of different sites and different hosting connection with same name, please make sure to properly update the respective hosting connections in the HostConnectios.yml file before running the Merge operation.

    Modify the hosting connection name in the .yml file as below:
     
    Find on-prem connection name and replace it with the new name you would want to be created in the Citrix Cloud for that respective connection.

    Example: HostConnectionNameOnPrem present in two different sites and then replace it with the required new name in each of the Site HostConnections.yml file

    For XenDesktopSite1 – HostConnectionNameOnPrem1 and For XenDesktopSite2 – HostConnectionNameOnPrem2

    [attachment=9702:name]

     

    Merge your Site Data config to Citrix Cloud using ACT Tool

    1. Back on the Migration tool PowerShell console, run the following command: Merge-CvadAcToSite to merge the existing Cloud configuration (if any exists) with the configuration exported from the On-Premises site.

    [attachment=9703:name]

    2. When each task runs successfully, the output looks green as .yml files are imported and the corresponding components are added to the cloud site:

    [attachment=9704:name]

    3. The resulting files show in the following directory: <This PC>\Documents\Citrix\AutoConfig\
    Import_<YYYY_MM_DD_HH_mm_ss>

    [attachment=9705:name]

    4. In this same folder, you can find a Backup_YYYY_MM_DD_HH_mm_ss folder. 

    Note: Copy this folder somewhere safe as it is a backup of the configuration.

    5.  The Backup folder contains the following files, which are helpful for reverting changes, if needed:

    [attachment=9706:name]


    Verify configuration created in Cloud Studio

    1. Access your Virtual Apps and Desktops service Manage tab via the Cloud Console > My Services > Virtual Apps and Desktops service > Manage tab).

    2. Refresh to make sure the Machine catalogsDelivery groupspoliciestags, and applications are now showing as expected. 

    Note: Depending on what you import, the results vary as they are specific to your own unique configuration. Review each section to make sure the expected items are listed.

    [attachment=9707:name]

     

    With this blog post, Citrix Admins and customers will be able to successfully migrate their Site Database to Citrix Cloud. In case of any issues encountered, please feel free to nudge the Citrix Support and to also reach out to me @udjajoo or email me @er.uddavejajoo@gmail.com.

     

    I will be writing one final blog with respect to this series for Control Layer Migration to Citrix cloud soon which will be focused on Cutover of resources from On-Prem DDCs to Citrix Cloud Connectors.

    Reference Articles:

    PoC Guide: Automated Configuration Tool | Citrix Tech Zone

    Migrate configuration to Citrix Cloud

    MIgrate From on Premises to cloud

    NEXT: Guidelines for Migration of CVAD On-Prem to Citrix DaaS–Control Layer: Part 3

    Are you a member of CUGC? Join FREE today!

    jajoo012523-01.jpg.7c81a58b79c5e231b7f397c999d24207.jpg

    jajoo012523-02.png.f939fbcee4ac4e151ce6caeeb2c2f98b.png

    jajoo012523-03.jpg.383c99ff62b72129f77176f4174e9e15.jpg

    jajook012523-04.jpg.5588db6987c14f0cf17c42aa99f49103.jpg

    jajoo012523-05.jpg.7f4a4b4ec9ce881b90b16ce99643b390.jpg

    jajoo012523-06.jpg.1b9cbfb0b776a7987d35edaee17ea83c.jpg

    jajoo012523-07.jpg.a0b903053bdc7d312ed745311564ec18.jpg

    jajoo012523-08.jpg.e071eb047adec52ad12c0d826d846f56.jpg

    jajoo012523-09.jpg.be300a4200b80007c8548512b712339f.jpg

    jajoo012523-10.jpg.656dfad978da084b962f17975635c4e6.jpg

    jajoo012523-11.jpg.b70f77bc21ea716aea44eb92fbc674fd.jpg

    jajoo012523-12.jpg.62ada4abe9e6d60f3972fdce84e4c9eb.jpg

    jajoo012523-13.jpg.434068063cca5e107a7cc9a4538e5424.jpg

    jajoo012523-14.jpg.69260fcde547eb1981f1a3abf84cefba.jpg

    jajoo012523-15.jpg.598f4348f7336885349bc7fa54b5841c.jpg

    jajoo012523-16.jpg.94c7d25f5b23e10aafb97bcc26ff069e.jpg

    jajoo012523-17.jpg.203a4e58107f7a449d812d4751503ce2.jpg

    jajoo012523-18.jpg.a7993037da67362983845044bd4b6085.jpg

    jajoo012523-19.jpg.c4545513f528a9564e1f7691ff4cf1c1.jpg

    jajoo012523-20.jpg.0d231e84afbb55d968611193f7a7b9fa.jpg

    jajoo012523-21.jpg.97d26389296dca939cd6fb3ff59bba4b.jpg

    jajoo012523-22.jpg.1d9fc923a2f0418461a45d1e4e2887f1.jpg

    jajoo012523-23.jpg.b3230a8d663e5ff396e9858c7fc80720.jpg

    jajoo012523-24.png.52cc24237926e0709249e98b48c76237.png


    User Feedback

    Recommended Comments

    Hi Uddave Jajoo,

     

    Thank for this detailed article covering all the steps, from start to finish. I have a question, please clarify. In our environment, all the server VDAs are created manually, no MCS or PVS used. No hosting connections. VDAs are not power managed, they are added to the catalog by Computer name. In such situations, what information should be updated in the CvadAcSecurity.yml file.

     

    Please let me know.

     

    Thanks.

    SRR - Citrix User

    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...