Autostart client with Windows

Hello.

If you want to start iRidium client in a user session, you can to create a task in the Task Scheduler Windows. In this case, the user logs in (enters username/password), he on the desktop directly starts the application. If you want to start the app as a service before login a user, you can use nssm. So you can start any application, but it will have to be manually configured. Reference: http://nssm.cc/download
Which method you prefer? Need help setting up?

Hi, I am indeed interested in this topic and would like some help on how to use it as a service.

With the last version of windows 10 the task scheduler doesn't work anymore..

How can i configure nssm?

Hello.

Get task scheduler in Windows 10:
WIN+R
taskschd.msc
Press Ok

Not working?

If the application needs to start, but without displaying a desktop (for example, it is already configured and does not require the input of some data and/or you don't need something to track), then you can install it as a Windows service. Then the app starts when the computer boots and before the user logs in. You can do it using nssm. For this you need to download the archive from binary files: http://nssm.cc/download
For Windows 10 you need to use version 2.2.4-101. Unzip the file and place the disk (for example on C:\bin\nssm-2.24-101-g897c7ad). Open cmd or powershell and run:

cd C:\bin\nssm-2.24-101-g897c7ad\win64\
install nssm iridium

Opens a GUI in which you need to specify settings. A must-have in your case is only a field Path - specify the location of the binary file of the iridium client (by default here: C:\Program Files (x86)\Ltd iRidium\iRidium Pro\iRidium\iRidium.exe). The remaining parameters can be left unchanged. Click "Install service". In the console management services to turn AutoPlay on the newly created service. If you need to see the window client Irudium, you can set the interact with desktop, but then it is better to use not nssm, and to use task scheduler.

The purpose of nssm - configure ANY application as a service: to correctly start, restart and stop the service on behalf of any account, including the system. Use with caution.

We tried to use NSSM in our projects. It worked but we found out there are couple of restrictions:

- you can't save information in a user sql database

- the logs are not saved

You mean "logs in the client"?? But the logs are never saved in the client

sorry, i didn't mention it: it's for the server.

I would suggest to use Windows task scheduler instead.

What I did at first to get around Windows 10 is to use a batch file to launch the program. Now I created a AutoHotKey program to do it. These files can then be placed in shell:startup.

AutoHotKey for 64bit

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
Run C:\Program Files (x86)\iRidium Ltd\iRidium Pro\iRidium\iRidium64.exe