I had to uninstall it completely and then the Agent install completed without any issues. Return value 3.Īfter some digging around, I found out that the issue was caused by Avast Antivirus. VMInstallNewLogoffHandler: ERROR: Failed to get system token: 5ĬustomAction VM_InstallWinNewLogoffHandler returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)Īction ended 15:11:02: InstallFinalize. VMInstallNewLogoffHandler: ERROR: failed to get LSASS Handle 5 VMInstallNewLogoffHandler: Entering VMInstallNewLogoffHandler in C:\\Windows\\Installer\\MSIEE13.tmp, version 0.0.0.0 DLL: C:\\Windows\\Installer\\MSIEE13.tmp, Entrypoint: VMInstallNewLogoffHandler MSI (s) (F0:7C) : Executing op:ĬustomActionSchedule(Action=VM_InstallWinNewLogoffHandler,ActionType=3073,Source=BinaryData,Target=VMInstallNewLogoffHandler,) There was an interesting error in the log: Action 15:11:02: VM\_InstallWinNewLogoffHandler. Installer logs are usually under the users temp folder, as below: `%temp%/vmmsi.log_2019XXXX_184154_Failed.log
The agent install rolled back and to retry installation a computer reboot was required.
Little did I know I would spend an hour troubleshooting the agent install, which usually is a straight forward install. The goal is to remote into a home PC using the Horizon client(PCOIP/BLAST) via DDNS, PFSense and Horizon direct connection.įor the direct connection feature, one of the key requirements is to run the Horizon agent install silently using the command, VMware-Horizon-Agent-x86_64-7.8.0-12599301 /v VDM_SKIP_BROKER_REGISTRATION=1 So I’ve been trying to get Horizon direct connection working in my home lab.
0 kommentar(er)
