Daemons Installed in Other Clients and the Linux Desktop

For security purposes, it is important to know whether any daemons or processes are installed by Horizon Client.

Table 1. Services, Processes, or Daemons Installed by Horizon Client, by Client Type

Type	Service, Process, or Daemon
Linux client	vmware-usbarbitrator, which numerates the various USB devices connected to the client and determines which devices to connect to the client and which to connect to the remote desktop. vmware-view-used, which provides services for the USB redirection feature. Note: These daemons start automatically if you click the Register and start the service(s) after installation check box during installation. These processes run as root.
Mac client	Horizon Client does not create any daemons.
Chrome client	Horizon Client runs in one Android process. Horizon Client does not create any daemons.
iOS client	Horizon Client does not create any daemons.
Android client	Horizon Client runs in one Android process. Horizon Client does not create any daemons.
Windows Store client	Horizon Client does not create or trigger any system services.
Linux desktop	StandaloneAgent, which runs with root privileges and is started when the Linux system is up and running. StandaloneAgent communicate with View Connection Server to perform remote desktop session management (sets up tears down the session, updating the remote desktop status to the broker in View Connection Server). VMwareBlastServer, which is started by StandaloneAgent when a StartSession request is received from View Connection Server. The VMwareBlastServer daemon runs with vmwblast (a system account created when Linux Agent is installed.) privilege. It communicates with StandaloneAgent through an internal MKSControl channel and communicates with Horizon Client by using the Blast protocol.