mirror of https://github.com/quasar/Quasar.git
Updated Client deployment settings (markdown)
parent
8eb8df3e2b
commit
193f2b5ca6
|
@ -2,8 +2,12 @@
|
||||||
|
|
||||||
### Client identification
|
### Client identification
|
||||||
|
|
||||||
|
The client identification acts as a way to associate a tag with the client. It should help you to recognize the client once it has been deployed, since it can be difficult to keep an overview with many different client settings per deployment.
|
||||||
|
|
||||||
### Process mutex
|
### Process mutex
|
||||||
|
|
||||||
|
The process mutex ensures that only one instance of the client is running on the same system. It should be unique and not re-used for new client deployments. One of the first checks a client performs after startup is to check if the mutex has been used. If it is already in use on the system, the client process is terminated.
|
||||||
|
|
||||||
### Unattended mode
|
### Unattended mode
|
||||||
|
|
||||||
The unattended mode allows remote control of the client without user interaction. When the unattended mode is not activated a small icon will be shown in the taskbar. Additionally notifications will be shown for non-visible actions such as starting a remote desktop session or a file transfer.
|
The unattended mode allows remote control of the client without user interaction. When the unattended mode is not activated a small icon will be shown in the taskbar. Additionally notifications will be shown for non-visible actions such as starting a remote desktop session or a file transfer.
|
||||||
|
|
Loading…
Reference in New Issue