So a bit of an odd thing...

So when i connect to a VM that is already up and running i don't seem to see an issue.

However if it is freshly spun up i see the following:

Flex log-

2018-12-13 16:09:38.048 [DEBUG] ImportRegistry::Import: Calling '"C:\Windows\REGEDIT.EXE" /S "C:\Users\xxxxxx~1\AppData\Local\Temp\FLX16A1.tmp"' (RPAL: l=0 (D/E), r=0)

2018-12-13 16:09:47.594 [DEBUG] Read 20 entries from profile archive (size: 49135; compressed: 8277; took 9557 ms; largest file: 46826 bytes; slowest import took 0 ms)

2018-12-13 16:09:47.594 [DEBUG] Conditions: Check for endpoint name = true ('LJ2359H2' is equal to 'LJ2359H2')

So there is a delay from 16:09:38 -16:09-47.  Now when i checked the host:

vmkernel

2018-12-13T21:09:33.960Z cpu17:1943395)Net: 2324: connected Test05 eth0 to Virtual Machine Network, portID 0x40002f6

2018-12-13T21:09:33.963Z cpu17:1943395)Vmxnet3: 17293: Disable Rx queuing; queue size 512 is larger than Vmxnet3RxQueueLimit limit of 64.

2018-12-13T21:09:33.964Z cpu17:1943395)Vmxnet3: 17651: Using default queue delivery for vmxnet3 for port 0x40002f6

2018-12-13T21:09:33.964Z cpu17:1943395)NetPort: 1662: enabled port 0x40002f6 with mac 00:50:56:8f:b2:43

2018-12-13T21:09:34.225Z cpu28:1943395)Hbr: 3489: Migration end received (worldID=2139992) (migrateType=7) (event=1) (isSource=0) (sharedConfig=0)

2018-12-13T21:09:34.226Z cpu1:74341)Config: 706: "SIOControlFlag2" = 0, Old Value: 1, (Status: 0x0)

2018-12-13T21:09:38.307Z cpu22:1943398)NetPort: 1881: disabled port 0x40002f6

2018-12-13T21:09:40.496Z cpu19:1943399)Vmxnet3: 17293: Disable Rx queuing; queue size 512 is larger than Vmxnet3RxQueueLimit limit of 64.

2018-12-13T21:09:40.496Z cpu19:1943399)Vmxnet3: 17651: Using default queue delivery for vmxnet3 for port 0x40002f6

2018-12-13T21:09:40.496Z cpu19:1943399)NetPort: 1662: enabled port 0x40002f6 with mac 00:50:56:8f:b2:43

Please note that this is 5 hours ahead, so 21:09:38 is actually 16:09:38.  The port the VM is connected to is disabled, then enabled a short time later.  I don't think this is a coincidence as the timing is dead on.  Not to mention the fact that the majority of these delays are about the same time... but i digress.

I've opened a case with vmware regarding this, and I'll see where that goes.  When i have more time tomorrow I'll test through and see if this is what is causing the issue as i don't like a single example .