After deleting this entry, the setup went through.įun Fact: There is an MSI Property for this, when you want to Silently install the View Agent : SUPPRESS_RUNONCE_CHECK. There was an entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce. I found a script, but there was no reboot pending. “PendingFileRenameOperations” is one of the common issues when you face this problem. The logs are located at: C:ProgramDataVMwareView ComposerLogs The Horizon Composer Guest Agent log contains information about QuickPrep and Sysprep script execution. There are some registry keys you can check of you get such an error. The Horizon Composer logs are located in the computer in which Horizon Composer and vCenter Server are installed. Okay, I just installed Windows Updates, so I rebooted my laptop. So I downloaded the latest View 2006 Agent (VMware-Horizon-Agent-x86_64-8.0.0-16530789.exe) and started the setup. In order to use the Horizon Direct Connection Plug-in, you have to install the View Agent. For pretty small environments or direct access a perfect fit! Error message View Agent setup ![]() You can access it using the View Client, but you don’t have to run the connection through a Connection Server. The Horizon Direct Connection Plug-in is not a new feature and you can think of it as a View Agent without a Connection Server. So how should I access it? RDP? TeamViewer? Why not use the Horizon Direct Connection Plug-in? ![]() My intention was to use it headless in a docking station. ![]() I faced this issue not in a customer environment, rather then on my second Lenovo laptop, an X250 with Windows 10 20H2.
0 Comments
Leave a Reply. |