|
|
Have a windows 10 linked-clone floating desktop pool that is experiencing frequent disconnects on dell wyse zero clients (p25 and p45). When the disconnect happens the guess OS crashes, resets, and registers the event in vsphere. VM is then placed in an already used state in View.
This is the only error in the PCOIP log I can find.
SERVER :map_agent_to_tera: DISCONNECT_FOR_RECONNECT -> TERA_DISCONNECT_CAUSE_HOST_BROKER_RECONNECT
2016-06-07T07:43:34.220-04:00> LVL:0 RC: 0 MGMT_SESS :Tearing down the session
2016-06-07T07:43:34.220-04:00> LVL:1 RC: 0 VGMAC :Stat frms: R=000000/000000/000000 T=000000/000000/000000 (A/I/O) Loss=0.00%/0.00% (R/T)
2016-06-07T07:43:34.220-04:00> LVL:2 RC: 0 COMMON :TERA_PCOIP: SESSION_EVENT=TERA_MGMT_SYS_SESS_EVENT_RESET, disconnect cause (0x105)
2016-06-07T07:43:34.220-04:00> LVL:2 RC: 0 SERVER :server main: cb_notify_session_status called (mask 0x10) with tera_disconnect_cause (0x105)
Connection Servers are sitting behind a F5 virtual NLB.
Anyone else run into issues with Win10 crashing in a VDI environment
|
|
收藏