Dan White

I have an open ticket. I will post the results, in hopes it helps someone in the future

@VDINinja3 Thanks for that info! I was wondering where the images went after I migrated to Next-Gen. I am running into a new issue... My images were created in USWest3. I am able to publish them to both regions with the republish command. Now when I clone the image (as a version or image), I can only clone it to USWest3. I will be decommissioning USWest3 as a capacity provider. I will need to be able to manage the images from my new capacity, USWest2. Any ideas on how to accomplish that, short of building new images? Thx, Dan

I believe I have stumbled upon the answer myself. You go into the image and republish. You can then publish the image to multiple Edges: There does not seem to be an easy way to list where all the images are published. You need to click each image individually.

I am in the process of moving our Horizon Cloud service from one Azure region to another. I opened a case some time ago about the process and I don't believe many people have attempted this. The basic steps from the case: Create a new provider Deploy a new Edge Create new pools Decommission old pools Decommission old Edge Decommission old Provider I have completed steps one and two. The Issue now is I have some heavily customized imaged that I need to deploy to pools in the new region. I was under the assumption that images in Next-Gen were universal and could be deployed to any infrastructure. This is not the case. It appears that the images are locked to one Provider/Edge. I have a couple of questions: Is it possible to allow an image to be deployed to multiple Providers/Edges? Can you "clone" an image to a new Provider/Edge? How do you tell what Provider/Edge an image is tied to? This appears to only be visible when creating an image Thanks in advance, Dan

Yes, it appears this is now available within the console: This is a great improvement with the latest release!

@Lola Groppi It was just me and a technician from the Horizon team. It was smooth, once the console came back on line.

@Lola Groppi The onboarding went well, other than the fact that we were in the middle of the migration when Broadcom decided to cut over the administration console over to Omnissa. This caused a bout a 2 hour delay in completion.

@Lola Groppi 1) I have been using the Horizon Cloud Console Next-Gen for approx. 3 months. Horizon Cloud First-Gen 2+ years and Horizon Connection Server for about 4 years. 2)I would like to think I am somewhere around "advanced" level of expertise. I can hold my own with the top-level support and know the Horizon Cloud architecture pretty well. We have had a couple of bad outages that pulled me deeper into the architecture than most customers. 3)Not a bad thing, it mostly runs itself (which is what we like). Lately, I am working on bringing my pools up to Windows 11. This means that I have to spend more time in the console than normal. I am an old school scripter. I like to automate mundane tasks, as much as possible. Brining a new OS in means that I have to create a bunch of manual applications/entitlements. In Next-Gen, you currently cannot edit a published app. It is very frustrating when you are trying to make minor changes. You can only delete and recreate the app. This is why I would like to script such things. I had a look at the REST API and it appears that there is no publishes API method to create a new manual application.

Hopefully this will help someone in the future. I found this article that had an example of how to access the REST API from PowerShell: https://techzone.omnissa.com/blog/getting-started-horizon-cloud-service-next-gen-supported-rest-apis-powershell Here is a basic script that I have that will return information on the pools: #Authenticate $Url = "https://connect.omnissa.com/csp/gateway/am/api/auth/api-tokens/authorize" $APIToken = "YOUR API TOKEN HERE" #Expires every 6 months $params = @{refresh_token = $APIToken} $Connection = Invoke-WebRequest $url -Method Post -Body $params -UseBasicParsing | ConvertFrom-Json $Token = $Connection.access_token #Setup Headers $Headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]" $Headers.Add("Authorization", "Bearer $Token") $Headers.Add("Accept","application/json, text/plain, */*") #Get Pool Data $Url = "https://cloud.vmwarehorizon.com/portal/v2/pools" $Pools = Invoke-WebRequest $url -Method Get -Headers $Headers -UseBasicParsing | ConvertFrom-Json $pools.content | Select name,DisplayName,Type It's disappointing that the code insertion feature of this forum doesn't support PowerShell 😞 As stated above, here is the link to the full REST API documentation: https://developer.omnissa.com/horizon/apis/horizon-cloud-nextgen/#api Hope that helps

@Lola Groppi Literally all features were moved, between Gen-One and Next-gen. It was a complete rewrite, so that is to be expected I suppose. It generally takes a little longer to locate things that are not used that often. We are a very small installation. We have 50 concurrent user licenses with an average of 20 users at any given time. Things like separating the pools and pool groups don't really make sense in my environment. We will never be big enough to need multiple pools in a group, for capacity. I understand why it was architected that way, but only the largest customers would need that. Having the pool groups makes it a little clunky to entitle apps to users. Gen-One and Horizon on prem were managed very similarly, so administrators could easily translate skills. I have been on Next-Gen for a couple months. I assume it will eventually become second nature. Day to day, I spend about an hour doing tasks in the console. Supporting Horizon is only one piece of my job description. For repetitive tasks, the big one for me is publishing manual apps. I have about 40 VNC connections I would like to publish. Doing them manually would be ruthless. I would like to script the creation and maintenance of those links. In the on-prem world, we would just use PowerCLI. It doesn't work with Horizon Cloud. I could publish dozens of manual applications in seconds. I did start another thread asking about PowerShell support and was told I could use the REST Api. I am an administrator and not a programmer, so manipulating REST is not my forte. I am trying to get a handle on it, but the documentation is very sparse with examples.

I spend most of the time looking for features that are missing or moved in the Next-Gen console. 🙂 Most of my administration is performed from the Horizon Cloud Console (https://cloud.horizon.vmware.com/hcsadmin). It is a shame that you have to click to another console for the performance reporting with Intelligence. It now takes 3 clicks and is not that intuitive for all users to get to. In my old on-prem versions of Horizon, I would heavily leverage PowerCLI/PowerShell to do most of the administration. I am just starting on the path on how to leverage the REST Api to script repetitive tasks.

Thanks for the reply. I was aware of the API documentation. I am not a developer, so I was hoping for an example of how to leverage the API with PowerShell

In the on-premises version of Horizon, we have the luxury of having the PowerCLI module to automate the infrastructure. This was particularly helpful when you have to publish dozens of manual applications. Is there anyway to extend this functionality to the cloud version? The current PowerCLI connections require a connection server, which we don't have in the cloud version. Is there a fast way to publish and assign 50ish manual applications quickly? Thx, Dan

In Next-Gen, have we lost the ability to drain users from a node? How do we go about changing the state of a node to stop new user sessions? Thx, Dan

Hi Guys, Is there any way to change the Pool Group type, after the pool group is created? I have some Pool Groups that were created as part of the migration. I would like to keep these pool groups, as all my entitlements are based off of them. These entitlements would be a pain to recreate and would cause me to have an outage for my users while I create a new Pool Group, entitlements, etc. I would like this Pool Group that is Published Desktop & Application: Thx, Dan