To detect network anomalies, network owners must have a concept of expected or normal behavior. We haven't tried to delete profiles yet (and have worked really hard configuring applications to avoid making all users local administrators, so don't really want to do that - specially given that it had been working for ~2 months since we rebuilt these computers using Win 10 圆4). Anomalies can classified generally in several ways: Network anomalies: Anomalies in network behavior deviate from what is normal, standard, or expected. We're using folder redirection, but we are not using roaming profiles. If this option is set to false, but the enable.download option is set to true, the user is taken to a web page for downloading the native Horizon Client installer. We tried uninstalling/reinstalling VMWare Horizon Client, no difference. Option Property Setting Disable HTML Access: enable.webclientfalse. If we run it with a local admin user, it does start the UI (and quickly lowers it CPU usage) - we just have to kill any other instances that were stuck running w/o a UI before starting it as an admin. It seems it is breaking down as it applies Windows Updates, haven't determined an specific update, but it might be HW specific (since at least one computer remains functional after having all updates installed). When we start VMWare Horizon Client v3.5.2, we can see it starts a process in task manager(which stays stuck with 18% of CPU usage), but it never displays its UI WIndows. If that entry exists, it will skip that part. The workaround is to stop the AV temporarily until the install is complete, or add those entries manually. VMware-Horizon-Client-4.9.0-9539668.exe Windows7 HomePremium SP1 I had disabled Firewall and Avast AV and still the error occurs. A lot of AntiVirus applications will prevent this, and hence the failed install. Module D:\Software\VMware\VMware Horizon View Client\vmwHorizonClientController64.dll failed to register. To obtain pre-7.11 versions, customers with active support agreements can contact VMware Support. 127.0.0.1 view-localhost view localhost server. Versions earlier than 7.11 are no longer generally available for download. T12:09:46.Reporting the same problem, seemingly the same behavior. Customers who have purchased VMware Horizon can download their relevant installation package from the product download tab below. T12:09:46.735+05:30 WARN (01) : CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg_Tracked: WriteFile failed: error 233 (Unknown error) T12:09:46.735+05:30 INFO (01) : CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: desktop PID is INFO (01) : CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: client handle is 0F2827A0 T12:09:46.735+05:30 INFO (01) : Session::OnDisconnected:2019: Remote session (C6CD0AC) disconnected: The connection to the remote computer ended. T12:09:46.733+05:30 WARN (01) : RMKSWindow::OnConnectionStateChanged:2202: (C6CB368) disconnected with error 'The connection to the remote computer ended.'. T12:09:46.603+05:30 EROR (01) : RMKSWindow::OnMKSPresentChanged:2050: Failed to mount to remote session. (Posting here in case someone is able to identify what is going on here) On the affected machines I tried checking the client logs but couldn't find any references on the error below: I would strongly recommend you to collect the client and connection server logs and upload it to the VMware GSS team with the user name and timestamp. I changed the agent to 2106 and client to 2203 and it started working fine again. I have observed similar issues with agent 2111 2203 2206 and client 22.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |