I’m building a 1909 Win 10 gold image vm and i’m running into an issue of a black screen delay when windows begins to login.

 

6.7U3

Horizon 7.10

DEM 7.11

 

1.  Hosts are using physical Nvidia GPUs.

2.  Ran the OSOT allowing Windows updates along with a couple apps (calculator etc.)  Everything else is pretty much default using the Windows 10 1909-2004 template.

3.  I’m currently running an earlier build in production, during logon, all i see is waiting with a delayed spinning circle, which eventually goes to Preparing Desktop (circle runs smoother in this stage) followed by an immediate Windows desktop.  In the current 1909 build that i’m getting prepared for production, it goes through at logon with applying vmware dem, gpos etc displayed on the screen, once thats complete it goes to preparing for a few seconds and goes to a solid black screen that is delayed by like 15 seconds…  it also seems that the startup apps take longer to start in this build post optimizations as well.  Has anyone experienced this?

4.  Lastly, everything else is great other than the dreaded start menu click delaying for 3 seconds or so , sometimes its immediate, but most times there is a noticable delay with the start button as well as Windows search.  Is there anything that addresses this outside of the OSOT that i’m missing?

 

Thanks for any insight!

I’m getting ready to upgrade from 1907 and was wondering if anyone has upgraded to to 2005 on-prem.  If you have upgraded, did you experience any issues. 

 

I’m upgrading to get to the latest version and also resolve an issue where the VMWare Tunnel (via the UAG) will lose it credentials every 6 months and stop working.  Also, there was an issue where the tunnel settings page wouldn’t load because of a similar issue.

 

I could go to 2001 but will be in the same boat soon enough where I need to upgrade.

 

Any feedback is appreciated.

 

Joe Beaty

Hey all,

 

Is it possible to report on all the datastores that are in the cluster?  For instance, we have a Datastore Cluster that has 16 datastores inside of it.  I want to traverse by each cluster and get results for the entire Datastore Cluster and not each individual datastore.  This is what I have been using but it returns every single datastore. 

 

javascript:;Get-Datastore  |
Select @{N='Datacenter';E={$_.Datacenter.Name}},
    @{N='DSC';E={Get-DatastoreCluster -Datastore $_ | Select -ExpandProperty Name}}, 
    Name,CapacityGB,@{N='FreespaceGB';E={[math]::Round($_.FreespaceGB,2)}},
    @{N='ProvisionedSpaceGB';E={[math]::Round(($_.ExtensionData.Summary.Capacity - $_.Extensiondata.Summary.FreeSpace + $_.ExtensionData.Summary.Uncommitted)/1GB,2)}},
    @{N='UnCommittedGB';E={[math]::Round($_.ExtensionData.Summary.Uncommitted/1GB,2)}},
    @{N='VM';E={$_.ExtensionData.VM.Count}} | Format-Table -AutoSize

Hi all,

Horizon 7.10

Windows 10 1903

Linked Clones

 

We have two different types of clients which uses two separate types of audio hardware. Our issues is that a subset of users are having to set the audio driver every time they login. 

 

The default audio driver in the golden image is Vmware audio driver.

 

We have some users that use a zero client to connect to our VDI environment and use a headset with microphone. The only way to get headset and mic to work on the headset is use to the Teradici audio driver. 

 

each user has the audio output option of Vmware or Teradici.  When they choose the audio driver, its reset after logoff/logon.

 

how can we solve this?

 

Thank you.

Hi;

 

I just got a BSOD running a Windows 10 Host (1909). I was running a RHEL 7.7 Linux Guest full-screen at the time. (I had just returned from a break).

 

I got a mini-dump and a memory.dmp.

 

Running windbg against the memory.dmp calls out what looks to the casual observer like Workstation driver and process references:

 

“FAULTING_PROCESSOR: 6

 

PROCESS_NAME:  vmware-vmx.exe

 

FAULTING_THREAD:  ffffdd86e5270080″

 

and

 

“

STACK_TEXT: 

ffff8603`bfddf468 fffff801`4f778228 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmx86+0x100a

ffff8603`bfddf470 fffff801`4f77abdb : 00000000`00000000 00000000`00000000 ffff8603`bfddf938 00000000`00000000 : vmx86+0x8228

ffff8603`bfddf5b0 fffff801`4f771f13 : 00000000`000001b0 00000000`00000001 ffff8603`bfddf938 ffffdd87`01c65430 : vmx86+0xabdb

ffff8603`bfddf680 fffff801`4f77293e : 00000000`00000000 fffff801`391543a9 00000000`00000000 fffff801`38f132d4 : vmx86+0x1f13

ffff8603`bfddf860 fffff801`394b2a2b : 00000000`000003f8 fffff801`38f13269 00000000`00000000 ffffdd86`fab5d7a0 : vmx86+0x293e

ffff8603`bfddf8c0 fffff801`394b22f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x71b

ffff8603`bfddf9e0 fffff801`38fd3c18 : 00000000`746c6644 ffff8603`bfddfa00 00000000`00000000 ffff8f85`bb997c40 : nt!NtDeviceIoControlFile+0x56

ffff8603`bfddfa50 00007ffe`f23dc154 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

00000073`dc9ff5c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`f23dc154

 

 

STACK_COMMAND:  .thread 0xffffdd86e5270080 ; kb

 

SYMBOL_NAME:  vmx86+100a

 

MODULE_NAME: vmx86

 

IMAGE_NAME:  vmx86.sys

 

BUCKET_ID_FUNC_OFFSET:  100a

 

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_vmx86!unknown_function”

 

I’ll attach the entire !analyze -v output. (I’m only familiar enough with WinDbg to produce the !analyze output at this time, so I’m not sure what else would be helpful).

 

Is this an issue with the workstation driver? The system has an E5-1650 V4 Xeon CPU, for what its worth.

 

Thanks;

I’m trying to figure out how to use 2 monitors. I’m running Ubunut 18.04 with a 4k monitor and an HD monitor. Both are recognized and work fine on the local machine.

The  horizon client is version 5.4.1 build 15988340.

 

i’m connecting to a windows 10 vm on a corporate network. In the guest Display settings, I only see a single display which is the 4k monitor so that is the first question, is true dual monitor at the guest OS level supported? At some point i could see both monitors in some horizon view, similar to what windows would show, ie 2 boxes that can be moved to be side by side or stacked. And they had checkable marks on them (checking both and applying did not show the 2nd monitor) But i no longer see any option in the horizon menu to show this view.

 

So i do not see any way to pick 2 monitors.

 

I have also tried stretching the guest desktop image across monitors in one of two ways.

 

1) If i position the desktop so that it overlaps both local monitors and select full screen – all monitors, then i get a very distorted image where it looks like it has dropped the resoution to HD. it is virtually unusable.

 

2) i tried was from windowed mode and with the desktop on the 4k monitor,  dragging  the vertical border onto the HD monitor. But for each pixel column the desktop is extended, it ‘robs’ a pixel on the other side, ie it turns black. So that there is never more than 3840 pixels on the virtual desktop.

 

Is this all consistent with what is supported in the linux horizon client or is there some way to run 2 monitors with independent resolutions?

i’m trying to configure TKG cluster on vsphere 7 for the first time.

NSX-T 3.0 configured and running.

when i enable workload management with all required info it’s never finished configuring.

i can see in wcp log many messages in loop.

 

attaching error messages that repeatedly showing in the log:

 

020-06-29T12:52:51.438Z debug wcp informer.processLoop() lister.List() returned

2020-06-29T12:52:54.612Z error wcp [opID=5ef9ca68-domain-c8] Unexpected object: &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:Failure,Message:an error on the server (“unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)”) has prevented the request from succeeding,Reason:InternalError,Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body),Field:,},StatusCause{Type:ClientWatchDecoding,Message:unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body),Field:,},},RetryAfterSeconds:0,UID:,},Code:500,}

2020-06-29T12:52:54.612Z error wcp [opID=5ef9ca68-domain-c8] Error watching NSX CRD resources.

2020-06-29T12:52:54.612Z error wcp [opID=5ef9ca68-domain-c8] Error creating NSX resources. Err: Kubernetes API call failed. Details Error watching NSX CRD resources.

2020-06-29T12:52:54.612Z error wcp [opID=5ef9ca68-domain-c8] Failed to create cluster network interface for MasterNode: VirtualMachine:vm-1008. Err: Kubernetes API call failed. Details Error watching NSX CRD resources.

2020-06-29T12:52:54.612Z error wcp [opID=5ef9ca68-domain-c8] Error configuring API server on cluster domain-c8 An error occurred. This operation will be retried.

2020-06-29T12:52:54.832Z error wcp [opID=5ef9ca68-domain-c8] Unexpected object: &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:Failure,Message:an error on the server (“unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)”) has prevented the request from succeeding,Reason:InternalError,Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body),Field:,},StatusCause{Type:ClientWatchDecoding,Message:unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body),Field:,},},RetryAfterSeconds:0,UID:,},Code:500,}

2020-06-29T12:52:54.832Z error wcp [opID=5ef9ca68-domain-c8] Error watching NSX CRD resources.

2020-06-29T12:52:54.832Z error wcp [opID=5ef9ca68-domain-c8] Error creating NSX resources. Err: Kubernetes API call failed. Details Error watching NSX CRD resources.

2020-06-29T12:52:54.832Z error wcp [opID=5ef9ca68-domain-c8] Failed to create cluster network interface for MasterNode: VirtualMachine:vm-1007. Err: Kubernetes API call failed. Details Error watching NSX CRD resources.

2020-06-29T12:52:54.832Z error wcp [opID=5ef9ca68-domain-c8] Error configuring API server on cluster domain-c8 An error occurred. This operation will be retried.

2020-06-29T12:52:54.957Z error wcp [opID=5ef9ca68-domain-c8] Unexpected object: &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:Failure,Message:an error on the server (“unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)”) has prevented the request from succeeding,Reason:InternalError,Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body),Field:,},StatusCause{Type:ClientWatchDecoding,Message:unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body),Field:,},},RetryAfterSeconds:0,UID:,},Code:500,}

2020-06-29T12:52:54.957Z error wcp [opID=5ef9ca68-domain-c8] Error watching NSX CRD resources.

2020-06-29T12:52:54.957Z error wcp [opID=5ef9ca68-domain-c8] Error creating NSX resources. Err: Kubernetes API call failed. Details Error watching NSX CRD resources.

2020-06-29T12:52:54.957Z error wcp [opID=5ef9ca68-domain-c8] Failed to create cluster network interface for MasterNode: VirtualMachine:vm-1006. Err: Kubernetes API call failed. Details Error watching NSX CRD resources.

2020-06-29T12:52:54.957Z error wcp [opID=5ef9ca68-domain-c8] Error configuring API server on cluster domain-c8 An error occurred. This operation will be retried.

2020-06-29T12:52:54.957Z info wcp [opID=5ef9ca68-domain-c8] no single master succeeded – retrying

2020-06-29T12:52:54.957Z debug wcp Publish change event: &cdc.ChangeLogChangeEvent{Resource:std.DynamicID{Type_:”ClusterComputeResource”, Id:”domain-c8″}, Kind:”UPDATE”, Properties:[]string{“messages”}, ParentResources:[]std.DynamicID(nil)}

 

 

does anyone had a similar issue to this?