INSTANT CLONE PROVISIONING IN VMWARE HORIZON

CREATING MASTER IMAGE

A master Image also known as a base image or a golden image is the most important part of the VDI deployment scenarios.

Create one VM as a master image, and Horizon 7 can generate a pool of virtual desktops from that image.

You can Use VMware optimization tool to optimize the golden image. If the image is not optimized, you will run into performance issues.The VMware OS Optimization Tool helps in preparing and optimizing Windows 10/8/7 and Windows Server 2019/2016/2012/2008 systems for use with VMware Horizon

The OS Optimization Tool includes customizable templates to enable or disable Windows system services and features, per VMware recommendations and best practices.

Now that the optimized Golden Image is ready, take a snapshot of the optimized Golden Image.  We will use that snapshot while creating Desktop Pools.

For more information about creating and managing snapshots in vSphere Web Client, please refer to this link: https://kb.vmware.com/s/article/2032907

CREATING DESKTOP POOL

A desktop pool is a collection of desktops that users select when they log in using the View client

There are two main types of virtual desktop pools: automated and manual.

Automated desktop pools use a vCenter Server virtual machine template or snapshot to create a pool of identical virtual machines.

Manual desktop pools are a collection of Server virtual machines, physical computers, or third-party virtual machines. In automated or manual pools, each machine is available for one user to access remotely at a time

For more information on creating Instant-Clone Desktop Pools visit: https://docs.vmware.com/en/VMware-Horizon-7/7.9/horizon-console-administration/GUID-C450DD3D-AB0B-4B24-8981-ED6C4D1B9148.html

As soon as we create the desktop pools and enable provisioning, the process of creating the template from the associated snapshot starts. Once the template is created, it remains in the powered off state and resides in the same cluster as the Golden VM. The nomenclature of the Template is defined and the name of the template will be cp-template*followed by digits*

The next step after the creation of template is creation of a Replica VM. Replica VM also remains in power off state. Each replica is created per Datastore basis that means there will be one replica VM per Datastore. Similar to Template, the nomenclature of the Replica VM is defined and the name of the template will be cp-replica*followed by digits*

The last part of the PRIMING stage is marked by the creation of parent VM starts. It is important to remember that the parent VM is in powered ON state and single parent VM is created per ESXI host per Datastore.

Parents VM loads the OS in the memory and sets up the shared area. Since the parent is powered ON, it will create a shared memory location. Immediately after that if forks off itself to create Instant Clone.

This ends the PRIMING stage in the instant clone provisioning process. The PRMING stage starts with the template creation up to the point when the Parent forks off itself to create the Instant Clone. Priming is the most time consuming part. It takes around 20-30 minutes.

The instant clone will then read from the shared memory and replica VM. Instant clone becomes a unique memory location with unique identity of its own, including a MAC address, UUID, and other system information.

Instant clones require less storage and less expense to manage and update because the desktop is deleted when the user logs out, and a new desktop is created using the latest master image.

I downloaded ccleaner to free up my ram and to get rid of some junk files. I ran ccleaner, tried to start my vmware and I got the error message "VMware Workstation failed to start the VMware Authorization Service. You can try manually starting the VMware Authorization Service. If this problem persists, contact VMware support." I shutdown my host / main pc, turned it back on and tried to start my vmware and I got this "Unable to find the VMX binary 'G:\VMWARE\vmware-vmx.exe'."

Can anyone suggest what to do here? Would a simple reinstalling fix this?

Both VM guests have one network adapter set to NAT.

The Kali (guest) machine has IP address 192.168.93.141, and the Windows 7 Pro machine is IP address 192.168.93.143. The windows firewall is turned off. I am doing some research, but cannot connect to the Windows machine (guest) from Kali. I can ping in both directions, but cannot connect. If I open a connection through the web browser to the Win 7 Pro machine, it does connect just fine.

Everything I have searched here and on Google describes connections between guest and host. Am I missing something? Is it a Windows 7 setting that I'm missing? The firewall is turned off.

.

Hello!

I am using Vcenter Converter Standalone (6.2.0-build8466193) to convert a rhel5.5 to a VM, I've checked the portgroups that needs to be avaiable (TCP/UDP:22;443;902;903;137;138), logging with root via ssh works fine, on Vcenter the VM is created, installed and keeps on converter screen at least for 2 hours, than the error is prompted (Error: Unable to connect to the Converter helper server on the destination virtual machine.). On the source the /tmp is on write

I checked the logs, but no known issued helped figure out what's wrong, could anyone help?

Hello guys!
I am struggling with a problem with low performance in my guest machine. I`ve got low FPS, "top" shows that xorg utilize 50-75% of CPU, when I switched to gnome its even worse - sometimes more than 100%. I have got disabled Accelerate 3D graphics checkbox in VM Settings. With enabled Accelerate 3D graphics the situation is better when nothing is running, when I try to work the screen becomes black on some places like buttons, bars, windows or places when windows are moving. The situation is not new, it was like that from the very beginning on that host.
On monitors section I have checked: Use host setting for monitors.
Its very difficult for me to make a screenshot for these blacked elements because when pressing printscreen, the screen is refreshing and everything looks fine.
My host specification:

Dell Tower 7910

Intel Xeon CPU E5-2640 v3 2.60 Ghz

64GB RAM

NVIDIA NVS310 with updated drivers (and second graphic card on USB - Fresco Logic IDDCX Adapter)
VMware Workstation Pro 15

My guest specification:
Kali Linux (Debian based), kernel 5.6.0 with newest tools installed.

I am wondering if there is a problem with my graphic card, which is very old NVS 310 and I dont have integrated graphic card. Working on that machine is very frustrating, especially since I have a much more better performence on my notebook or others, theoretically worse hosts. I am also ready to buy new graphic card if its necessary, but first I would like to ask you guys.

I am read to provide you with any logs you want to, any help would be appreciated.

Hi All

I am testing nsx-t 3.0 and deep security agentless. At present,

the VM needs to be added to the group manually to configure it to deep security.

Is there any setting that can automatically add the newly created VM to the group?

Thanks.

vRA 8.x -  There is supposed to be abeta build for vRealize Orchestrator Plugin for vSphere HTML5 Client. 1. What is the link to this Plug-in ? 2. Also if there is an official date for the release for it ?

It appears that any tests I try to create, Local or Remote fail instantly with "Failed to start Infra server data collection".

The harness log suggests it is failing when it tries to obtain host statistics/info.

Can anyone clarify what rights the vCenter account needs to have?

Kind regards, James

view planner 4.4

chrome 81.0.4044.138

None of chrome's actions are performed.

Can anyone please help here..

# RUN TestRun: Preparing . . . . .

# RUN TestRun: Starting . . . . .

# WORKGROUP WorkGrp: Failed to fetch Optimization workload

# WORKGROUP WorkGrp: Searching for 1 desktop(s).

# Could not find VM's in pool for pattern C-VM-001, Error code 501

# WORKGROUP WorkGrp: Required desktop(s) are not available, found 0, expected 1

# RUN TestRun: WorkGroup failed, Error code: 24

# RUN TestRun: Generating report . . . . .

# RUN TestRun: Failed !

#_

Here is the log..

2020-04-28 01:38:57,611 DEBUG harnessCore.database.db_query.py - getVDIServer_list exit

2020-04-28 01:38:57,612 DEBUG shared.util_harnessCache.py - _createViewObject enter

2020-04-28 01:38:57,613 DEBUG harnessCore.VDI.ViewInterface.py - View __init__ entry

2020-04-28 01:39:01,674 DEBUG harnessCore.VDI.ViewInterface.py - View __init__ exit

2020-04-28 01:39:01,701 DEBUG harnessCore.VDI.ViewInterface.py - View login enter

2020-04-28 01:39:02,094 DEBUG harnessCore.VDI.ViewInterface.py - View login exit

2020-04-28 01:39:02,100 DEBUG shared.util_harnessCache.py - _createViewObject exit

2020-04-28 01:39:02,101 DEBUG shared.util_harnessCache.py - getVDIServer exit

2020-04-28 01:39:02,101 DEBUG harnessCore.VDI.ViewInterface.py - isInstantClonePool entry

2020-04-28 01:39:02,102 DEBUG harnessCore.VDI.ViewInterface.py - getPoolInfofromPattern entry

2020-04-28 01:39:02,270 ERROR suds.umx.typed - Schema:0x7f87a8597dd8

(raw)

  <schema/>

(model)

2020-04-28 01:39:02,288 ERROR harnessCore.VDI.ViewInterface.py - getPoolInfofromPattern failed to get pool info, Exception Type not found: 'allowMultipleAssignments'

2020-04-28 01:39:02,307 DEBUG harnessCore.VDI.ViewInterface.py - isInstantClonePool exit

2020-04-28 01:39:02,333 DEBUG harnessCore.run.workGroup.py - WorkGroup: _isDesktopInstant exit: False

2020-04-28 01:39:02,339 DEBUG harnessCore.database.db_query.py - getWorkload_list enter

2020-04-28 01:39:02,346 DEBUG harnessCore.database.db_query.py - queryHandler enter

2020-04-28 01:39:02,352 DEBUG harnessCore.database.db_adapter.py - dbAdapter : query enter

2020-04-28 01:39:02,358 DEBUG harnessCore.database.db_adapter.py - dbAdapter: acquireConnection enter

2020-04-28 01:39:02,364 DEBUG harnessCore.database.db_adapter.py - dbAdapter query exit

2020-04-28 01:39:02,364 DEBUG harnessCore.database.db_query.py - queryHandler exit

2020-04-28 01:39:02,364 DEBUG harnessCore.database.db_query.py - getWorkload_list exit

2020-04-28 01:39:02,364 DEBUG shared.harness_util.py - STATUS: WORKGROUP WorkGrp: Failed to fetch Optimization workload

2020-04-28 01:39:02,364 DEBUG harnessCore.run.workGroup.py - WorkGroup: _calculateMinimumRequiredVMCount enter

2020-04-28 01:39:02,365 DEBUG harnessCore.run.workGroup.py - WorkGroup: _calculateMinimumRequiredVMCount exit

2020-04-28 01:39:02,365 DEBUG harnessCore.database.db_query.py - insertHarnessOpData enter

2020-04-28 01:39:02,365 DEBUG harnessCore.database.db_query.py - queryHandler enter

2020-04-28 01:39:02,365 DEBUG harnessCore.database.db_adapter.py - dbAdapter : query enter

2020-04-28 01:39:02,365 DEBUG harnessCore.database.db_adapter.py - dbAdapter: acquireConnection enter

2020-04-28 01:39:02,367 DEBUG harnessCore.database.db_adapter.py - dbAdapter : No result set to fetch from

2020-04-28 01:39:02,375 DEBUG harnessCore.database.db_adapter.py - dbAdapter query exit

2020-04-28 01:39:02,376 DEBUG harnessCore.database.db_query.py - queryHandler exit

2020-04-28 01:39:02,376 DEBUG harnessCore.database.db_query.py - insertHarnessOpData exit

2020-04-28 01:39:02,376 DEBUG shared.harness_util.py - STATUS: WORKGROUP WorkGrp: Searching for 1 desktop(s).

2020-04-28 01:39:02,376 DEBUG harnessCore.run.VMAgentFactory.py - scaleVMPool enter

2020-04-28 01:39:02,377 DEBUG shared.util_harnessCache.py - getInfraServer enter

2020-04-28 01:39:02,377 DEBUG shared.util_harnessCache.py - getInfraServer exit

2020-04-28 01:39:02,380 DEBUG shared.util_harnessCache.py - getVDIServer enter

2020-04-28 01:39:02,380 DEBUG harnessCore.database.db_query.py - getVDIServer_list enter

2020-04-28 01:39:02,381 DEBUG harnessCore.database.db_query.py - queryHandler enter

2020-04-28 01:39:02,381 DEBUG harnessCore.database.db_adapter.py - dbAdapter : query enter

2020-04-28 01:39:02,382 DEBUG harnessCore.database.db_adapter.py - dbAdapter: acquireConnection enter

2020-04-28 01:39:02,434 DEBUG harnessCore.database.db_adapter.py - dbAdapter query exit

2020-04-28 01:39:02,458 DEBUG harnessCore.database.db_query.py - queryHandler exit

2020-04-28 01:39:02,477 DEBUG shared.util.py - readBinaryFile enter

2020-04-28 01:39:02,540 DEBUG shared.util.py - readBinaryFile exit

2020-04-28 01:39:02,558 DEBUG shared.harness_util.py - AESCipher _init__ enter

2020-04-28 01:39:02,577 DEBUG shared.util.py - stringToBytes enter

2020-04-28 01:39:02,596 DEBUG shared.util.py - stringToBytes EXIT

2020-04-28 01:39:02,605 DEBUG shared.harness_util.py - AESCipher _init__ exitr

2020-04-28 01:39:02,605 DEBUG shared.harness_util.py - AESCipher decrypt enter

2020-04-28 01:39:02,605 DEBUG shared.harness_util.py - AESCipher Decrypt EXIT

2020-04-28 01:39:02,606 DEBUG shared.harness_util.py - AESCipher _unpad enter

2020-04-28 01:39:02,606 DEBUG harnessCore.database.db_query.py - getVDIServer_list exit

2020-04-28 01:39:02,607 DEBUG shared.util_harnessCache.py - _createViewObject enter

2020-04-28 01:39:02,608 DEBUG harnessCore.VDI.ViewInterface.py - View __init__ entry

2020-04-28 01:39:05,646 DEBUG harnessCore.controller.controller.py - getRunStatus enter

2020-04-28 01:39:05,689 DEBUG harnessCore.run.run.py - Run: getRunStatus enter

2020-04-28 01:39:05,788 DEBUG harnessCore.run.run.py - Run: getRunStatus exit

2020-04-28 01:39:05,852 DEBUG harnessCore.controller.controller.py - getRunStatus enter

2020-04-28 01:39:05,864 DEBUG harnessCore.run.run.py - Run: getRunStatus enter

2020-04-28 01:39:05,869 DEBUG harnessCore.run.run.py - Run: getRunStatus exit

2020-04-28 01:39:06,366 DEBUG harnessCore.VDI.ViewInterface.py - View __init__ exit

2020-04-28 01:39:06,377 DEBUG harnessCore.VDI.ViewInterface.py - View login enter

2020-04-28 01:39:06,565 DEBUG harnessCore.VDI.ViewInterface.py - View login exit

2020-04-28 01:39:06,593 DEBUG shared.util_harnessCache.py - _createViewObject exit

2020-04-28 01:39:06,617 DEBUG shared.util_harnessCache.py - getVDIServer exit

2020-04-28 01:39:06,640 DEBUG harnessCore.VDI.ViewInterface.py - getPoolNamefrompattern entry

2020-04-28 01:39:06,659 DEBUG harnessCore.VDI.ViewInterface.py - getPoolInfofromPattern entry

2020-04-28 01:39:06,786 ERROR suds.umx.typed - Schema:0x7f87b913e160

(raw)

  <schema/>

(model)

2020-04-28 01:39:06,820 ERROR harnessCore.VDI.ViewInterface.py - getPoolInfofromPattern failed to get pool info, Exception Type not found: 'allowMultipleAssignments'

2020-04-28 01:39:06,833 DEBUG harnessCore.VDI.ViewInterface.py - getPoolNamefrompattern exit

2020-04-28 01:39:06,873 DEBUG shared.harness_util.py - STATUS: Could not find VM's in pool for pattern C-VM-001, Error code 501

2020-04-28 01:39:06,897 DEBUG harnessCore.run.VMAgentFactory.py - _allocateVMAgents called with target count 1

2020-04-28 01:39:06,921 DEBUG shared.util.py - readConfigFile_int enter

2020-04-28 01:39:06,954 DEBUG shared.util.py - readConfigFile_int exit

2020-04-28 01:39:06,973 DEBUG harnessCore.run.VMAgentFactory.py - _allocateVMAgents exception Set of coroutines/Futures is empty.

2020-04-28 01:39:06,982 ERROR harnessCore.run.VMAgentFactory.py - scaleVMPool: Exception while allocating agents: Set of coroutines/Futures is empty.

2020-04-28 01:39:06,983 DEBUG harnessCore.run.VMAgentFactory.py - scaleVMPool exit

2020-04-28 01:39:06,983 DEBUG harnessCore.database.db_query.py - incrementDiscardedVMCount enter : TestRun

2020-04-28 01:39:06,984 DEBUG harnessCore.database.db_query.py - queryHandler enter

2020-04-28 01:39:06,984 DEBUG harnessCore.database.db_adapter.py - dbAdapter : query enter

2020-04-28 01:39:06,984 DEBUG harnessCore.database.db_adapter.py - dbAdapter: acquireConnection enter

2020-04-28 01:39:06,987 DEBUG harnessCore.database.db_adapter.py - dbAdapter : No result set to fetch from

2020-04-28 01:39:06,998 DEBUG harnessCore.database.db_adapter.py - dbAdapter query exit

2020-04-28 01:39:06,998 DEBUG harnessCore.database.db_query.py - queryHandler exit

2020-04-28 01:39:06,999 DEBUG harnessCore.database.db_query.py - incrementDiscardedVMCount exit

2020-04-28 01:39:06,999 DEBUG shared.harness_util.py - STATUS: WORKGROUP WorkGrp: Required desktop(s) are not available, found 0, expected 1

2020-04-28 01:39:07,000 DEBUG harnessCore.run.workGroup.py - WorkGroup: startWorkGroupRun exit

2020-04-28 01:39:07,000 DEBUG shared.harness_util.py - STATUS: RUN TestRun: WorkGroup failed, Error code: 24

2020-04-28 01:39:07,000 DEBUG harnessCore.run.run.py - Run: _stopInfraDataCollection enter

2020-04-28 01:39:07,001 DEBUG harnessCore.infra.vcenter.py - Stopping vCenter stats collection..

2020-04-28 01:39:07,002 DEBUG harnessCore.infra.vcenter.py - stopInfraDataCollection enter

2020-04-28 01:39:12,358 DEBUG harnessCore.infra.vcenter.py - collectAndDump exit

2020-04-28 01:39:14,625 DEBUG harnessCore.controller.controller.py - getRunStatus enter

2020-04-28 01:39:14,626 DEBUG harnessCore.run.run.py - Run: getRunStatus enter

2020-04-28 01:39:14,626 DEBUG harnessCore.run.run.py - Run: getRunStatus exit

2020-04-28 01:39:14,651 DEBUG harnessCore.controller.controller.py - getRunStatus enter

2020-04-28 01:39:14,652 DEBUG harnessCore.run.run.py - Run: getRunStatus enter

2020-04-28 01:39:14,652 DEBUG harnessCore.run.run.py - Run: getRunStatus exit

2020-04-28 01:39:17,364 DEBUG harnessCore.infra.vcenter.py - stopInfraDataCollection exit

2020-04-28 01:39:17,365 DEBUG harnessCore.run.run.py - Run: _stopInfraDataCollection exit

2020-04-28 01:39:17,366 DEBUG shared.harness_util.py - provideHtpdPermissions() : Enter

2020-04-28 01:39:17,366 DEBUG shared.harness_util.py - provideHtpdPermissions() : Exit

2020-04-28 01:39:17,367 DEBUG shared.harness_util.py - STATUS: RUN TestRun: Generating report . . . . .

2020-04-28 01:39:17,367 DEBUG harnessCore.run.run.py - Run::_setCompleteTimeStamp Enter

Having issue getting my first run underway.  I was able to get VMs spun up.  I did notice the VMs is not automatically logging in as Admin in until I intervene by  clicking CTL + ALT + DEL in console.  However, once run is initiated I get the following error.  Not sure what else to check.  I made VMs with Prefix VPLT, and entered VPLT into the Workload setup prefix.  I am figuring the VMs are found within vCenter.  However, I did ensure the VMs spun up can communicate to View Planner appliance over port 8080.  Any suggestion on additional test or diagnosis?

# RUN TEST: Preparing . . . . .

# RUN TEST: Starting . . . . .

# WORKGROUP TESTVP: Searching for 2 desktop(s).

# Could not find VM's in pool for pattern VPLT, Error code 501

# WORKGROUP TESTVP: Required desktop(s) are not available, found 0, expected 2

# RUN TEST: WorkGroup failed, Error code: 24

# RUN TEST: Generating report . . . . .

# RUN TEST: Failed !

I am pleased to announcegeneral availability of the VMware View Planner 4.5.

You can download the bits from: https://www.vmware.com/products/view-planner.html

Documentation and release notes can be accessed from https://docs.vmware.com/en/VMware-View-Planner/index.html

Hello,

I deployed a Windows 10 1809 image, with no fancy software installed - just Office. VMware tools stops running after a few minutes, and only way to remedy this is to reboot the VM, however VMware tools stops again. The VM itself becomes non-responsive. This does not happen with the master image within the console. The issue starts after deployment.

Using an older version of Windows 10, previous build, VMware tools stays running just fine.

Yes, the power settings are set to high performance, so this is not an issue with hibernation.

I have tried various versions of VMware tools also - including the latest.  Running the Horizon Agent 7.4.0. If I log into the master image at the VMware console prior to deployment, the VM runs fine with no issues. After de

Logs do not appear to display any information relevant to VMware tools stopping, and the event viewer on the VM itself does not display any errors either - Any suggestions?

123456

Hi, I tried to add my vSphere Host to vCenter, but This error occurred.  vSphere says "Failed - Cannot change the host configuration." How to fix this?

Hi Guys,

I need something to do with my ESXi host which is disable USB,

I did try google, but not found many information to disable the USB services, but i found something, it about  turn off USB arbitration, is this similar thing like we normally do in Windows GPO to disable USB?

Appreciate any input on this.

Thank you.

I'm extremely new to VMware...  kindly help me out....

Hi All,

Can you help me with our problem, Im new to Esxi. We have a DELL r720 in our company with a Esxi 4.1 (I inherited from the previous IT guy).

There was a power outage and the UPS did not suffice the time of outage.

After powering on, we got a n issue with our server DELL r720 iDRAC.

I applied the soft or hard reset but still IDRAC still no working, in short it FAILED.

I continue to load the  ESXi, but it cant load the "impi_si_drv"

I found some article to disable the module "impi_si_drv"

by using "Shift+O" and enter the command "noipmiEnabled"

but its not working

"boot: noipmiEnabled"
"could not find kernel image: noipmiEnabled"

please help.

Thank you.

We have a Horizon 7.9 environment running on ESXi, 6.7.0, 16075168. We are using NVIDIA GPU cards. We recently did the ESX upgrade and recompose of the VMs. Some of the users running on Windows 7 desktops are complaining about black screen issues, mostly when they are disconnected for a long time and then reconnects. Once they hit the black screen, they are unable to resolve it without rebooting the machine.

The logs show the below:

=====================

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0        MGMT_SYS :SESSION ACTIVE

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0      MGMT_VCHAN :Connect callback 0 accepted opening chan name=RDP__CARANOC

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling connect callback 1: event=OPEN cap=0x2 reject=0 flags=0x0 (RDP__CARANOC)

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0      MGMT_VCHAN :Connect callback 1 accepted opening chan name=RDP__CARANOC

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0      MGMT_VCHAN :Received OPEN_REQ request to open channel RDP__NLR3hv (peer_chan=1)

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> PEER_OPEN  (name=RDP__NLR3hv)

2020-05-28T21:45:50.873+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling connect callback 0: event=OPEN cap=0x3 reject=15876192 flags=0x0 (RDP__NLR3hv)

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Connect callback 0 accepted opening chan name=RDP__NLR3hv

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling connect callback 1: event=OPEN cap=0x3 reject=0 flags=0x0 (RDP__NLR3hv)

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Connect callback 1 accepted opening chan name=RDP__NLR3hv

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Received OPEN_REQ request to open channel RDP__NLW3hv (peer_chan=2)

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> PEER_OPEN  (name=RDP__NLW3hv)

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling connect callback 0: event=OPEN cap=0x4 reject=15876192 flags=0x0 (RDP__NLW3hv)

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Connect callback 0 accepted opening chan name=RDP__NLW3hv

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling connect callback 1: event=OPEN cap=0x4 reject=0 flags=0x0 (RDP__NLW3hv)

2020-05-28T21:45:50.874+10:00> LVL:2 RC:   0      MGMT_VCHAN :Connect callback 1 accepted opening chan name=RDP__NLW3hv

2020-05-28T21:45:50.879+10:00> LVL:2 RC:   0        MGMT_HDA :mgmt_hda_apdu_fcc_encode_and_send: Encoding MGMT_HDA_AUDIO_INPUT_CTRL_BOOST_ON message...

2020-05-28T21:45:50.879+10:00> LVL:2 RC:   0        MGMT_HDA :mgmt_hda_apdu_fcc_encode_and_send: Encoding MGMT_HDA_AUDIO_INPUT_CTRL_CHANGE_MIC_VOLUME message...

2020-05-28T21:45:50.879+10:00> LVL:1 RC:   0        MGMT_HDA :soft_hda_host_send_mic_volume_apdu: mic_volume(786432)

2020-05-28T21:45:50.880+10:00> LVL:2 RC:   0        MGMT_IMG :CODEC: Processing MGMT_IMG_APDU_TYPE_QUAD_CFG_ACK. [pri = 0]

2020-05-28T21:45:50.880+10:00> LVL:2 RC:   0        MGMT_IMG :cfg_ack_process: processing [1]: MGMT_IMG_APDU_TYPE_QUAD_CFG_ACK - extended

2020-05-28T21:45:50.880+10:00> LVL:2 RC:   0        MGMT_IMG :Soft client sent no preferred display topology. Using default values for 4 display(s). Forcing topology: 0

2020-05-28T21:45:50.880+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=MultimediaRedirChannel)

2020-05-28T21:45:50.881+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=0 data=0x7:0x1 (MultimediaRedirChannel)

2020-05-28T21:45:50.886+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=RPC#VMwareRde#17628_-001 data=0x00000000

2020-05-28T21:45:50.886+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=RPC#VMwareRde#17628_-001)

2020-05-28T21:45:50.886+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=RPC#RPCME#5272_-001 data=0x00000000

2020-05-28T21:45:50.886+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=RPC#RPCME#5272_-001)

2020-05-28T21:45:50.888+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=RPC#MKSVchan#6076_-001 data=0x00000000

2020-05-28T21:45:50.888+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=RPC#MKSVchan#6076_-001)

2020-05-28T21:45:50.889+10:00> LVL:2 RC:   0        MGMT_HDA :Speaker audio is being enabled: encoding=STEREO-48K-ADPCM (active-bw=9.00 Mbps)

2020-05-28T21:45:50.889+10:00> LVL:2 RC:   0        MGMT_HDA :AUDIO enable changed state from 0 to 1

2020-05-28T21:45:50.891+10:00> LVL:2 RC:   0        MGMT_IMG :Native resolution of the client display 0 is 2560x1440

2020-05-28T21:45:50.891+10:00> LVL:2 RC:   0        MGMT_IMG :   Display 0 added using native dmt: resolution=2560x1440, origin=(0, 0), rotation=0

2020-05-28T21:45:50.891+10:00> LVL:2 RC:   0        MGMT_IMG :Native resolution of the client display 1 is 2560x1440

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :   Display 1 added using native dmt: resolution=2560x1440, origin=(2560, 0), rotation=0

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :Native resolution of the client display 2 is 2560x1440

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :   Display 2 added using native dmt: resolution=2560x1440, origin=(5120, 0), rotation=0

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :Native resolution of the client display 3 is 2560x1440

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :   Display 3 added using native dmt: resolution=2560x1440, origin=(7680, 0), rotation=0

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :Topology: valid:1 (res supported:1, no overlap:1, num active displays:4)

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :process_min_max_quality_params: minimum quality is set to 40 [host setting]

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :process_min_max_quality_params: maximum initial quality is set to 80 [host setting]

2020-05-28T21:45:50.892+10:00> LVL:2 RC:   0        MGMT_IMG :extended img_settings: use_client_settings: 0, build_to_lossless:1, max_frame_rate: 30, smoothness_vs_sharpness: 50

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          SERVER :Resolution Set does not support VMwareResolutionSet_SetLogLevel, skipping ...

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0    IMG_FRONTEND :Calling open display in Tera2 mode.

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTap_Attach2: inRdsSession 0 sessionId 1

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, deviceID PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00 flags 0x0

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY2, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80005

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY3, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80001

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY4, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:50.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY5, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:50.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, deviceID  flags 0x200008

2020-05-28T21:45:50.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, deviceID  flags 0x200008

2020-05-28T21:45:50.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, deviceID  flags 0x200008

2020-05-28T21:45:50.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 1, nvDisplays 4, amdDisplays 0, intel 0

2020-05-28T21:45:50.899+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=RPC#VMwareRde#17628_-001)

2020-05-28T21:45:50.899+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=4 data=0x0:0x0 (RPC#VMwareRde#17628_-001)

2020-05-28T21:45:50.900+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=RPC#MKSVchan#6076_-001)

2020-05-28T21:45:50.900+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=6 data=0x0:0x0 (RPC#MKSVchan#6076_-001)

2020-05-28T21:45:50.904+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=RPC#RPCME#5272_-001)

2020-05-28T21:45:50.904+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=5 data=0x0:0x0 (RPC#RPCME#5272_-001)

2020-05-28T21:45:50.917+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> Unable to get API interface version 1: 0

2020-05-28T21:45:50.917+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 force win32 0  forceXPDMForRDS 0

2020-05-28T21:45:50.917+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 4 NVFBC disabled 0

2020-05-28T21:45:50.917+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: profiling disabled.

2020-05-28T21:45:50.917+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, deviceID PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00 flags 0x0

2020-05-28T21:45:50.917+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY2, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80005

2020-05-28T21:45:50.918+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY3, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80001

2020-05-28T21:45:50.918+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY4, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:50.918+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY5, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:50.919+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, deviceID  flags 0x200008

2020-05-28T21:45:50.919+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, deviceID  flags 0x200008

2020-05-28T21:45:50.919+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, deviceID  flags 0x200008

2020-05-28T21:45:50.919+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 1, nvDisplays 4, amdDisplays 0, intel 0

2020-05-28T21:45:50.919+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: Allocating server, size=10472 bytes

2020-05-28T21:45:50.927+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=UNITY_UPDATE_CHA#44dc_1#PSC data=0x00000000

2020-05-28T21:45:50.927+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=UNITY_UPDATE_CHA#44dc_1#PSC)

2020-05-28T21:45:50.931+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionSetReadRegistryInt error 2.

2020-05-28T21:45:50.931+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionSetReadRegistryInt error 2.

2020-05-28T21:45:50.931+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: Enabling 3D RDSH registry key not present

2020-05-28T21:45:50.931+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: configure conventional VDGA

2020-05-28T21:45:50.931+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> VMwareResolutionSet_ConfigureVDGADisplays: enter

2020-05-28T21:45:50.931+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionVDGADevicesPresent - VDGA Devices present called

2020-05-28T21:45:50.932+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: displays requested 1, VDGA devices present 4, attached VDGA displays 2

2020-05-28T21:45:50.933+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: Display update strategy: modify

2020-05-28T21:45:50.934+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:50.937+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=UNITY_UPDATE_CHA#44dc_1#PSC)

2020-05-28T21:45:50.937+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=7 data=0x0:0x0 (UNITY_UPDATE_CHA#44dc_1#PSC)

2020-05-28T21:45:51.132+10:00> LVL:1 RC:   0          SERVER :InputDevTap_GetKeyboardState @ timer: LEDs = 0xFFFFFFFF ==> 0x02

2020-05-28T21:45:51.132+10:00> LVL:1 RC:   0          SERVER :InputDevTap_GetKeyboardState @ timer: typematic [delay 0 ==> 500] [rate 0 ==> 33]

2020-05-28T21:45:51.245+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=VMWARE__1.25148@1 data=0xFFFFFFFF

2020-05-28T21:45:51.245+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=VMWARE__1.25148@1)

2020-05-28T21:45:51.253+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=VMWARE__1.25148@1)

2020-05-28T21:45:51.253+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=8 data=0xFFFFFFFF:0x0 (VMWARE__1.25148@1)

2020-05-28T21:45:51.386+10:00> LVL:2 RC:   0      MGMT_VCHAN :closing chan 8 (type=CLOSE_GRACEFUL) ...

2020-05-28T21:45:51.386+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change OPENED ==> CLOSE_PEND  (name=VMWARE__1.25148@1)

2020-05-28T21:45:51.396+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending CLOSE_REQ APDU: name=VMWARE__1.25148@1 data=0xFFFFFFFF

2020-05-28T21:45:51.414+10:00> LVL:2 RC:   0      MGMT_VCHAN :Received CLOSE_ACK APDU: chan=8 name=VMWARE__1.25148@1 reason=0xFFFFFFFF

2020-05-28T21:45:51.416+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=CLOSED chan=8 data=0x0:0xFFFFFFFF ()

2020-05-28T21:45:51.503+10:00> LVL:2 RC:   0        MGMT_KMP :>>> Rxed SET_MULTIPLE_LOCALE: num_locales=2 lang[0]=0xC09 layout[0]=0x1

2020-05-28T21:45:51.503+10:00> LVL:2 RC:   0        MGMT_KMP :>>> Rxed SET_MULTIPLE_LOCALE:               lang[1]=0x409 layout[1]=0x1

2020-05-28T21:45:51.510+10:00> LVL:2 RC:   0          SERVER :Desktop switched: EVENT_SYSTEM_DESKTOPSWITCH

2020-05-28T21:45:51.511+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> VMwareResolutionSet_SyncDisplayTopology: enter

2020-05-28T21:45:51.513+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=VMWARE__1.25148@2 data=0xFFFFFFFE

2020-05-28T21:45:51.513+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=VMWARE__1.25148@2)

2020-05-28T21:45:51.521+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=VMWARE__1.25148@2)

2020-05-28T21:45:51.521+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=9 data=0xFFFFFFFE:0x0 (VMWARE__1.25148@2)

2020-05-28T21:45:51.968+10:00> LVL:2 RC:   0      MGMT_VCHAN :closing chan 9 (type=CLOSE_GRACEFUL) ...

2020-05-28T21:45:51.968+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change OPENED ==> CLOSE_PEND  (name=VMWARE__1.25148@2)

2020-05-28T21:45:51.979+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending CLOSE_REQ APDU: name=VMWARE__1.25148@2 data=0xFFFFFFFE

2020-05-28T21:45:52.101+10:00> LVL:2 RC:   0      MGMT_VCHAN :Received CLOSE_ACK APDU: chan=9 name=VMWARE__1.25148@2 reason=0xFFFFFFFE

2020-05-28T21:45:52.109+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=CLOSED chan=9 data=0x0:0xFFFFFFFE ()

2020-05-28T21:45:52.373+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionVMWDevicesActive: inRdsSession 0 sessionId 1

2020-05-28T21:45:52.374+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: Could not find VMware devices.

2020-05-28T21:45:52.374+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: noop sync topology

2020-05-28T21:45:52.386+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change PEER_OPEN ==> OPENED  (name=RDP__CARANOC)

2020-05-28T21:45:52.386+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_ACK APDU: name=RDP__CARANOC data=0x00000001

2020-05-28T21:45:52.386+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=1 data=0x2:0x0 (RDP__CARANOC, indirect)

2020-05-28T21:45:52.410+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:52.410+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0, status returns 0  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:52.898+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 0, sys object 0C22ECCC  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:53.217+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:53.434+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:53.434+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0, status returns 0  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:53.621+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC_Create() failed -5, adapter 1  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:53.622+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: UpdateDisplayWatcher ERROR

2020-05-28T21:45:53.805+10:00> LVL:2 RC:   0      MGMT_VCHAN :closing chan 1 (type=CLOSE_GRACEFUL) ...

2020-05-28T21:45:53.805+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change OPENED ==> CLOSE_PEND  (name=RDP__CARANOC)

2020-05-28T21:45:53.815+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending CLOSE_REQ APDU: name=RDP__CARANOC data=0x00000001

2020-05-28T21:45:53.834+10:00> LVL:2 RC:   0      MGMT_VCHAN :Received CLOSE_ACK APDU: chan=1 name=RDP__CARANOC reason=0x00000001

2020-05-28T21:45:53.835+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=CLOSED chan=1 data=0x0:0x1 ()

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: BlankHostScreen m_Displays empty

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: usermode backend init failed

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTap_Attach2 failed, retrying

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTap_Attach2: inRdsSession 0 sessionId 1

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, deviceID PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00 flags 0x0

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY2, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80005

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY3, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80001

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY4, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:53.888+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY5, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:53.889+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, deviceID  flags 0x200008

2020-05-28T21:45:53.889+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, deviceID  flags 0x200008

2020-05-28T21:45:53.889+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, deviceID  flags 0x200008

2020-05-28T21:45:53.889+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 1, nvDisplays 4, amdDisplays 0, intel 0

2020-05-28T21:45:53.893+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> Unable to get API interface version 1: 0

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 force win32 0  forceXPDMForRDS 0

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 4 NVFBC disabled 0

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: profiling disabled.

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, deviceID PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00 flags 0x0

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY2, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80005

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY3, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80001

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY4, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID T4-4Q, name \\.\DISPLAY5, deviceID PCI\VEN_10DE&DEV_1EB8&SUBSYS_130E10DE&REV_A1 flags 0x80000

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, deviceID  flags 0x200008

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, deviceID  flags 0x200008

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, deviceID  flags 0x200008

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 1, nvDisplays 4, amdDisplays 0, intel 0

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: Allocating server, size=10472 bytes

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionSetReadRegistryInt error 2.

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionSetReadRegistryInt error 2.

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: Enabling 3D RDSH registry key not present

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: configure conventional VDGA

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> VMwareResolutionSet_ConfigureVDGADisplays: enter

2020-05-28T21:45:53.894+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ResolutionVDGADevicesPresent - VDGA Devices present called

2020-05-28T21:45:53.895+10:00> LVL:0 RC:   0          EXTERN :set_resolution ==> ressetlib: displays requested 1, VDGA devices present 4, attached VDGA displays 2

2020-05-28T21:45:53.896+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: Display update strategy: modify

2020-05-28T21:45:53.896+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:53.913+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:53.913+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0, status returns 0  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:53.982+10:00> LVL:2 RC:   0      MGMT_VCHAN :Sending OPEN_REQ APDU: name=RDP__CARANOC data=0x00000002

2020-05-28T21:45:53.982+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change NOT_FOUND ==> LOCAL_OPEN  (name=RDP__CARANOC)

2020-05-28T21:45:54.077+10:00> LVL:2 RC:   0      MGMT_VCHAN :State Change LOCAL_OPEN ==> OPENED  (name=RDP__CARANOC)

2020-05-28T21:45:54.077+10:00> LVL:2 RC:   0      MGMT_VCHAN :Calling chan callback: event=OPENED chan=10 data=0x2:0x0 (RDP__CARANOC)

2020-05-28T21:45:54.211+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: created the sys object - adapter 0, sys object 0DB948E4  Adapter 0, Display \\.\DISPLAY2

2020-05-28T21:45:54.309+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:54.318+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is possible.  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:54.318+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0, status returns 0  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:54.391+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC_Create() failed -1, adapter 1  Adapter 0, Display \\.\DISPLAY3

2020-05-28T21:45:54.391+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: UpdateDisplayWatcher ERROR

2020-05-28T21:45:54.668+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: BlankHostScreen m_Displays empty

2020-05-28T21:45:54.668+10:00> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: usermode backend init failed

2020-05-28T21:45:54.668+10:00> LVL:0 RC:-500    IMG_FRONTEND :cSW_HOST_FRONTEND::open_display - Error attaching to SVGADevTap, error 1: Failed

2020-05-28T21:45:54.668+10:00> LVL:0 RC:-500        MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. 10 retries remaining. Trying again...

==============

Attaching full logs.

I haven't tried with BLAST yet. We installed the VMware Tools and Horizon agent in the correct order during the maintenance/recompose.

Any help is appreciated.