Category:

Omnissa Horizon

Omnissa Horizon

Omnissa Horizon Upgrade 2406 to 2412

by Tommy Grot
written by Tommy Grot 2 minutes read

Omnissa Horizon has established itself as a leading solution for Virtual Desktop Infrastructure (VDI) and Desktop-as-a-Service (DaaS) environments. Building on the success of its predecessor, the Horizon 2406, we are excited to announce the release of the Horizon 2412 upgrade. This latest iteration offers a range of enhancements designed to further improve performance, scalability, and manageability for organizations leveraging VDI and DaaS solutions. With advanced features and improved capabilities, the Omnissa Horizon 2412 is poised to deliver even greater value to users, administrators, and IT professionals alike

Lets Upgrade!

  • Take a Snapshot of your Horizon Connection Server
  • Copy the Omnissa-Horizon-Connection-Server-x86_64-2412-8.14.0-12990578933.exe to your Horizon Connection Server.

Next ->

Your preference to join the CEIP -> Next

Install!

Follow up on the New Documentation site on Omnissa’s Site

New Look! For the Admin Login, really clean and streamlined and snappy interface I must say!

Now, that the Horizon Connection server is upgraded, we will now upgrade the Agent on our Image for our Pool, if you have a non-persistent image then you will need to unpack your template and update the gold image, but for my deployment I have persistent so I updated the VM it self.

Agent Upgrade

Next ->

Depending on your Deployment I would stick with IPv4 if you do not have IPv6 Routing capabilities.

Select your features you want enable on the Image.

Install!

Now we will re-deploy my Unified Access Gateway with the same IP address and configuration as my old 2406, but before turning off and removing the old UAG I exported my json file of my configuration to re-import it into the new 2412 UAG.

Login! with the credentials you setup during the OVA deployment.

Now we will Import the settings, so when you import the json file you will need to also re-import your certificate file, mine is a PFX and reapply it because after the import and reboot of the Horizon Connection and UAG I kept running into this error, and it was due to that the certificate was not imported within the json file and it needed a re-import. After reboot and all I was able to login!

Really nice and clean UI of the new Horizon 2412 Upgrade!

0 comments 1.2K views
0 FacebookTwitterLinkedinThreadsBlueskyEmail
Omnissa Horizon

VMware Horizon 2303 – Deleting / Cleaning up Orphaned VMs / Templates

by Tommy Grot
written by Tommy Grot 1 minutes read

Tonight’s topic is about an issue I encountered with VMware Horizon 2303 and Instant Clone pool. I deleted an instant clone pool from Horizon View administration and it deleted it from Horizon, but my cluster was throwing an vSAN error that it could not delete. So, what I had to do is go into the Horizon Connection Server and use the iccleanup.cmd utility.

Connect to your Horizon Connection server via RDP

Then go to ->

C:\Program Files\VMware\VMware View\Server\tools\bin

While you have this Explorer window open, a little shortcut to change directory and open Command Prompt, just type in CMD

iccleanup.cmd -vc <your-fqdn-vcsa> -uid [email protected] -skipCertVeri

Ensure to skip certificate verification if using self signed certs, sometimes may cause connection issues.

Next you will enter command “list”

Next, you will have the option to do the following: (unprotect/delete/output/back) – For my situation, I unprotected the cp-template that was orphaned and causing issues by defining the index number.

Then I ran the delete command and it found few more templates from a previous VDI Instant Clone pool and it removed all orphaned templates and VMs!

0 comments 5.6K views
0 FacebookTwitterLinkedinThreadsBlueskyEmail
Omnissa Horizon

Removing Invalid Instant Clones / Horizon Pool

by Tommy Grot
written by Tommy Grot 3 minutes read

A quick tip for the day, if you encounter any issues with your Horizon platform and you bring it back up from a backup or any other issues, and you see that some Instant Clones are missing, no worries you will need to do few things to clean up your Horizon View, with the ViewDbChk and ADSI Edit.

First step, login to your Horizon server. Once you are logged in you will need to open ADSI Edit and run these commands specifically.

Right click on ADSI Edit -> Connect To

EXACTLY Fill it out like I have it, or you will run into issues or corrupt something else. Once it is all filled out, click OK.

Name: Horizon View ADAM
Connection Point: DC=vdi, DC=vmware, DC=int
Computer: localhost:389

Now you see that you are connected to the ADAM database and you will now drill down to the specific areas.

First you want to remove the specific Horizon Pool(s) Ex. My Lab Horizon server has two Pools Download Desktop, Remote Desktop. These are both test pools. Be very CAREFUL to make sure you delete the proper CN=HORIZON_POOL.

After the desktop pool objects within the OU=Applications are deleted, you will want to delete the corresponding CN=HORIZON_POOL in the OU=Server Groups, this I have noticed wouldn’t let me rebuild the Horizon Pools with the previous name. After the OU=Server Groups have been removed it worked and let me create a new pool.

Next steps, is to run the viewdbchk.cmd, you will have to execute this from Command Prompt, you will not be able to just click on the .cmd file. Below I have provided the path so you may copy it and paste it in Command Prompt, ran as Administrator.

cd C:\Program Files\VMware\VMware View\Server\tools\bin

Once the script is ran you will see syntax and switches to use. I have provided a table of all them.

ViewDbChk --findDesktop --desktopName <desktop name> [--verbose]
   Find a desktop pool by name.
ViewDbChk --enableDesktop --desktopName <desktop name> [--verbose]
   Enable a desktop pool.
ViewDbChk --disableDesktop --desktopName <desktop name> [--verbose]
   Disable a desktop pool.
ViewDbChk --findMachine --desktopName <desktop name> --machineName <machine name> [--verbose]
   Find a machine by name.
ViewDbChk --removeMachine --machineName <machine name> [--desktopName <desktop name>] [--force] [--noErrorCheck] [--verbose]
   Remove a machine from a desktop pool.
ViewDbChk --scanMachines [--desktopName <desktop name>] [--limit <maximum deletes>] [--force] [--verbose]
   Scan all machines for problems. The scan can optionally be limited to a specific desktop pool.
ViewDbChk --help [--commandName] [--verbose]
   Display help for all commands, or a specific command.

First, you will need to find the pool you want to operate on. But for this tutorial we will be removing the desktop pool. So you will need to scan for it

ViewDbChk --findDesktop --desktopName <desktop name> --verbose

Once you have found your Desktop Pool you want to scan, this will also delete the entry if the Virtual Machine is orphaned or no longer existing. If you encounter other issues, you will need to use the –force switch to forcefully remove the pool, but in my scenario I was able to remove a large pool of Instant Clones in the last image.

ViewDbChk --scanMachines --desktopName <desktop name> --limit <maximum deletes>  --verbose

That is it! If you were able to remove all the Virtual Machines that were stuck in the Horizon View, now you are able to re-use or create a new pool even with the same name!

0 comments 3.7K views
0 FacebookTwitterLinkedinThreadsBlueskyEmail