bujia
5th December 2005 13:29 UTC
NSIS & Installation via LAN
Hi!
I'm developing an application for Windows. My target clients are Net Administrators, so I want to create an application .EXE that give possibility to my client to install software from their PC to any other PC of the LAN, simply select IP address of the target PC, after that, my installer push software files to remote destination and then launch installation like it was performed in a local way.
Is this possible to realize with NSIS software?
Thanks in advance to any give me help!
Regards,
Alessandro
Comm@nder21
5th December 2005 13:55 UTC
it is for sure.
its just a bit difficult to develop all the code you need.
you ought to use lots of winapi instructions, meaning a heavy use of the system plugin.
bujia
5th December 2005 14:19 UTC
Installation via LAN
So, it's possible do that with NSIS.
But, do you know best solutions for my task?
Thanks in advance,
Alessandro
Instructor
5th December 2005 14:36 UTC
and then launch installation like it was performed in a local way
You can do it only if you have user shell access.
mstsc.exe /?
Remark: If users servers are on the WinXP and higher.
bujia
5th December 2005 14:43 UTC
Help
Can you post me an example script with NSIS in order to copy a .exe file to remote IP and then launch installation? Controlled by net administrator on his PC.
Thanks in advance,
Alessandro
Instructor
5th December 2005 15:02 UTC
Now I can't. Maybe tomorrow in the office. PS: For the clients on the Win9X/Me and NT/2000, need to be installed special additional software some server to connect.
bujia
5th December 2005 15:11 UTC
I hope that you give me help tomorrow... I need this feauter...but I'm very beginner in this argument...
Thanks in advance,
Alessandro
Instructor
6th December 2005 17:24 UTC
I found nothing useful. My advice: use some program "Client - Server". I have attached RpcExec V1.0, it contain server and client, you can play with it.
NOTE THAT THE 'RpcExec' SERVER DOES _NOT_ PERFORM ANY SORT OF AUTHENTIFICATION !!!
Therefore, make sure that the machine running the 'RpcExec' server is not directly
accessible via Internet !!!