RoderikdeBlock's Accepted Solutions

I think this is because of Smart Provisioning :   Horizon 8 (2006) also adds new functionality to instant clones. Smart provisioning is now available, which will create parentless instant-clone pools for clusters with density at or below 12 VMs per host. Parent VMs are created otherwise, and they are a running clone of the replica VM snapshot.

I am having simular issues and just found this comment on -->  Comments | VMware Flings  : "We discussed this today and this is probably related to another setting. The Welcome screen is displayed for the amount of time allowed by this timer. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DelayedDesktopSwitchTimeout The issue is described in this MS article (it also applies to Windows 10 even though it only mentions Vista and Server 2008) https://support.microsoft.com/en-ie/help/940452/the-welcome-screen-may-be-displayed-for-30-seconds-and-the-logon-scrip If we leave this at a high value, then logons will always take at least that amount of time. E.g. If the timer is set to 30 seconds, even if all processing has been done in 10 seconds and the desktop is really ready, the user wouldn't get access until at least the 30 second count. We want the delay to be a short as possible so that the session is switched from logon to the other processes that happen at logon. The downside is that the Welcome screen is only displayed during the logon session and a black screen is then displayed when other processing is happening. The duration of the other processes and therefore the black screen can be affected by things like antivirus processing, GPO, App Volumes mounting operations, etc." I hope this is usefull for your issues!

You could give it a try using PowerCLI: Connect-HVServer -Server <Your HV Server> $ViewAPI = $global:DefaultHVServers[0].ExtensionData $query_service = New-Object "Vmware.Hv.QueryServiceService" $query = New-Object "Vmware.Hv.QueryDefinition" $query.queryEntityType = 'SessionLocalSummaryView' $Sessions = $query_service.QueryService_Query($ViewAPI,$query) $Sessions.Results.Namesdata This will give you the following output.

Hi, You can fix this issue by creatiung a locked.properties file in this directory: "C:\Program Files\VMware\VMware View\Server\sslgateway\conf". Add this line: checkOrigin=false More information about this issue can be found in this KB article: VMware Knowledge Base

1Does the VCenter this cluster is connected to, need to be a separate VCenter, dedicated to Horizon and the Cluster? It doesn't have to be a separate vcenter but it is a best practice. Horizon wil create a lot of noise in the vCenter while it's creating/destroying/cloning all the time. 2 If so, Does that VCenter need to be running on that cluster or can it actually reside on my normal Server Cluster which is a traditional build HPE server cluster? vCenter can run in another cluster with your other servers. 3 Are there any pre-built server OVFs/Appliances that can be downloaded for all the individual pieces of Horizon? Do I need to hand build the servers? I can't seem to find any. Similiar to VCenter    Appliance. Horizon Connection and composer server have to be installed on a Windows server. You will also need an SQL server for your event database or composer database if you are planning to use Linked Clones. 4 Is Windows Server 2019 compatible for those individual server pieces? Windows Server 2019 is supported with Horizon Connection Server 7.8 and newer. 5 Does anyone know of a good step by step guide to installing and deploying Horizon? Carl Stalhood describes on his website how to setup Horizon step by step. https://www.carlstalhood.com/vmware-horizon-7-connection-server/

Horizon 7 provides proxy support for the VMware Identity Manager (vIDM) server. The proxy details such as hostname and port number can be configured in the ADAM database and the HTTP requests are routed through the proxy. This feature supports hybrid deployment where the on-premise Horizon 7 deployment can communicate with a vIDM server that is hosted in the cloud. Prerequisites Procedure Start the ADSI Edit utility on your Connection Server host. Expand the ADAM ADSI tree under the object path: cd=vdi,dc=vmware,dc=int,ou=Properties,ou=Global,cn=Common Attributes. Select Action > Properties, and add the values for the entries pae-SAMLProxyName and pae-SAMLProxyPort

As far as I know this isn't possible. According to the documentation these are your options: You can place the automatically generated number anywhere else in the name by using a token. When you type the pool name, type n surrounded by curly brackets to designate the token. For example: amber-{n}-desktop When a machine is created, Horizon 7 replaces {n} with a unique number. You can generate a fixed-length token by typing {n:fixed= number of digits } . Horizon 7 replaces the token with numbers containing the specified number of digits. For example, if you type amber-{n:fixed=3} , Horizon 7 replaces {n:fixed=3} with a three-digit number and creates these machine names: amber-001 , amber-002 , amber-003 , and so on. Length of the Naming Pattern When You Use a Fixed-Length Token Names that contain fixed-length tokens have a 15-character limit, including your naming pattern and the number of digits in the token.