Resolving Instant Clone Provisioning issues

There are several causes why an Instant Clone Pool hierarchy might not clean out properly from the vCenter Server Inventory. The causes include hardware failure or possible glitches in the Horizon Code or the vCenter infrastructure.
For example, I might execute a delete of an Instant Clone Desktop Pool or RDS Server Farm and either the vCenter server or the ESXi host are not available to receive the API call when sent from Horizon to Delete the Instant Clone Pool hierarchy. As a result we have Orphaned objects in the Inventory.

An administrator might not even realize that the call has failed and the Pool might continue to be redeployed at a later time with a new Instant Clone hierarchy.

We will look at two scenarios

  1. We replicate file loss which is more apparent as the hierarchy will show as (orphaned or Inaccessible)
  2. We will help show how to identify Instant clone elements no longer in use than need

However if it does happen its imperative the administrator knows how to clean out Read-only objects from the vCenter inventory.

Expand or collapse content Part 1. Introduction to the Lab environment

In this Lab this is the current state of the lab environment you will be troubleshooting and cleaning out

  • We have 2 Instant Clone based Desktop Pools.
    • One is a Linux Instant Clone Desktop Pool
    • One is a Windows 11 Instant Clone Desktop Pool
    • The Windows 11 Instant Clone Pool has been configured to be in ModeA. Therefore the CP-Parent image
    • The Linux Instant Clone Pool is in the default configuration that being ModeB
  • We have a RDS Server Instant Clone Farm
  1. On your Control Center server
    • open your Site 1  Chrome Browser
      • on the Favourites Bar
        • select the vcenter-01a shortcut
  1. In the vSphere client area
    • in the username area
    • in the password area
      • enter Pa$$w0rd
    • at the bottom of the screen
      • select LOGIN
  1. In the vSphere client
    • in the Hosts & Clusters inventory
      • note the Instant Clone hierarchy
  1. In the vSphere client
    • in the Hosts & Clusters inventory
      • compare the designated elements with your environment. Note that you have exactly the same entities

In the real world it might be helpful if Replica and Template VM hierarchy is documented. Failing to do that, it becomes very challenging to figure out which hierarchy is associated with which desktop Pool.
We are going to look at it from the perspective that this has not been done. We are providing the above graphic as a reference to relate, the labs do not depend on one knowing the above graphic. The object would be to figure the information out when this has not been documented.

In this setup you will also notice there is a hierarchy that has no Desktop Pool associated with it and has not been removed automatically. It is not showing up as orphaned as its Virtual Machine files still exist on the datastore .

  • Your first task will be to execute a script that damages the file structure of the Replica VM of your RDS server farm.
  • You will then execute a script rebooting the ESXi host and the Replica VM will then show as Orphaned.
  • We will also help you know how to identify which Virtual machines are the correct as this is not by default information available in either the vSphere or Horizon Console
  • We will demonstrate the Horizon Tools that can help us validate these associations.
  • We will use tools provided by Horizon to remove the Read-only status of the hierarchy so we can delete the virtual machines.
  • Once the correct Virtual Machines have been Identified, you will the proceed with a manual clean out of the vSphere Infrastructure.
  • Lastly you will re-deploy the Pools and validate they are working correctly

 

Expand or collapse content Part 2. Performing a vCenter Inventory cleanup and fix after Instant Hierarchy  failure using Traditional Horizon Tools
Expand or collapse content Section 1. Putting Horizon Virtual Machines in Maintenance Mode

When we have to perform maintenance tasks on an ESXi Cluster with multiple Instant Clone Pools, it can becoming daunting trying to get an ESXi host into Maintenance Mode. What one might experience is as one powers off certain virtual Machines others automatically power on. Putting the virtual machines in Maintenance Mode in Horizon facilitates maintenance tasks.

  1. On your Skillable Studio Resources tab
    • ensure that you have ControlCenter.techseals.co selected
      • select Ctrl+Alt+Delete
      • select Pa$$w0rd
  1. On the ControlCenter.techseals.co server
    • select the submit button
  1. On your ControlCenter Server
    • Site 1 - Bangalore Chrome browser
      • from the Favourites bar
        • select the Horizon shortcut
  1. From the Horizon Login page
    • in the User Name area
      • enter Administrator
    • in the Password area
      • enter Pa$$w0rd
        • select SIGN IN
  1. In the Horizon Administrative console
    • left-hand pane Inventory section
      • select Machines
  1. In the Machines area
    • In the Centre menu bar
      • next to Machine
        • select the checkbox
    • below the Tabs, to the right
      • select MORE COMMANDS
        • from the dropdown
          • select Enter Maintenance Mode
    • in the Enter Maintenance Mode window
      • select OK
Expand or collapse content Section 2. Performing the Break

we will execute 2 PowerShell scripts to facilitate a break scenario for us to fix

  1. On the ControlCenter.techseals.co server
    • on the Desktop
      1. select the START button
        • from the START menu
          1. select and right-click Windows PowerShell ISE
            • from the pop-out
              1. select More > Run as administrator
  1. In the Windows PowerShell ISE window
    • in the Terminal
      • enter cd c:\scripts
        • to select scripts
          • with your keyboard
            • press ENTER
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\ line
      • enter cd .\
      • with your Keyboard
        • select the down arrow to select lab 1. Troubleshooting Instant Clone
        • press ENTER
        • press ENTER
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\lab 1. Troubleshooting Instant Clone line
      • enter Set-ExecutionPolicy Unrestricted
        • with your Keyboard
          • press ENTER
  1. In the Execution Policy Change window
    • select Yes to All
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\Lab 1. Troubleshooting Instant Clone> line
    • enter .\
      • with your Keyboard
        • select the down arrow
          • select delete_replica_folder.ps1
            • press ENTER
            • press ENTER
  1. In the Security Warning window
    • select Run once
  1. In the Windows PowerShell ISE - Input window
  1. In the Windows PowerShell ISE window
    • Read the TERMS of USE of this script
      • choose your response to the terms terms and conditions
        • enter either Yes to agree or No to disagree

If you agree you can continue with this Lab

Steps 10 and 11 need to be executed fast or else the RDS servers are restarted.

  1. In the Windows PowerShell ISE window
    • When prompted "Do you want to continue? (y/N):
      • enter y
      • with your Keyboard
        • press ENTER

Note. If the Replica folder delete was not successful run , run the script again and make sure that step 12 and 13 are executed with no time wasting between these steps

  1. In the Windows PowerShell ISE window
    • PS C:\scripts\Lab 1. Troubleshooting Instant Clone> line
    • enter .\
    • with your Keyboard
    • select the down arrow
      • select shutdown_vms.ps1
        • press ENTER
        • press ENTER
  1. In the Security Warning window
    • select Run once
  1. In the Windows PowerShell ISE - Input window
  1. In the Windows PowerShell ISE window
    • Read the TERMS of USE of this script
      • choose your response to the terms terms and conditions
        • enter either Yes to agree or No to disagree

If you agree you can continue with this Lab

  1. In the Windows PowerShell ISE - Input window
    • when prompted
      • Do you want to continue? (y/N):
        • with your keyboard
          • Enter y

Give yourself five minutes before moving on the next section

Expand or collapse content Section 3. Understanding preparing and resolving the Issue
  1. On your Controlcenter server (if nec
    • Site 1 - Bangalore browser
      • from the Favourites bar
        • select the vcenter-01a shortcut
  1. In the vSphere client
    • in the username area
    • in the password area
      • enter Pa$$w0rd
    • enter LOGIN
  1. In the vSphere Client
    • select the esxi.techseals.co host and right-click
      • from the dropdown
        • select Maintenance Mode > Exit Maintenance Mode
  1. In the vSphere client
    • Host & Clusters inventory
      • expand vcenter-01a.techseals.co
      • expand the Region01A Datacenter
      • expand the Bangalore Cluster

In the vCenter inventory note that one of the cp-replica- * vms is ( inaccessible )

Notice in the Inventory RDS-Farm-1 & RDS-Farm-2 are powered Off

  1. In the vSphere Client Inventory
    • at the bottom of the window
      • below Recent Tasks
  • Notice
    • below Task Name > Power on virtual machine
    • below Target > RDSFarm-1 & RDSFarm-2
    • below Status > Unable to enumerate all disks. A required file was not found

A typical scenario might be hardware failure.
Having Instant  CloneTechnology, we are able to redeploy and repair , we have the RDS-Master available so redeploying the farm and getting the Farm up and running is not a problem.

However, doing this with the existing old hierarchy in place will cause the provisioning to fail

We therefore need to do the following

  1. disable provisioning in the Pool
  2. clean out the old hierarchy
  3. re-enable provisioning

 

Expand or collapse content Step 1. Disabling Pool Provisioning
  1. On your Controlcenter server
    • Site 1 - Bangalore browser
      • from the Favourites bar
        • select the Horizon Site 1
  1. In the Horizon login
    • in the username area
      • enter administrator
    • in the password area
      • enter Pa$$w0rd
    • enter SIGN IN
  1. In the Horizon Admin Console
    • side Menu Pane > Inventory area
      • select Farms
  1. In the Horizon Admin Console
    • Farms area
      • next to RDS-Farm-BLR
        • select the check box
      • select EDIT
  1. In the Edit Farm - RDS-Farm-BLR area
    • select the Provisioning Settings tab
  1. In the Edit Farm - RDS-Farm-BLR area
    • Provisioning Settings tab
      • next to Enable Provisioning
        • uncheck the checkbox
      • to close the Edit Farm - RDS-Farm-BLR  window
        • select OK
Expand or collapse content Step 2. Cleaning out the unwanted hierarchy using traditional Horizon Tools

Overview of objective we want to achieve

  • We have a Replica-VM and Template-VM (Yellow) that are associate with RDS Server Farm
  • This needs to be cleaned out.
    • We will use the traditional tools to validate this below diagram
    • Then remove the unwanted elements in the hierarchy.
  1. On the ControlCenter server
    • select and Open the Remote Desktops > Site 1 folder
    • In the Site 1 folder
      • select and double-click the Horizon-01a.RDP shortcut
  1. On the Horizon-01a server
    • from the Desktop
      • select and right-click the Command Prompt
        • from the pop-out menu
          • select Run as administrator
  1. In the Administrator: Command Prompt window
    • enter
cd C:\Program Files\Omnissa\Horizon\Server\tools\bin
  • with your keyboard
    • select ENTER
  1. In the Administrator: Command Prompt window
    • enter dir
  1. In the Administrator: Command Prompt window
    • enter
iccleanup.cmd -vc vcenter-01a.techseals.co -uid [email protected] -skipCertVeri
  • next to Please enter vCenter Password
    • enter Pa$$w0rd
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (list/unprotect/delete/exit):
      • type list
        • with your keyboard
          • select ENTER
  1. In the Administrator: Command Prompt window
    • scroll down notice you  have 4 pairs of images
    • Note number 2.
      • the cp-template GUID and the cp-replica GUID
      • matches what we have in the screenshot below
    • We will clean out these elements from vCenter
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (unprotect/delete/output/back):
      • type unprotect -I 2
    • then below to continue this operation.
      • type UNPROTECT
    • with your keyboard
      • press ENTER
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (unprotect/delete/output/back):
      • type delete -I 2
    • then below to continue this operation.
      • type DELETE
    • with your keyboard
      • press ENTER

note. you might get errors. Look out for a result which says " The specified group of internal Vms, with index 2 has been successufly deleted"

  1. In the Administrator: Command Prompt window
    • In line with Please input the command (unprotect/delete/output/back):
      • type back
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (list/unprotect/delete/exit):
      • type list
        • with your keyboard
          • press ENTER
  1. In the Administrator: Command Prompt window
    • note that now you only have 3 VM groups
  • note that we still have an un-associated VM group
    • If look at the command line, this is INDEX VM group 1
    • We have staged this situation, but it can sometimes happen that VM groups do not get deleted during maintenance operations
    • In the next step, we will use the iccleanup.cmd tool to delete this VM Group
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (unprotect/delete/output/back):
      • type unprotect -I 1
    • then below to continue this operation.
      • type UNPROTECT
    • with your keyboard
      • press ENTER
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (unprotect/delete/output/back):
      • type delete -I 1
    • then below to continue this operation.
      • type DELETE
    • with your keyboard
      • press ENTER
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (unprotect/delete/output/back):
      • type back
  1. In the Administrator: Command Prompt window
    • In line with Please input the command (list/unprotect/delete/exit):
      • type list
  1. In the Administrator: Command Prompt window
    • scroll down
      • note the now you only have two VM Groups
Expand or collapse content Step 3. Cleaning out vCenter RDS servers and Horizon RDS elements
  1. On your Controlcenter server
    • Site 1 - Bangalore browser
      • from the Favourites bar
        • select the vcenter-01a shortcut
  1. In the vSphere client
    • in the username area
    • in the password area
      • enter Pa$$w0rd
    • enter LOGIN
  1. In the vSphere client
    • Host & Clusters inventory
      • expand vcenter-01a.techseals.co
      • expand the Region01A Datacenter
      • expand the Bangalore Cluster

Notice in the Inventory RDS-Farm-1 & RDS-Farm-2 are powered Off

These are still from the previous deployment

  1. In the vSphere Client inventory
    • select and right-click RDS-Farm-1
      • in the dropdown
        • select Remove from Inventory
      • in the Confirm Remove window
        • select YES

Repeat the Task for RDS-Farm-2

  1. In the vSphere client
    • select the Datastores Icon
  1. In the vSphere client
    • select the Datastores Inventory
      • select CorpLun-01a
  1. In the CorpLun-01a area
    • select the Files tab
    • In the Files area
      • left Inventory pane
        • next to CorpLun-01a
          • select the expand icon
      • in the Overview area
        • in front of RDS-Farm-1 and RDS-Farm-2
          • select the checkboxes
        • in the top right corner
          • select Delete
      • in the Confirm Deletion window
        • select OK
  1. On your Controlcenter server
    • Site 1 - Bangalore browser
      • In the Horizon login
        • in the username area
          • enter administrator
        • in the password area
          • enter Pa$$w0rd
        • enter SIGN IN
  1. In the Horizon Admin Console
    • side Menu Pane > Inventory area
      • select Farms
  1. In the Horizon Admin Console
    • Farms area
      • select RDS-Farm-BLR
  1. In the RDS-Farm-BLR area
    • select the RDS Hosts tab
  1. In the RDS-Farm-BLR area
    • RDS Hosts tab
      • next to DNS Name
        • select the checkbox
      • select REMOVE FROM FARM
  1. In the Remove RDS Host window
    • select OK
Expand or collapse content Step 4. Re-enabling Pool Provisioning
  1. In the Horizon Admin Console
    • side Menu Pane > Inventory area
      • select Farms
  1. In the Horizon Admin Console
    • Farms area
      • next to RDS-Farm-BLR
        • select the check box
      • select EDIT
  1. In the Edit Farm - RDS-Farm-BLR area
    • select the Provisioning Settings tab
  1. In the Edit Farm - RDS-Farm-BLR area
    • Provisioning Settings tab
      • next to Enable Provisioning
        • check the checkbox
      • select OK
  1. In the vSphere Client
    • Hosts & Clusters Inventory
    • Recent Tasks
      • note that a new cp-template and cp-replica are being created
      • note the GUID ID of your cp-template and cp-replica for future reference

Don't wait too long or else you will loose the opportunity to note this information

After about 5 minutes

  1. In the vSphere Client
    • Host & Clusters inventory
      • note that your RDS Servers are now deployed
  1. In the Horizon Admin console
    • under Farms > RDSFarm_BLR
      • select the RDS Hosts tab
      • scroll to the right of the middle pane and observe the Status
      • Do you notice that both RDS servers are now Available
  1. In the vSphere Client
    • Host & Clusters inventory
      • note that your RDS Servers are now deployed
      • Also note you have a new VM hierarchy in your Inventory.
      • Compare it to what you had originally
Expand or collapse content Part 3. Performing a vCenter Inventory cleanup and fix after Instant Hierarchy  failure using the Horizon Instant Clone Associated VMs Tool
Expand or collapse content Section 1. Putting Horizon Virtual Machines in Maintenance Mode

When we have to perform maintenance tasks on an ESXi Cluster with multiple Instant Clone Pools, it can becoming daunting trying to get an ESXi host into Maintenance Mode. What one might experience is as one powers off certain virtual Machines others automatically power on. Putting the virtual machines in Maintenance Mode in Horizon facilitates maintenance tasks.

  1. On your Skillable Studio Resources tab
    • in the top right-corner
      • select X Exit Lab
      • select X End Lab
    • when prompted Are you sure you want to end this lab?
      • select Yes end my lab
    • when prompted Lab Closed
      • select Close Window
  1. On your Lab Profile page
    • to relaunch your lab
      • select Launch
  1. On your Skillable Studio Resources tab
    • ensure that you have ControlCenter.techseals.co selected
      • select Ctrl+Alt+Delete
      • select Pa$$w0rd
  1. On the ControlCenter.techseals.co server
    • select the submit button
  1. On your ControlCenter Server
    • Site 1 - Bangalore Chrome browser
      • from the Favourites bar
        • select the Horizon shortcut
  1. From the Horizon Login page
    • in the User Name area
      • enter Administrator
    • in the Password area
      • enter Pa$$w0rd
        • select SIGN IN
  1. In the Horizon Administrative console
    • left-hand pane Inventory section
      • select Machines
  1. In the Machines area
    • In the Centre menu bar
      • next to Machine
        • select the checkbox
    • below the Tabs, to the right
      • select MORE COMMANDS
        • from the dropdown
          • select Enter Maintenance Mode
    • in the Enter Maintenance Mode window
      • select OK
Expand or collapse content Section 2. Performing the Break

We will execute 2 PowerShell scripts to facilitate a break scenario for us to fix

  1. On the ControlCenter.techseals.co server
    • on the Desktop
      1. select the START button
        • from the START menu
          1. select and right-click Windows PowerShell ISE
            • from the pop-out
              1. select More > Run as administrator
  1. In the Windows PowerShell ISE window
    • in the Terminal
      • enter cd c:\scripts
        • to select scripts
          • with your keyboard
            • press ENTER
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\ line
      • enter cd .\
      • with your Keyboard
        • select the down arrow to select lab 1. Troubleshooting Instant Clone
        • press ENTER
        • press ENTER
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\lab 1. Troubleshooting Instant Clone line
      • enter Set-ExecutionPolicy Unrestricted
        • with your Keyboard
          • press ENTER
  1. In the Execution Policy Change window
    • select Yes to All
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\Lab 1. Troubleshooting Instant Clone> line
    • enter .\
      • with your Keyboard
        • select the down arrow
          • select delete_replica_folder.ps1
            • press ENTER
            • press ENTER
  1. In the Security Warning window
    • select Run once
  1. In the Windows PowerShell ISE - Input window
  1. In the Windows PowerShell ISE window
    • Read the TERMS of USE of this script
      • choose your response to the terms terms and conditions
        • enter either Yes to agree or No to disagree

If you agree you can continue with this Lab

  1. In the Windows PowerShell ISE window
    • When prompted "Do you want to continue? (y/N):
      • enter y
      • with your Keyboard
        • press ENTER
  1. In the Windows PowerShell ISE window
    • PS C:\scripts\Lab 1. Troubleshooting Instant Clone> line
    • enter .\
    • with your Keyboard
    • select the down arrow
      • select shutdown_vms.ps1
        • press ENTER
        • press ENTER
  1. In the Security Warning window
    • select Run once
  1. In the Windows PowerShell ISE - Input window
  1. In the Windows PowerShell ISE window
    • Read the TERMS of USE of this script
      • choose your response to the terms terms and conditions
        • enter either Yes to agree or No to disagree

If you agree you can continue with this Lab

  1. In the Windows PowerShell ISE - Input window
    • when prompted
      • Do you want to continue? (y/N):
        • with your keyboard
          • Enter y

Give yourself five minutes before moving on the next section

Expand or collapse content Section 3. Understanding preparing and resolving the Issue
  1. On  your ControlCenter Server
    • Site 1 - Bangalore browser
      • In the vSphere client session
        • Host & Clusters inventory
        • if necessary
          • expand vcenter-01a.techseals.co
          • expand the Region01A Datacenter
          • expand the Bangalore Cluster

In the vCenter inventory note that one of the cp-replica- * vms is ( inaccessible )

Notice in the Inventory RDS-Farm-1 & RDS-Farm-2 are powered Off

  1. In the vSphere Client Inventory
    • at the bottom of the window
      • below Recent Tasks
  • Notice
    • below Task Name > Power on virtual machine
    • below Target > RDSFarm-1 & RDSFarm-2
    • below Status > Unable to enumerate all disks. A required file was not found

A typical scenario might be hardware failure.
Having Instant  CloneTechnology, we are able to redeploy and repair , we have the RDS-Master available so redeploying the farm and getting the Farm up and running is not a problem.

However, doing this with the existing old hierarchy in place will cause the provisioning to fail

We therefore need to do the following

  1. Disable provisioning in the Pool
  2. Clean out the old hierarchy
  3. Re-enable provisioning

 

Expand or collapse content Step 1. Disabling Pool Provisioning
  1. On your Controlcenter server
    • Site 1 - Bangalore browser
      • In the Horizon login
        • in the username area
          • enter administrator
        • in the password area
          • enter Pa$$w0rd
      • enter SIGN IN
  1. In the Horizon Admin Console
    • side Menu Pane > Inventory area
      • select Farms
  1. In the Horizon Admin Console
    • Farms area
      • next to RDS-Farm-BLR
        • select the check box
      • select EDIT
  1. In the Edit Farm - RDS-Farm-BLR area
    • select the Provisioning Settings tab
  1. In the Edit Farm - RDS-Farm-BLR area
    • Provisioning Settings tab
      • next to Enable Provisioning
        • uncheck the checkbox
      • to close the Edit Farm - RDS-Farm-BLR  window
        • select OK
Expand or collapse content Step 2. Cleaning out the unwanted hierarchy using the Horizon Fling Tools

Overview of objective we want to achieve

  • We have a Replica-VM and Template-VM (Yellow) that are associated with the RDS Server Farm
  • This needs to be cleaned out.
    • We will use the Horizon Fling tool to validate this below diagram
  • Then remove the unwanted elements in the hierarchy.
  1. On the ControlCenter server
    • from the Task bar
    • select and open the File Explorer icon
  1. In the File Explorer window
    • browse to c:\scripts > Lab 1. Troubleshooting Instant Clone
  1. In the File Explorer window
    • c:\scripts > Lab 1. Troubleshooting Instant Clone folder
      • select and right-click Instant-Clone Associated-VMs.exe
        • from the dropdown
          • select Run as administrator
  1. In the Windows protected your PC window
    • select More info
    • select Run anyway

give the app about 30 seconds to load, monitor your Taskbar

  1. In the  Horizon Instant Clone Associated VMs  window
    • we are first going to Generate a report
      1. In the Horizon Connection Server area
        • next to Connection Server FQDN
          • enter horizon-01a.techseals.co
        • next to Horizon Admin Username
        • next to Horizon Admin Password
          • enter Pa$$w0rd
      2. In the vCenter Server area
        • next to vCenter Server FQDN
          • enter .vcenter-01a.techseals.co
        • next to vCenter Admin Username
        • next to vCenter Admin Password
          • enter Pa$$w0rd
      3. select Start
  1. In the  Horizon Instant Clone Associated VMs  window
    • select Generate Report
  1. On your Control Center server
    • In the How do you want to open this file? window
      • select Chrome
      • select OK
  1. On your Control Center server
    • Note the RDS Farm BLR row.
      • the cp-template GUID and the cp-replica GUID
        • matches what we have in the screenshot below
    • Below Unused VM's
      • note your GUIDs with our original screenshot
    • We will now use the Horizon Instant Clone Associated VM's tool  to clean out these elements from vCenter
  1. On your Horizon Instant Clone Associated VMs report
    • Select and highlight the  RDS-Farm-BLR row / CP-Replica Column
      • from the dropdown
        • select Copy
  1. On the ControlCenter server
    • from the Task bar
      • select and open the File Explorer icon
  1. In the File Explorer window
    • browse to c:\scripts
      • In the c:\scripts folder
        • select and right-click
          • from the dropdown
            • select New > Text Document
              • rename the txt document to Scripts.txt
  1. In the c:\scripts folder
    • select and right-click Scripts.txt
      • from the dropdown
        • select Open
  1. In the Scripts.txt file
    • paste your cp-replica GUID

leave the Scripts.txt file open

  1. On your Horizon Instant Clone Associated VMs report
    • Select and highlight the  RDS-Farm-BLR row / CP-Template column
      • from the dropdown
        • select Copy
  1. In the Scripts.txt file
    • paste your cp-template GUID
  1. On your Horizon Instant Clone Associated VMs report
    • below Unused VM's
    • select and right click the  cp-replica-GUID
      • from the dropdown
        • select Copy
  1. In the Scripts.txt file
    • on a new line
      • paste your Unused VMs cp-replica GUID
  1. On your Horizon Instant Clone Associated VMs report
    • below Unused VM's
    • select and right click the  cp-template-GUID
      • from the dropdown
        • select Copy
  1. In the Scripts.txt file
    • on a new line
      • paste your Unused VMs cp-template GUID
    • select File > Save
  1. In the vSphere Client
    • select the esxi.techseals.co host and right-click
      • from the dropdown
        • select Maintenance Mode > Exit Maintenance Mode
  1. In the  Horizon Instant Clone Associated VMs  window
    • in the top-right corner
      1. next to Delete VM's
        • select the radio button
      2. below Text File Path
        • Browse to C:\scripts\Scripts.txt
      3. select Start

you will notice your vCenter server credentials are retained

  1. In the  Horizon Instant Clone Associated VMs  window
    • next to ALL
      • select the checkbox
        • select Delete VM's
  1. In the vSphere Client
    • note what the VM hierarchy looks like now in relation before
    • Its only the Linux Pool and the Windows 11 Pool hierarchies that remain
Expand or collapse content Step 3. Cleaning out vCenter RDS servers and Horizon RDS elements
  1. On your Controlcenter server
    • Site 1 - Bangalore browser
      • from the Favourites bar
        • select the vcenter-01a shortcut
  1. In the vSphere client
    • in the username area
    • in the password area
      • enter Pa$$w0rd
    • enter LOGIN
  1. In the vSphere client
    • Host & Clusters inventory
      • expand vcenter-01a.techseals.co
      • expand the Region01A Datacenter
      • expand the Bangalore Cluster

Notice in the Inventory RDS-Farm-1 & RDS-Farm-2 are powered Off

These are still from the previous deployment

  1. In the vSphere Client inventory
    • select and right-click RDS-Farm-1
      • in the dropdown
        • select Remove from Inventory
      • in the Confirm Remove window
        • select YES

Repeat the Task for RDS-Farm-2

  1. In the vSphere client
    • select the Datastores Icon
  1. In the vSphere client
    • select the Datastores Inventory
      • select CorpLun-01a
  1. In the CorpLun-01a area
    • select the Files tab
    • In the Files area
      • left Inventory pane
        • next to CorpLun-01a
          • select the expand icon
      • in the Overview area
        • in front of RDS-Farm-1 and RDS-Farm-2
          • select the checkboxes
        • in the top right corner
          • select Delete
      • in the Confirm Deletion window
        • select OK
  1. On your Controlcenter server
    • Site 1 - Bangalore browser
      • In the Horizon login
        • in the username area
          • enter administrator
        • in the password area
          • enter Pa$$w0rd
        • enter SIGN IN
  1. In the Horizon Admin Console
    • side Menu Pane > Inventory area
      • select Farms
  1. In the Horizon Admin Console
    • Farms area
      • select RDS-Farm-BLR
  1. In the RDS-Farm-BLR area
    • select the RDS Hosts tab
  1. In the RDS-Farm-BLR area
    • RDS Hosts tab
      • next to DNS Name
        • select the checkbox
      • select REMOVE FROM FARM
  1. In the Remove RDS Host window
    • select OK
Expand or collapse content Step 4. Re-enabling Pool Provisioning
  1. In the Horizon Admin Console
    • side Menu Pane > Inventory area
      • select Farms
  1. In the Horizon Admin Console
    • Farms area
      • next to RDS-Farm-BLR
        • select the check box
      • select EDIT
  1. In the Edit Farm - RDS-Farm-BLR area
    • select the Provisioning Settings tab
  1. In the Edit Farm - RDS-Farm-BLR area
    • Provisioning Settings tab
      • next to Enable Provisioning
        • check the checkbox
      • select OK
  1. In the vSphere Client
    • Hosts & Clusters Inventory
    • Recent Tasks
      • note that a new cp-template and cp-replica are being created
      • note the GUID ID of your cp-template and cp-replica for future reference

Don't wait too long or else you will loose the opportunity to note this information

After about 5 minutes

  1. In the vSphere Client
    • Host & Clusters inventory
      • note that your RDS Servers are now deployed
  1. In the Horizon Admin console
    • under Farms > RDSFarm_BLR
      • select the RDS Hosts tab
      • scroll to the right of the middle pane and observe the Status
      • Do you notice that both RDS servers are now Available
  1. In the vSphere Client
    • Host & Clusters inventory
      • note that your RDS Servers are now deployed
      • Also note you have a new VM hierarchy in your Inventory.
      • Compare it to what you had originally

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.