Corporate laptops and Workspace One. We want to enroll our corporate laptops in the Workspace One. But when the user launches an AirwatchAgent.msi installation requests ad admin privileges to complete the installation. How we can get around this because our employees haven't administrator rights on the corporate laptops.

Hi all,

I am having some trouble with vCenter and vROPS and I am unable to fix this at the moment, so I need some help :-)

I have a working vROPS and I can work with it, it collects data from the Vcenter, so the account / connection seems to be correct.

But if i navigate through the vCenter ( Menu -> vRealize Opeartions ) , I am getting no content. The Output is displaying the blue/grey circle, which suggests,

that vcenter is loading some content from vROPS

Can anyone help me with this? Is there a way to "reset" the connection ?

Thx in advance

Chakoe

I have an issue where a client's backup software has been creating snaps and then has not been cleaning them up afterward.

The guest is shut down, when I try and manually consolidate the snaps, the process fails at the same point on the same files with the following output:

Code run:

[root@EC-ADLS-ESX02:/vmfs/volumes/58802a46-6f78cfbc-c901-a0369fcb02d0/EC-ADLS-FS01] vmkfstools -e EC-ADLS-FS01_1-000254.vmdk

Return Code:

Disk link /vmfs/volumes/58802a46-6f78cfbc-c901-a0369fcb02d0/EC-ADLS-FS01/EC-ADLS-FS01_1-000015.vmdk successfully opened.

Failed to open disk link /vmfs/volumes/58802a46-6f78cfbc-c901-a0369fcb02d0/EC-ADLS-FS01/EC-ADLS-FS01_1-000014.vmdk :Failed to lock the file (16392)Disk chain is not consistent : The parent of this virtual disk could not be opened (23)

I can see the snaps go back to 000001

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000001-ctk.vmdk

-rw------- 1 root     root     419598336 Apr 2 06:04 EC-ADLS-FS01-000001-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000001.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000002-ctk.vmdk

-rw------- 1 root     root      16945152 Apr  2 06:04 EC-ADLS-FS01-000002-delta.vmdk

-rw------- 1 root root           422 Apr 21 03:54 EC-ADLS-FS01-000002.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000003-ctk.vmdk

-rw------- 1 root     root     469929984 Apr 2 06:04 EC-ADLS-FS01-000003-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000003.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000004-ctk.vmdk

-rw------- 1 root     root     402821120 Apr 2 06:04 EC-ADLS-FS01-000004-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000004.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000005-ctk.vmdk

-rw------- 1 root     root     419598336 Apr 2 06:04 EC-ADLS-FS01-000005-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000005.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000006-ctk.vmdk

-rw------- 1 root     root     503484416 Apr 2 06:04 EC-ADLS-FS01-000006-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000006.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000007-ctk.vmdk

-rw------- 1 root     root     503484416 Apr 2 06:04 EC-ADLS-FS01-000007-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000007.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000008-ctk.vmdk

-rw------- 1 root     root     402821120 Apr 2 06:04 EC-ADLS-FS01-000008-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000008.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000009-ctk.vmdk

-rw------- 1 root     root     402821120 Apr 2 06:04 EC-ADLS-FS01-000009-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000009.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000010-ctk.vmdk

-rw------- 1 root     root     402821120 Apr 2 06:04 EC-ADLS-FS01-000010-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000010.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000011-ctk.vmdk

-rw------- 1 root     root     453152768 Apr 2 06:04 EC-ADLS-FS01-000011-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000011.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000012-ctk.vmdk

-rw------- 1 root     root     436375552 Apr 2 06:04 EC-ADLS-FS01-000012-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000012.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000013-ctk.vmdk

-rw------- 1 root     root     1560449024 Apr  2 06:04 EC-ADLS-FS01-000013-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000013.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000014-ctk.vmdk

-rw------- 1 root     root      16945152 Apr  2 06:04 EC-ADLS-FS01-000014-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000014.vmdk

-rw------- 1 root     root       5243392 Apr  2 06:04 EC-ADLS-FS01-000015-ctk.vmdk

-rw------- 1 root     root 167936 Apr  2 06:04 EC-ADLS-FS01-000015-delta.vmdk

-rw------- 1 root root           429 Apr 21 03:54 EC-ADLS-FS01-000015.vmdk

How can I validate this file/s to continue with consolidation, or can I simply delete all these objects and start up the box?

Any assistance will be greatly appreciated.

Infos tech

Vcenter Applicance 6.7

PSC embeded

Esxi 6.5 U2

Bonjour à tous,

voilà, je viens sur le forum pour trouver de l'aide au problème que je rencontre. Je viens de mettre à jour mon "Vcenter" avec un certificat Autosigné + Root. Je suis passé par le process du "Certificat Manager" et de l' "ADCS". Jusque là, tout va bien. J'ai bien mis à jour le serveur. Je vérifie le certificat (cadenas sur la page Web) sur le "Vcenter" et sur le "Vmware Appliance Management", tout est OK !

Hi All,

here, I come to the forum to find help with the problem I am having. I just updated my "Vcenter" with a Self-signed + Root certificate. I went through the process of "Certificate Manager" and "ADCS". That's fine. I have successfully updated the server. I check the certificate (padlock on the web page) on the "Vcenter" and on the "Vmware Appliance Management", everything is OK !

Par contre, des que j'ajoute un ESXI à mon "Vcenter", là, il récupère l'ancien certificat Root Vmware (CA)...

On the other hand, I added an ESXI to my "Vcenter", it recovers the old Root Vmware (CA) certificate ...

Au niveau de l'ESXI :

on the ESXI :

J'ai pourtant fait un renouveler certificat et un actualisé du certificat au niveau du "Vcenter", mais rien à faire il garde l'ancien certificat + root Vmware...

J'ai lancé toutes ces commandes afin de localiser le certificat + Root Vmware :

However, I did a certificate renewal and an updated certificate at the "Vcenter" level, but nothing, it keeps the old certificate + root Vmware ...

I launched all these commands in order to locate the + Root Vmware certificate:

J'ai bien retrouvé le "CA Vmware" dans "TRUSTED_ROOTS" que j'ai sauvegardé, dépublié et enfin supprimé avec les commandes suivantes :

I found the "CA Vmware" in "TRUSTED_ROOTS" which I saved, unpublished and finally deleted with the following commands:

Relancer tous les services du "Vcenter/PSC", rebooter même (le Vcenter, l'ESXI)... Mais rien n'y fait, l' "ESXI" récupère toujours le certificat "CA Vmware"...

Relaunch all the services on the "Vcenter / PSC", then reboot (the Vcenter, the ESXI) ... But nothing !!! the "ESXI" always retrieves the "CA Vmware" certificate ...

Que faire d'autre, svp ???

What can i do please ??

Merci à vous pour votre aide précieuse..

Thanks a lot for your help...

Akeena64

Hello there,

We have a doubt with our NSX license. Few months ago, we bought a NSX professional license, and we know the products available for those license, https://kb.vmware.com/s/article/2145269

The doubt is the following:

We can deploy a load balancer (not included on professional license), also we can use Application Rule Manager  (not included on professional license) and surely we have the same with other products that we dont deploy yet. Why can we use that products? Can use that but we dont have official support?

Thanks in advance.

Regards

i have been trying to install horizon client version 5.4.2 or 5.4.0 on windows 7 but it fails silently and error just pops up install failed. it seems that the client is installed but around 90% of completion, it just fails.  Have disabled antivirus also but same issue.

Attaching logs.

Need a setup file for VCenter 6.7 for Windows OS. Can someone please help me on this?

Help    

I have ESXi 6.7 running, after a funny issue with the webportal not working correctly, stuck just before the login screen, I reset the management agents, now all I presented with is

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x000000a63051bb30] _serverNamespace = / action = Allow _port = 8309)

Have tried resetting the management agents again and the network agent both via ssh and on the console, I'm now at a loss please help me.

Thanks

Adrian

Environment - three 6.5 hosts - two have just been upgraded to 6.5 P04 (build 15256549), one is still at 6.5 U2 (8294253) but will be upgraded shortly. vCenter Appliance has just been upgraded to 6.5.0.32300.

Hardware is three essentially identical old HP desktop PCs (8300 SFF), 32GB RAM, and 500GB SSDs. Each has a single onboard Intel 82579LM GigE NIC, and that single NIC provides everything - VMware management and vmotion which share the same IP, guest network connectivity, and Intel AMT for remote management (on a separate IP); everything is on a single VLAN and subnet. Network is a Cisco 3560G switch. There is no shared storage (other than an NFS mount for ISOs and such), so vmotion is done from local storage on host A to local storage on host B. Vmotion speed averages over 900Mbps, so essentially wirespeed. The network is otherwise clean and quiet.

As I was preparing to do the ESX upgrades, I was vmotioning VMs around so I could power cycle the hosts. More often than not, running guests would fail to vmotion after period of time (2-10 minutes) - data would be flying along, and then just stop. This continues to happen even after I've upgraded the hosts.

The error usually seen in the vSphere client is: "Failed waiting for data. Error 195887137. Timeout."

After a number of trials, I've dug up what appears to be an indication of the problem: events in vmkernel.log on the source host.

Consistently, the source host reports the following (with nothing significant for minutes before it):

2020-05-19T00:37:29.280Z cpu7:65944)INFO (ne1000): hardware TX hang detected on vmnic0

2020-05-19T00:37:29.280Z cpu7:65944)DEBUG (ne1000): resetting adapter of vmnic0

This is followed by a bunch of log entries that indicate a reset of the network interface. The switch reports the same - the link flaps, and connectivity is lost to the source host and all of its guests for a few seconds. No drops or errors are seen on the switch on either the source or destination port.

The destination reports a timeout error, but about six seconds after the above messages (and yes, they are in sync, using ntp). So the messages above are the FIRST indication that something's failing, although I suspect that if I were doing a packet capture, I'd see the network stream stop a few seconds earlier.

Surprisingly, I haven't been able to find anything that refers specifically to "hardware TX hang detected". I haven't found anything in any logfiles (host or guest) that occur just before that message, which leads me to believe that this issue is a NIC/driver issue. I have some dual-port PCI NICs (also Intel) on order, which would fix the problem IF the issue is either related to

- Combination with Intel AMT on the same interface

- Combination with too much VMware stuff (management, vmotion, guests) on the same interface

- Overall lousiness of a desktop embedded NIC (but hey, it's Intel?)

But wouldn't address the issue if there's something I need to tweak with the ne1000 driver, or my crappy desktop hosts just aren't up to the task.

Sure - this is (mostly) cheap consumer hardware, and it's a hanky-janky environment with no shared storage or separate networks. But it's standard stuff - no realtek nonsense, for instance.

One thought I had was the possibility of trying the e1000 driver instead of ne1000. That sort of seems like a step backwards.

Any brighter ideas?

Hi,

When I try to remove a datastore from vsphere I get the following error:

Call "HostDatastoreSystem.RemoveDatastore" for object "datastoreSystem-15" on vCenter Server "xxxxxx" failed.

The datastore is emtpy and we want to unpresent it to the hosts. Is there a way to remove a datastore via the CLI? If I unpresented it to the hosts via the SAN would this cause any issues?

Good morning everyone,

We've been using vCenter for a while on multiple locations, however when we recently installed it on another location we got a very strange problem. The networking between the ESXi hosts, the other clients connected to the network and really anything physical was a max of 110~mbit. However, VMs on those hosts have a proper 1Gbit to other clients on the network, including other ESXi hosts.

What we've tried so far:

- New switch

- Renew VMKernel ports

- Look at switch configuration

- Create distributed switch and assign VMKernel ports to those

- Try new ESXi hosts

- Reboot everything

- Check disks

- New disks

- Different network ports

Now I am out of options to try, I don't know why it is like this. We get this slowness the most when deploying templates, no matter where (even on the host the template is from) it's exceptionally slow.

I hope someone can help!

Friendly regards,

Kane

Hi,

I am having issue importing tags and getting error as below

Please help

CSV file data

"Folder","VM","IPAddress","PowerState","OS","Application","Department","Owner"

"Testing","HADOOP02",,"PoweredOff",,"Hadoop","Operations","Karl"

Script

$CMDBInfo = Import-CSV ".\Tags1.csv"

# Get the header names to use as tag category names

$TagCatNames = $cmdbinfo | Get-Member | Where {$_.MemberType -eq "NoteProperty"} | Select -Expand Name

# Create the Tag Category if it doesnt exist

Foreach ($Name in ($TagCatNames | Where {$_ -ne "VM" -and $_ -ne "Folder" -and $_ -ne "IPAddress" -and $_ -ne "OS" -and $_ -ne "PowerState"})) {

    if (-Not (Get-TagCategory $Name -ea SilentlyContinue)) {

        Write-Host "Creating Tag Category $Name"

        New-TagCategory -Name $Name -Description "$Name from CMDB" | Out-Null

        # Create Tags under the Tag Categories

        $UniqueTags = $cmdbinfo | Select -expand $name | Get-Unique

        Foreach ($Tag in $UniqueTags) {

            if (-Not (Get-Tag $Tag -ea SilentlyContinue)) {

                Write-Host "..Creating Tag under $Name of $Tag"

                New-Tag -Name $Tag -Category $name -Description "$Tag from CMDB" | Out-Null

            }

            # Assign the Tags to the VMs/Hosts

            $cmdbinfo | Where {$_.($Name) -eq $Tag} | Foreach {

                Write-Host ".... Assigning $Tag in Category of $Name to $($_.Name)"

                $TagAssignment = Get-Tag -Category $Name -name $Tag

                New-TagAssignment -entity $($_.Name) -Tag $Tagassignment | Out-Null

            }

        }        

    }

}

Output

Get-Tag : Cannot validate argument on parameter 'Name'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again

At D:\Tags\Create_Import_Category_Tags\Tags.ps1:24 char:64

+                 $TagAssignment = Get-Tag -Category $Name -name $Tag

+                                                                ~~~~

    + CategoryInfo          : InvalidData: (:) [Get-Tag], ParameterBindingValidationException

    + FullyQualifiedErrorId : ParameterArgumentValidationError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag

New-TagAssignment : Cannot bind argument to parameter 'Entity' because it is null.

At D:\Tags\Create_Import_Category_Tags\Tags.ps1:25 char:43

+                 New-TagAssignment -entity $($_.Name) -Tag $Tagassignm ...

+                                           ~~~~~~~~~~

    + CategoryInfo          : InvalidData: (:) [New-TagAssignment], ParameterBindingValidationException

    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.NewTagAssignment

Hello all,

First, I'm new to this forum and to VMWare so your kindness is appreciated.

Here's the background:

I have 4 servers in different locations that are running ESXi 6.0, two are Dell R220, one HP DL 380 G9, and one is HP DL 160 G9.

The servers were built a few years ago by a previous VoIP vendor and are hosting ShoreTel servers and virtual switches.

The problem is that the vendor selected too small of hard drives and there isn't enough space for snapshots.

We have QNAPs available in each location.

I was wondering if it's possible to use them as storage locations for snapshots?

If so, can I be guide how to do that?

I tried consulting with QNAP support but they weren't helpful.

If more information is required, I will gladly provide it.

Thanks in advance.

Hello,

I'm using the new multiple user assignment option for a desktop pool with Horizon 7.12. It works without any issues using the html5 admin tool. My only issue is the amount of time it takes to manually add each user account to a desktop.

Has anyone found a way to assign multiple users to a desktop from the command line?

I'm not having much luck using the built in horizon powershell commandlets for multiple user assignments.

Update-UserOwnership -machine_id (Get-DesktopVM -Name machinename).machine_id -sid (Get-User -name username).sid

thanks in advance

Andy Sanderson

Hello vCenter Community, hope everyone is well.

  I'm trying to review requirements for a future maintenance to combine two vCenter clusters "2 hosts each" to one vCenter "VCSA 6.7" cluster with four hosts.

  We have two clusters because one was being ordered when the new expansions required a second set.  Both orders were for one vCenter VCSA with up to three hosts.

  The new license will be for the Enterprise version with one vCenter/VCSA with up to eight hosts.

My guess is to complete the following:

1.  Complete backups/snapshots of all devices and VMs

2.  disassociate all hosts from their vCenter/VCSA managers.

3.  Re-license the first vCenter.  If this is not possible create new vCenter and license it.

Question:  Can we just relicense one of the current VCSA 6.7 VM's to manage all VMs?  Do we have to create new?

4.  Join all hosts one at a time to the new VCSA 6.7 manager.

5.  Capture new backups/snapshots of all devices and VMs

  Are there any other considerations I should be aware of?  These changes will allow us to start using distributed switches and DRS to name two things.

Hi all,

hitting a really puzzling issue: configured the latest NSX-T on Cisco UCS, created T0, overlay TZ, created a segment and added two VMs. VMs are able to ping the gateway on T0, can ping each other if on the same host, but cannot ping each other if on different hosts. Upon closer inspection, it appears that no tunnels are formed between the ESXi nodes.

I'm able to ping between TEPs with large MTU, so no networking issues as far as I can see, but the tunnels are not formed... BFD shows tunnels are down (please see the output on the bottom).

Not seeing any related error messages in /var/log/vmkernel or /var/log/nsx-syslog.log on the hosts.

Anything else I can check? Would be happy to provide any other output. Please help!!!

Tested VXLAN connectivity and it looks good:

[root@NSX02:~] ping ++netstack=vxlan 10.12.0.151 -s 1600 -d

PING 10.12.0.151 (10.12.0.151): 1600 data bytes

1608 bytes from 10.12.0.151: icmp_seq=0 ttl=64 time=0.271 ms

Checked the logical switches on the hosts and they look good (the switch I'm using is called "test"):

NSX-Manager> get logical-switch

VNI     UUID                                  Name                                              Type

71688   5cce3073-c5c9-4cf6-9cad-8db50dd06b68  OV-WEB                                            DEFAULT

71689   8208b2cd-7d0c-407e-aacf-ee9297ef5cf2  OV-DB                                             DEFAULT

71691   fedd3ec3-d3e4-4d02-ac4f-cd94bde02fdf  transit-bp-2a5f80db-676d-41f4-b305-1e8591266f94   TRANSIT

71692   c9b96c71-ebff-4572-88a9-7639d2923743  transit-bp-8871e348-42da-447f-9193-70781b09730f   TRANSIT

71690   50db354a-bf9c-483f-9637-c397e78d05b7  transit-rl-8871e348-42da-447f-9193-70781b09730f   TRANSIT

71681   97655bd6-dd20-4746-8138-656a0c06e9b0  test                                              DEFAULT

71687   6fa865f8-4bb6-439a-a428-a94e27e02090  OV-APP                                            DEFAULT

[root@NSX02:~] nsxcli -c get logical-switch 71681 vtep-table

                                   Logical Switch VTEP Table

-----------------------------------------------------------------------------------------------

                                       Host Kernel Entry

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

Label      VTEP IP           Segment ID     Is MTEP       VTEP MAC       BFD count

124941    10.12.0.151        10.12.0.128     False  00:50:56:67:31:cb   0

                                       LCP Remote Entry

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

Label      VTEP IP           Segment ID          VTEP MAC                  DEVICE NAME

124941    10.12.0.151        10.12.0.128     00:50:56:67:31:cb                 None

                                        LCP Local Entry

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

Label      VTEP IP           Segment ID          VTEP MAC                  DEVICE NAME

124942    10.12.0.152        10.12.0.128     00:50:56:63:b0:56                 None

[root@NSX03:~] nsxcli -c get logical-switch 71681 vtep-table

                                   Logical Switch VTEP Table

-----------------------------------------------------------------------------------------------

                                       Host Kernel Entry

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

Label      VTEP IP           Segment ID     Is MTEP       VTEP MAC       BFD count

124942    10.12.0.152        10.12.0.128     False  00:50:56:63:b0:56   0

                                       LCP Remote Entry

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

Label      VTEP IP           Segment ID          VTEP MAC                  DEVICE NAME

124942    10.12.0.152        10.12.0.128     00:50:56:63:b0:56                 None

                                        LCP Local Entry

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

Label      VTEP IP           Segment ID          VTEP MAC                  DEVICE NAME

124941    10.12.0.151        10.12.0.128     00:50:56:67:31:cb                 None

Checked BFD sessions, tunnels down, no diagnostic....

[root@NSX03:/var/log]  net-vdl2 -M bfd -s nvds

BFD count:      3

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

Local IP: 10.12.0.151, Remote IP: 10.12.0.153, Local State: down, Remote State: down, Local Diag: No Diagnostic, Remote Diag: No Diagnostic, minRx: 1000, isDisabled: 0, l2SpanCount: 1, l3SpanCount: 1

Roundtrip Latency: NOT READY

VNI List: 71687

Routing Domain List: 8871e348-42da-447f-9193-70781b09730f

Local IP: 10.12.0.151, Remote IP: 10.12.0.200, Local State: down, Remote State: down, Local Diag: No Diagnostic, Remote Diag: No Diagnostic, minRx: 1000, isDisabled: 0, l2SpanCount: 3, l3SpanCount: 2

Roundtrip Latency: NOT READY

VNI List: 71690 71691   71692

Routing Domain List: 2a5f80db-676d-41f4-b305-1e8591266f94       8871e348-42da-447f-9193-70781b09730f

Local IP: 10.12.0.151, Remote IP: 10.12.0.152, Local State: down, Remote State: down, Local Diag: No Diagnostic, Remote Diag: No Diagnostic, minRx: 1000, isDisabled: 0, l2SpanCount: 2, l3SpanCount: 2

Roundtrip Latency: NOT READY

VNI List: 71681 71688

Routing Domain List: 2a5f80db-676d-41f4-b305-1e8591266f94       8871e348-42da-447f-9193-70781b09730f

Hi,

I have a application which I am running on VMware Workstation Pro with Windows 10 64bit OS. It captures mouse coordinates and sends it to a piece of hardware to move the mouse on it using the X,Y coordinates and the delta of the movement. On a bare metal machine I get normal X,Y coordinates but in the VM I get extremely high values that he opposite hardware doesn't understand. Any idea what the high values represent? or how to receive normal values in the VM?

Below is my configuration:

1. Workstation 15

2. Host Linux OS: RHEL 7.8

3. Guest OS: Windows 10

4. Host machine GPU: Nvidia quadro k620

5. Enabe 3D acceleration in VM

6. glxinfo | grep "renderer string" on host machine ---> llvmpipe

7. Host machine: OpenGL version string: 2.1 Mesa 18.3.4

And I get the below error while powering up the VM:

No 3D support available from host

And I can't use 3D applications properly inside the VM

Does any one know what is wrong with this configuration?

When using the Chrome OS Horizon Client, is there a way to switch between PCOIP and BLAST? Thanks

Tried to capture Mozilla Firefox 68.0esr and 68.8.0esr using ThinApp 5.2.7.

The "screenshot capture" function no longer works in the virtualized app even though it works in the native install.

Does anyone know why? Is it some screenshot component (like a library) that ThinApp is not capturing?