View Administrator can display desktops in a Protocol failure state when one protocol failed but other protocols started successfully. For example, the Protocol failure state might be displayed when HTML Access failed but PCoIP and RDP are working. In this case, the desktops are available and View Client devices can access them through PCoIP or RDP. You are allowed to reassign to another device after 90 days, or in the case of end-point failure You are allowed unlimited backups of both running and stored VMs The primary user of a Windows® VDA device has extended roaming rights, which means that he/she can access their VDI desktop from any device outside of the corporate environment, such as a home PC or an internet kiosk.
Recently I've had random VMs showing their See Agent standing getting 'Protocol Failing.' The View Agent wood logs display the following:
06/02/2014, 13:54:05.773gcapital t; LVL:2 RC: 0 VGMAC :Broker selected user interface address: 169.254.123.87
06/02/2014, 13:54:05.773gcapital t; LVL:2 RC: 0 MGMTENV :Setting ENV adjustable 4: pcoip.ipaddress = 169.254.123.87
06/02/2014, 13:54:05.773gtestosterone levels; LVL:2 RC: 0 MGMTENV :Setting ENV adjustable 5: pcoip.addressgiven = 1
06/02/2014, 13:54:05.773gt; LVL:1 RC:-500 VGMAC :terasockbind neglected for 169.254.123.87 - Can'testosterone levels assign required tackle!
06/02/2014, 13:54:05.773gcapital t; LVL:2 RC: 0 COMMON :terasocksocketclose neglected - Outlet procedure on non-socket (code 10038); treating outlet as shut.
06/02/2014, 13:54:05.773gt; LVL:1 RC:-500 MGMTPCOIPDATA :ERROR: Failed to open up UDP socket
06/02/2014, 13:54:05.773gt; LVL:1 RC:-500 MGMTPCOIPDATA :Failed to get ready for connections
06/02/2014, 13:54:05.773gcapital t; LVL:0 RC:-500 ASSERT :Assert at functionality initmanagers at series number 237.
06/02/2014, 13:54:08.815gtestosterone levels; LVL:0 RC:-500 Normal :Critical Exemption/Reset Detected!! Conserving a minidump file.
06/02/2014, 13:54:11.139gcapital t; LVL:0 RC:-500 Normal :Minidump Document stored as C:ProgramDataVMwareVDMIogspcoipserver201406020000054c.txtpcoipserver201406020000054c.dmp
Is certainly the error because of thé 169.254.123.87 APIPA? Generally a restart óf the VM resolves the issue, however I'm trying to obtain to the bottom of it. This is usually a Horizon View 5.3 environment. Thanks a lot in advance for any help.