Jump to content
Welcome to our new Citrix community!
  • Migrate MCS Provisioned Catalogs Within One Data Center


    cugcblogs

    UddaveJajoo22Rnd.png by Uddave Jajoo, Indianapolis CUGC Leader

    Remove Machines from Old Catalog

    1. Identify the pool of machines to migrate from one cluster to another.
    2. In the Studio console, navigate to the delivery group tab and select the respective delivery group, right click, and select Edit Delivery group.
    3. Export the list of desktop assignment from delivery group before removing the machines from the catalog and save it locally on the Delivery controller. (Will be utilized in next section.)
    4. In Studio console, navigate to machine catalog and right click on the catalog, select View Machines.
    5. Turn the maintenance mode on those machines from within Studio console.
    image-14.png.f5ceebd869e43613bba4a168b4ed5ba2.png
    1. Remove the machines form the delivery group and leave the assigned users intact.
    image-15.png.bb473612b8239dc365b8cf2b97dc5626.png
    1. Right click on the machines, select Delete and Select the option “Remove the machines from catalog but do not delete the virtual machines.”
    image-16.png.aa36d83674722b14e3ae27c1a84c45c6.png
    1. Click Next, then Finish.
    image-17.png.c480b9aed2be1a68903f57c335d34b33.png
    1. Right click on the machine catalog and select manage AD Accounts and select the machine account and click remove. In the wizard, select the option to leave them in active directory.
    image-18.png.840f588ec6e5a4113494e8760a0a9f9c.png

    vMotion Machines from one cluster to another

    1. Navigate to vCenter console, select the OldCluster and navigate to VMs tab.
    2. Select all the required virtual machines which we need to migrate. Note: All machines should be powered off, so that you can migrate easily across cluster.
    3. Right click on the selected virtual machines and select Migrate. When prompted, select Yes and proceed further.
    image-19.png.43dca60c739b4c0dcb94c1028cbfcfe6.png
    1. In the next window, select the Compute and Storage migration option, click Next and select the NewCluster, click Next.
    image-20.png.7ef5dda0e57f409b439d9d65c3dcaa49.pngimage-21.png.f3f23b0e9b5c3661170d3179b396f0be.png
    1. In the next window, select Storage based on the least utilized and click Next.
    image-22.png.91c4a4e6213d90ae9f0a3386c261db84.png
    1. In the next window, change the networks to the distributed vSwitch for the corresponding VLAN.

      Example– Source Network :- OLDVLAN need to change to Destination Network – NEWVLAN

    image-23.png.67018906ce38959f3371bd95653840cb.png
    1. Select vMotion with higher priority and click Next.
    image-24.png.74b1b237b071264e494c7ea008a90dfb.png
    1. In the next window, review the selections and select Finish.

    Create New Standalone machine catalog in the Studio Console

    Note: For the machines that need to be migrated, make sure to Edit one of the VM config parameters in vSphere as below:

     

    XdConfig XdProvisioned=false

    image-25.png.741182d44321525904733db21d900015.png
    1. Create New Machine catalog, Click Next.
    2. In operating System, select Single Session OS and click Next.
    image-26.png.d95d88a7758b6c3f83c17f36e04a20b2.png
    1. In Machine management select the option as below: “Machines that are power Managed” and “Another Service or technology.”
    image-27.png.424f2ac6fde3409386d6a998481d98ac.png
    1. In the Desktop Experience select the option, “I want users to connect to the same(static) Desktop each time they log on.”
    image-28.png.d85e1d1fac2f7bc2b78871228bf21a9f.png
    1. In the next window, select the minimum functional level as 1811 or newer if the VDA agent is 1912 or higher.
    image-29.png.3ae94eec4b3560e40090b70461a1a5da.png
    1. Modify the exported list to include the parameter [VirtualMachinePath] within the csv file.
    2. Add the value against [VirtualMachinePath] header as below:
      • [VirtualMachinePath],[ADComputerAccount],[AssignedUsers]
      • XDHyp:\Connections\HostingConnectionName\DataCenterName.datacenter\ClusterName.cluster\MachineName.vm,Domain\MachineName,Domain\UserName
    image-30.png.8f21e95f81512fb7a9a2a40a00c30751.png
    1. Click on Import List and point to the location of exported list saved in the Section1-Step3.
    2. Select the CSV file containing VirtualMachinePath, ADComputerAccount and AssignedUsers.
    image-31.png.7e46be8f91c568b052376204b51d6481.png
    1. The machine name will show up along with the user assigned to the machine.
    image-32.png.f0a1266cd4e0bef2795b61872a9a1de0.png
    1. Click Next and in the Scopes leave default and click Next.
    2. Enter the machine catalog name and description.
    image-33.png.7631c0a51cd8c980a19cc8f23d51c83f.pngExample:-Machine Catalog Name: udjajoo_StandloneMCSCatalog
    1. Click Finish. Wait for the catalog to be created and it should contain the machine added during the catalog creation process.

    Add New machine catalog to the existing Delivery group

    1. Right click on the new machine catalog, select View machines.
    image-34.png.1e86b5a0ada86258f225b0bc03c85917.png
    1. Execute start operation on the machine from Studio, by right click on the machine. Select Yes when prompted.
    image-35.png.01099aeb92f6fc62c5e633a4aa3b46a9.png
    1. Verify in vCenter console that machine got powered on and gets registered in the Studio console.
    2. Navigate to vCenter and power on the migrated machines.
    3. In the studio console, verify that machines shows up as registered.
    4. Turn off the MM Mode on the machine.
    5. Navigate to the delivery groups tab and select the respective delivery group, Right click on the DG and select “Add Machines.”
    image-36.png.6299dc5373f255dcce5d96aab47be79b.png
    1. The newly created catalog will show up in the wizard and click Next.
    image-37.png.adc9986860cf21d657a8e69b1042f280.png
    1. In the next window, it will show the machine which is being added to the delivery group along with the AssignedUserIDs. Select Next.
    image-38.png.1869adbfba1d587dc08ab7f0d3f5ac18.png
    1. In the summary tab, review the selection and click Finish.

      Note: Published Name property of Desktop needs to be updated for machines/VDIs added to new Delivery group. Use below command, execute in PowerShell on Delivery Controller.

       

      Desktop Name – MachineName%

      $Desktops= Get-BrokerPrivateDesktop -MaxRecordCount 300 -Filter {DNSName -like “MachineName*”}

      Foreach ($Desktop in $Desktops) {Set-BrokerPrivateDesktop -MachineName $Desktop.MachineName -PublishedName “DesktopName“}

    image-39.png.1797f939f4d715c7cbc88ae77a0374e7.png

     

    See more posts by Uddave Jajoo here.

     

    Are you a member of CUGC? If not, join here for free today!


    User Feedback

    Recommended Comments

    There are no comments to display.



    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...