NSSM - the Non-Sucking Service Manager can be configured to run LucidLink as a service or multiple services to perform client operations of running a daemon and Linking to your Filespace.

Please download NSSM - the Non-Sucking Service Manager. Making sure you have Installed LucidLink's latest OS client.  

Open command prompt Run as Administrator

Install service for Lucid daemon:

nssm install <servicename> "C:\Program Files\LucidLink\resources\Lucid.exe" daemon --fs <filespace.domain> --user <username> --password <userpassword> --mount-point <drive/folder>
nssm set <servicename> start service_delayed_auto_start

Start Services:

nssm start <servicename>

Multiple service daemons and Filespaces:

nssm install <servicename> "C:\Program Files\LucidLink\resources\Lucid.exe" --instance <id> daemon --fs <filespace.domain> --user <username> --password <userpassword> --mount-point <drive/folder>
nssm set <servicename> start service_delayed_auto_start
nssm start <servicename>

Link Filespace with a specific cache and metadata location root-path

nssm install <servicename> "C:\Program Files\LucidLink\resources\Lucid.exe" --instance <id> daemon --fs <filespace.domain> --user <username> --password <userpassword> --mount-point <drive/folder> --config-path <drive/folder> --root-path <drive/folder>
nssm set <servicename> start service_delayed_auto_start
nssm start <servicename>

To confirm the service started, mounted, and the correct paths are being used type the following.
(Replace the <id> in the command with the instance number that was used. If you aren't running multiple services/instances, then you can remove the entire "--id <id>" part of the command.)

lucid --id <id> status
lucid --id <id> info

Note: You may find that for NSSM to run services non-interactively on some Windows versions you may need to set an additional registry key. To resolve this add DWORD AppNoConsole with a value of 1 under HKLM\System\CurrentControlSet\Services\<servicename>\Parameters